Proof 04 · The ledger
The public record. Append-only. Externally verifiable. Growing daily.
Every meaningful operational decision the architecture makes is anchored to a numbered ledger entry. The numbers are sequential, the entries are dated, the actions are described, and the integrity of each entry is verifiable from the outside without our help.
This is the snapshot, current at the moment of this page going live.
What an entity is. A distinct record of something that exists or has existed — an artist, an artwork, an exhibition, an institution, a sale, a custody event. Each entity has a unique identifier, a category (A through F by category schema), a source authority tier, and a visibility scope. Entities are added when verified; they are not removed, only superseded.
What an anchor is. A sequenced ledger entry recording an operational decision — a record created, a record updated, a deployment completed, a covenant decision logged, a validation rule applied. Each anchor carries a monotonically increasing sequence number; sequence 1 is the first anchor in the chain, and the most recent number is the count of operational decisions logged since.
A small slice, recent.
| Seq | Date | Category | Description |
|---|---|---|---|
| 187+ | 2026-05-13 | F | sentyal.com wave 2 deploy — 10 pages live, sha256 verified |
| 186 | 2026-05-13 | F | sentyal.com wave 1 deploy — 6 foundation pages live |
| 185 | 2026-05-12 | E | Connectivity matrix locked — 7 domains, SSH users verified |
| 184 | 2026-05-12 | F | Sitemap regression fix — static generation, Array phantom resolved |
| 183 | 2026-05-11 | F | htaccess hardening — production policies applied |
| 182 | 2026-05-11 | D | Quarterly review section — deployed and reachable |
| ... | ... | ... | ... |
| 1 | (genesis) | A | Genesis anchor — chain initialised |
The full ledger is available to authenticated parties through the API surface, and a redacted public extract is available on request for due diligence reviews. Anchors marked under public-visibility scope are reachable directly; anchors under partner-visibility or higher require granted access.
Hash chain. Independent re-computation.
Each anchor carries a hash that depends on the contents of that anchor and the hash of the previous anchor. A third party who is given the full chain can recompute every hash and confirm that no entry has been silently rewritten — the property of an append-only ledger. If any entry were altered, the hashes downstream would no longer match the published values, and the alteration would be visible.
The published values are dated and signed at intervals against external timestamping. A reader who wants to verify can take a published checkpoint, recompute the chain forward to the next checkpoint, and confirm that nothing happened in between that should not have.