Status

What is fresh, and what is not.

Every feed this site reads, with its signer, its epoch and its age — under one rule. A signature proves who published the bytes, not that they are recent, and not that they are right. Where a feed has gone quiet, this page says so instead of a green light.

reading 6 feeds…

feedschemasigner · kidepochfreshnesswhat it powers
census_manifest.json

reading…

—verifying…—epoch…home counter · trust strip · /census matrix · page backdrop
census_v1.json

reading…

—verifying…—epoch_iso…/census four numbers + ladder · home "signed facts"
autonomous_live.json

reading…

—verifying…—as_of…nothing yet — proposed companion to the registered count; held until as_of is fresh
reputation_v1.json

reading…

—verifying…—epoch_iso…/agents fleet + tier pills · home "signed fleet"
anchor.json

reading…

—verifying…—latest_anchor…/census "recompute it yourself" · the age-of-record claim
status.json

reading…

—verifying…—observed_at…the footer status line on every page

backend·checking…

The rule

one function, six rows
live
epoch under 24 hours old. The only state that earns a dot.
as of {date}
one to seven days. Usable, dated out loud.
frozen since {date}
older than a week. The publisher has gone quiet; the numbers are what they were on that day.
—
no epoch, no file, or no probes. Never a guess, never a zero standing in for unknown.

Age is measured in your browser against the epoch the feed itself declares, so a wrong local clock moves every row the same way. The pinned signing key is fgkuOg…4kk=; "kid" is the key the feed names, which only matters when it is not that one.

When a row is frozen

  • · Pages that read that feed keep showing its last numbers, dated. They do not fall back to a hand-typed figure.
  • · A valid signature on a frozen feed still reads "signed ✓" — it proves authorship of old bytes, nothing more.
  • · If freshness and the footer disagree, the footer is wrong; it is being retired in favour of this page.

Something broke rather than aged? Incidents, with dates →