The heartbeat,
or the honest silence.
This is the public event stream of the Warden ledger. When the system is running it shows cryptographic events as they are written. When it isn't — which is right now — it says so, rather than filling the screen with something that looks like activity.
01 What appears here — and what deliberately doesn't
A public feed of a system that handles emergency imagery has to be careful about what it publishes.
Shown Cryptographic governance events
Key issuance and chain anchoring — the events that let a third party verify the record. These come from tables that are world-readable by design, because verification must not depend on our cooperation.
Never shown Incidents, flights, imagery
Operational records are readable only by authenticated, role-gated users. A public stream of fire-service activity would be a privacy failure, so incident and flight events cannot appear here — not because the feed is incomplete, but because the access model forbids it.
In synthetic demo stream mode you will see flight-type events, so you can judge the interface. Every one is tagged SIM and generated in your own browser.
02 The three states
All three are honest outcomes. None of them is a placeholder.
03 Don't take the feed's word for it
A live-looking feed is easy to fake; that is precisely why it is not the evidence. The evidence is the published algorithm, the public signing key and the verification tools — all of which let you recompute the record yourself, offline, without us.