3tears-epoch
Generation-stamped configuration epochs with NATS broadcast and per-message echo for cross-pod cache-reload coherence.
Why
Multiple in-memory configuration caches across the platform need to stay coherent across pods on admin writes:
- a model capabilities registry (registered at startup from the
modelstable) - a catalog cache (
gateway_models+gateway_providers+gateway_credit_rates) - per-tool MCP RBAC grants
Pure NATS broadcast (push) ships with a missed-message hole: a pod that didn't receive the broadcast (subscriber blip, pod just started during the window, JetStream redelivery edge) stays stale. Pure polling (pull) is correct but expensive on hot paths.
This package combines both: a strictly-monotonic generation number (epoch) per subject, broadcast best-effort via NATS and echoed in every relevant response message so consumers detect staleness on the next read and lazy-pull. Push for speed, pull for correctness.
The counter itself lives in a memory-backed NATS KV bucket for every epoch whose value stays inside the cluster. That is deliberate: an epoch is a coherence signal, not a durable fact, and a restart that loses the counter also loses every cache it was sequencing. The one exception is an epoch whose value escapes -- a tile epoch is the v{n} in a tile URL and reaches browser and CDN caches nothing here can reach -- and that family keeps a durable config_epochs row.
This is the standard pattern from etcd mod_revision + watch, K8s resourceVersion + informer, Envoy xDS version_info + ACK, DNS SOA serial + secondary refresh.
Deployment obligation: the KV grant
Every principal that bumps or reads an epoch must be granted the {ns}-epochs KV bucket
(AGENT_POD, HUB, GATEWAY in threetears.nats.subject_permissions). A missing KV
grant does not raise. A refused JetStream request is never answered, so the call blocks to
its deadline and returns a timeout, indistinguishable by shape from an unreachable broker.
The log tells them apart. threetears.nats reads the server's permissions violation frame
(which leaves the connection open, so nothing else reports it), names the bucket, and states
the js_resources entry to add; the deadline path and a failed bucket open say the same.
tests/enforcement/test_kv_bucket_grant_naming.py pins the grant against the bucket the
client actually opens, which catches a wrong name before a deploy rather than in a log.
Consumers also register an on_reset callback and schedule a
threetears.epoch.catchup_tick pass. A consumer that subscribes and schedules neither still
receives broadcasts, and misses everything a broadcast can lose -- including a counter
replaced by a broker restart, which every KV operation survives silently.
Identity
The unit of identity is the NATS subject path. Each consumer:
- Defines or uses an existing
Subjectbuilder for the configuration domain it owns (e.g.Subjects.capabilities_epoch()->capabilities.epoch). - Calls
EpochClient.bump(subject, payload=...)after committing the row mutation that motivates the reload. - Subscribes via
EpochListener.subscribe(subject, on_bump=...)from sibling pods.
For the durable family, the hub's config_epochs row PK is the subject path string and Postgres is the source of truth. For everything else the KV counter is, keyed on the subject path (digested when the path falls outside the KV key grammar). The NATS broadcast is best-effort either way. A subscriber that missed every broadcast still catches up on the next request whose response echoes the higher epoch (per-message echo is consumer-side wiring; the framework supplies the building blocks).
Wire envelope
EpochBumpMessage is a frozen Pydantic v2 model:
subject_path: stris the namespaced subject the bump targets (the KV counter key, or the row PK for the durable tile family)epoch: intis the new strictly-monotonic valuepayload: dict[str, Any] | Noneis an opaque hint for the consumer's reload callback (e.g.{"model_id": "...", "action": "create"})
The framework never inspects payload. Consumers parse if useful, ignore if not. The hint exists so a domain that only changes one row can avoid reloading the entire derived view.
Postgres
CREATE TABLE IF NOT EXISTS config_epochs (
subject_path TEXT PRIMARY KEY,
epoch BIGINT NOT NULL DEFAULT 0,
payload JSONB,
date_updated TIMESTAMPTZ NOT NULL DEFAULT now()
);
bump(subject, payload) increments the subject's counter and returns the new value. For an ephemeral subject that is a DistributedCounter CAS loop over NATS KV; for the durable family it is INSERT ... ON CONFLICT (subject_path) DO UPDATE SET epoch = config_epochs.epoch + 1, payload = $2, date_updated = now() RETURNING epoch, serialized on the row lock. Both are atomic and both hand back a per-subject contiguous number, so 0 means "never bumped" and the first bump returns 1.
Migration ships as a PLATFORM-scope PackageMigrations registration so consumers wire it via the canonical MigrationRunner alongside the rest of their platform tables.
1 maintainer
Release files for 3tears-epoch 0.42.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| 3tears_epoch-0.42.0.tar.gz | 49.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| 3tears_epoch-0.42.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 77.6 kB
Release files / 3tears_epoch-0.42.0.tar.gz
| Download URL | 3tears_epoch-0.42.0.tar.gz |
|---|---|
| Size | 49.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8476ed40cd54629729a231fa625de9cd6dfe2cae7fad0679fb4d4b81d811761c
|
|
BLAKE2b-256 checksum How to use checksums |
c0c9ce55b519b26f7f6c09794fb4651905b4502336aaf0802999d518f81e2f0d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 15, 2026.
Transparency logRelease files / 3tears_epoch-0.42.0-py3-none-any.whl
| Download URL | 3tears_epoch-0.42.0-py3-none-any.whl |
|---|---|
| Size | 28.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dd4e1e17532695312ea3f3a3a896ac053cb6baf21d3a48dacad2da9feb0eaa9c
|
|
BLAKE2b-256 checksum How to use checksums |
d116004cc250fbc52fbca57b4adaae222b5789c2a4dfbe8a4463d2544e3f92c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 15, 2026.
Transparency log
