Custody
Raw bytes are stored under their own hash and never rewritten. Derivatives are keyed by object and parser version, so improving a reading writes a new one beside the old rather than moving the ground under a claim that already cites it.
Integrity, at build time
- Observations
- 173
- Distinct objects
- 75
- Objects verified
- 75
- Corrupt
- 0
- Missing
- 0
- Failed reaches logged
- 1
- Re-observations of identical bytes
- 97
An unchanged response still logs an observation. Identical at T is evidence: it is the only thing that bounds when a silent revision could have happened.
The invariant
Custody integrity must not depend solely on the continued honesty or security of the repository that stores custody.
Git gives content addressing and history. It does not make history immutable against anyone with enough authority over the repository. Each checkpoint chains to the one before it over the manifest hash and a root across the sorted object set. Publishing a digest under different control is what turns a rewrite into a contradiction. That step is not built yet, and this page says so rather than implying it.
Checkpoint chain
-
2026-08-23
cf5f8d6ba5bac86bc699b5fa6e4e51ef…
104 observations · 75 objects
manifest e5728b12679e8879… · prior None… -
2026-08-23
374c8822bea887d6cf9b2fc2b815ad94…
173 observations · 75 objects
manifest 6a0bef1acebc5c3a… · prior cf5f8d6ba5bac86b…