habitat

The Record

Receipts

Five receipt runs, proven on real public data, answer the common questions of a record: what entered, what left, what it said on a date, what a revision changed, and whether a boundary held.

Kits

We have the individual kits as portable "recomputes" you can run in your own environment. Select the kit you'd like, and send us a note.

The five receipts

Agent traces
Did the agent’s own actions leak into its record of what happened?
Given a declared observed-vs-generated boundary in an agent's own record, the receipt detects movement across that boundary and reproduces byte-identically.
v3 67a6f95ee308a2884f73e071ed72bfb0326ba1b7d6da08a147e6ef10394009aa
Read the case →
Keep-out
Did a readable record shape what the system learned?
Given a declared exclusion set, the receipt proves the served geometry is byte-identical to the geometry computed as if those records had never been present.
v3 67a6f95ee308a2884f73e071ed72bfb0326ba1b7d6da08a147e6ef10394009aa
Read the case →
Take-out
Did the erased record actually leave the state?
Given a declared removal set, the receipt proves the certified state is as-if the removed records never existed, on the identity register, byte-for-byte.
v3 67a6f95ee308a2884f73e071ed72bfb0326ba1b7d6da08a147e6ef10394009aa
Read the case →
Point-in-time
Did the backtest’s state ever see the future?
Given a declared as-of state of a dataset, the receipt reproduces that state's digest byte-for-byte and flags any later restatement of the same closed window.
v3 be07f3713ccc406cfd6e880a6b92dadedf6950f503e326ebc2bdfd9f897b2472
Read the case →
Revision materiality
Did the revision change the history — or only its packaging?
The receipt grades a republication's change against the corpus's own measured churn floor, with no vendor-negotiated epsilon; the benign-equivalence class is decided byte-exactly.
v3 150c2313632ed2bfd6600b494dbc3d24d3b4ce05bf29a442df7f488dcaa7aebb
Read the case →

Boundary these receipts verify a declared property of a record deterministically; they do NOT verify whether an output is correct and do NOT certify fairness or independence. A human resolves. The receipt only shows what is byte-decidable.

verify a fingerprint in your browser

Each receipt is a small record of a case's public verdict and digests, and it carries its own SHA-256. Recompute it in your tab and watch it match; alter one character of a copy and watch it fail.

published fingerprint ·

or download the receipt and check it on your bench: receipt file. shasum -a 256 prints the same number.

or compute the SHA-256 of anything, yourself

Type or paste any text. The hash is computed in this tab as you type. No request is made. This is the whole idea at its smallest: a claim you can recompute is not a claim you take on trust, and the same move scales up from this one fingerprint to any record you bring.

sha256 = …

The computation is crypto.subtle.digest: WebCrypto, built into your browser. Press Verify: nothing of yours goes out. A verification is a number computed on your side of the glass.

Boundary CHECK does not recompute the field; RERUN does.

Recompute one in your browser

Recompute a published digit in this tab. Reshuffle holds. Change one value, and it moves.

Published
See the bytes this reads

Verify a receipt · the recompute, in depth · request a kit