Status
What was last observed, and when. This page is a static
snapshot generated at 2026-08-22T21:35:40Z. It cannot know when you are
reading it, so every time below is absolute and in UTC; subtract against your own clock.
The sources
117 observations recorded. The watcher fetches each source, stores the exact response bytes, and records what changed. It signs nothing and publishes nothing.
| Source | Last observed (UTC) | Result | Artifact |
|---|---|---|---|
superstate-ustb-nav-daily | 2026-08-22T05:00:44.078875Z | OBSERVATION_CHANGEDthe normalized observation itself differed | dfd58332f1d8f354… |
superstate-ustb-yield | 2026-08-22T05:00:44.078875Z | OBSERVATION_CHANGEDthe normalized observation itself differed | 2447fcc3694d27a4… |
superstate-ustb-holdings | 2026-08-22T05:00:44.078875Z | UNCHANGEDbyte-for-byte identical to the previous look | 0c42d7949ccfbcd1… |
The publishing daemon
The publishing daemon last wrote a heartbeat at 2026-08-22T21:35:30.633390Z, declaring it valid until 2026-08-22T21:38:30.633390Z.
Within its declared window at the moment this page was generated.
That verdict is computed here, at generation time, by comparing the heartbeat's own declared expiry against the clock. It is not a status the daemon stored about itself: a process that has stopped running cannot write down that it stopped.
The measured window
The canonical public facts record lists
25 reports, of which
20 reached
CONFIRMED, and records
9 permit/refuse enforcement
transactions. Unattended publication began
2026-08-20. That proves the unattended path
ran; it does not establish a multi-day reliability record, and no uptime percentage
is claimed.
This page does not publish an incident history. The repository implements an append-only incident log, but no incident-log projection is present in the canonical public site data consumed by this generator. Operational failures must not be presented as public history until such an artifact exists and is wired into this page.
How to read a stale page
An old timestamp above is not proof that the daemon is down. It proves that this page was not regenerated. Those are different failures: one is about the publisher, the other about whatever refreshes this file. Neither is evidence for the other, and this page will not guess which one happened.
Nothing on this page asserts that an asset is safe or independently verified. As of the generation time above: No canonical artifact state was supplied to this status build, so this page does not invent one. Use the Coverage and Verify surfaces for retained artifacts, and read the registry for current onchain state. A later report can reach a different state while this file is still being served, so check Coverage, Verify, and the live registry rather than treating this sentence as current.
The observations above are captured against the workspace named in this service's configuration; the retained artifact and public chain counts are separate facts. Neither implies the other.