MathSphere Nexus
Every project in this house carries a demo section: every feature tested live, and the runs written up as guidance. On this site, that record has a public face — Feature Evidence. Each entry below is a Run Record: one real run of the real product, what it did, and its verdict. For an integrity ledger, the natural first evidence is the ledger witnessing itself — and that is where this record begins. Where a run has not happened yet, this page says so.
The Arbiter's first baseline of its own tree: 57 files snapshotted and hashed into a manifest (beginning 194c363b), and the snapshot verified at creation — the verify returned ok. A baseline is a promise about the past: from that day forward, any change to those files is a difference the ledger can name.
A day later, after the salt bank and the guard-view landed, the second baseline: 76 files, 369,839 bytes, manifest beginning b8463c5f — and the verify again returned ok. The growth itself checks out against the first baseline's own arithmetic: 57 files, plus 21 added, minus 2 renamed away, is 76. The ledger's story of its own change adds up.
The Arbiter's MCP bridge — the doorway by which a model may look at the ledger — landed with the suite at 149 of 149, and exactly eight tools, every one read-only. A model at that bridge can observe and report; it cannot snapshot, seal, or change anything. Observation is receipted; modification belongs to the person, at the terminal, asked twice. The bridge's shape is the verdict: looking is permitted, touching is not.
The per-feature Run Records — the demo section assembled feature by feature from the Arbiter's own records: the salt bank at work, the vault and its five one-time recovery keys, the guard-view reads. The Arbiter's next build, its graphical interface, will give those records their natural home; this page carries what exists today.
Generous software, with built-in privacy.
— Alexander