Alpha Data Omega
Provenance anchor

Every claim, anchored to a hash.

ÃDO is where the work's provenance lives — content-addressed on IPFS and written to a hash-chained, append-only record. Anyone can verify that a published artifact is exactly the bytes that produced a result. Accountability is not a policy on top; it is the address of the thing.

Content-addressed · Hash-chained · Append-only

How anchoring works

Anchoring is four mechanical steps. There is no trusted authority in the loop — the hash does the work.

01 · Hash

Hash

Every artifact — a benchmark package, an evidence release, an access request — is SHA-256 hashed on creation.

02 · Address

Address

The artifact is content-addressed on IPFS, so its address is its hash — change one byte and the address changes.

03 · Chain

Chain

The hash is written to an append-only record that links to the prior head, so the order and integrity of the whole history is verifiable.

04 · Verify

Verify

Anyone with the artifact can recompute the hash and confirm it matches the published anchor. No trust required.

What is anchored

content-addressed artifacts
Results

Benchmark result packages

The frozen package behind a reported number, hashed so the bytes that produced the result are fixed.

results.ado.earth →
Evidence

Evidence releases

Public evidence packages with their sealed-source commitments, each carrying a signed manifest digest.

evidence.ado.earth →
Access

Access-request receipts

Receipts from the agreement flow, anchored so the terms and timing of each request are tamper-evident.

Scrub

Scrub / exclusion manifests

The record of what was withheld before publication and why, so the omission itself is auditable.

SHA-256 Content-addressed Hash-chained Append-only

An anchor, illustrated

Each anchored artifact publishes its digest and the head of the chain it links into. The values below are an illustrative example — they are not live anchors.

chain head · sha256
558307411338f8a7831d2aef…
prev head · sha256
259467c906631b7f1b5b8c90…
artifact · sha256
230ccf4dbb6d9125f1f6331c…
IPFS address (CID digest)
3a52886c6d30b6ca51123947…
Illustrative — live anchors are published beside each artifact.

Why content-addressing.

When the address of a thing is its own hash, tampering is not hidden — it is a different address. That is what makes 'accountable by construction' literal rather than aspirational.