PLAN
Changelog
The one rule says that when the code catches up we update the page. This is the record of that happening, including the entries that make us look worse than the previous version did.
| Date | Kind | What changed |
|---|---|---|
| 2026-10-04 | status | The fact sheet (/facts/) moved from IN DESIGN to LIVE. Every figure on it is now read from a real surface this site computes — the transparency log, the ledger invariant, the countersignature survey, the estate tally and the registry — each carrying its own as-of, and a labelled absence where a source does not answer. No figure on it is a typed constant. |
| 2026-10-04 | spec | Two routes added for Token2049, both LIVE and both server-rendered: /network/ frames why the agent economy needs an unfakeable settlement record and links the canonical AAO and mesh definitions on gda.group and flashyos.com rather than restating them; /demo/ lets a stranger verify a real settlement and a real log leaf in one screen, composing /verify/ and /verify-leaf/ with no second client component. |
| 2026-09-07 | status | The settlement rail went live end-to-end. FlashyID mints a short-lived rewards:issue token with its own OIDC key, the rail verifies that signature (RAILS_VERIFIER=flashyid), and flashy.gold and this property both read the rail. The dev shared-secret verifier is retired. |
| 2026-09-07 | status | The rail’s RFC 6962 transparency log shipped, and this property reads it at /settlement-log/. The server hands over the opaque feed — hashes and proofs, no amounts and no identity — and inclusion and append-only history are recomputed in the reader’s own browser against the published tree head. |
| 2026-09-07 | status | The explorer read-model is self-healing: it rebuilds from the log rather than being written to alongside it, so a divergence between the two closes on the next read instead of being carried forward as a second source of truth. |
| 2026-08-14 | spec | Property created. Twenty-eight routes registered with their status glyphs; the nav, footer, sitemap, llms.txt and network.json all generate from one registry module. |
| 2026-08-14 | status | Anchoring added to the roadmap as IN DESIGN, with TON and Base as the first two targets. The chain question is answered on /roadmap/: the record gets anchored, the asset deliberately does not. |
| 2026-08-14 | honesty | Every figure published at launch reads REPORTED. The invariant job does not exist, so nothing is entitled to read RECONCILED. |