Simulated date 2026-09-25 Back to the fleet overview
Readings
Each line below was read from the state store on this request. Where a reading could not be taken, the line says so rather than showing a number.
-
State store
Firestore, answering reads
-
Last docket sweep
2026-09-02T16:53:54.088321+00:00
Swept 23 simulated days ago, on the simulated date 2026-09-02. It looked at 3 projects and 16 rights.
-
Event bus depth
12 pending of 12 published
Events are documents in the store-backed bus. An event counts as acknowledged here when any subscription has acknowledged it; the bus fans out, so an event one consumer has finished with can still be pending for another. No consumer subscription has acknowledged anything, because no consumer agent is built yet.
- AFFIDAVIT_WINDOW_OPEN P4 due 2026-11-15
- NOTICE_WINDOW_OPEN P1 due 2026-09-15
- NOTICE_WINDOW_OPEN P4 due 2026-09-15
- NOTICE_WINDOW_OPEN P2 due 2026-09-15
- NOTICE_WINDOW_OPEN P4 due 2026-10-15
- AFFIDAVIT_WINDOW_OPEN P2 due 2026-11-15
- NOTICE_WINDOW_OPEN P1 due 2026-10-15
- NOTICE_WINDOW_OPEN P2 due 2026-10-15
- NOTICE_WINDOW_OPEN P2 due 2026-11-15
- RETAINAGE_ALARM P2 due 2026-09-27
- AFFIDAVIT_WINDOW_OPEN P1 due 2026-11-15
- AFFIDAVIT_WINDOW_OPEN P2 due 2026-12-15
-
Gateway dispatches recorded
0 carried, 0 refused
The gateway has written no line on this store, so nothing has been presented to a rail through it. This is a reading of an empty collection, not a report that every dispatch succeeded.
-
Circuit-breaker trips
0 halted of 0 tasks tracked
No agent task has recorded a failed attempt on this store, so the breaker has nothing to count yet. This is a reading of an empty collection, not a report that nothing has gone wrong.
-
Rights by state
16 across the fleet
- 3 Not yet running
- 9 Running
- 3 Due soon
- 0 At risk
- 0 Preserved
- 0 Enforcement window
- 0 Paid and released
- 1 Expired terminal
- 0 Enforcement expired terminal
- 0 Waived terminal
A terminal state is irreversible. A right that expired is not revived by a later sweep, by a payment, or by anything else, which is why the docket records the refusal to move it rather than moving it quietly.
-
Documents the read model could not stand behind
0
Every project, right, dollars-at-risk figure, tick, event, and circuit breaker this read saw decoded, and each one was filed under the key its own identity field names.
Not measured yet
The spec names two more readings this system has no subsystem behind. Each one below names the component that will report it. Neither reads as zero, because a zero would say the measurement was taken and came back clean.
-
Dead-letter queue depth
Will be reported by the Pub/Sub subscriptions, once the event bus runs on them.
The fleet runs the store-backed bus, where an event is a document and an unacknowledged event stays pending rather than moving to a dead-letter queue. There is no queue to have a depth, so this reports nothing rather than nothing wrong.
-
Idempotency keys in flight
Will be reported by the agent gateway, if it comes to write its line before it hands a dispatch to the rail as well as after.
Dispatch happens. Every key the gateway derives is recorded in gateway_dispatches with the agent that presented it and what the rail answered, which is the reading above. What no document holds is the interval between the two: the audit line is written once the rail has answered, deliberately, so that a line saying a letter went is never written before one did. A key in flight therefore has nothing to be counted from, and a worker that died mid-dispatch leaves no row at all. What makes the repeat safe is the far side's own check of the key, which answers E008 rather than opening a second file.