ROOT0-DLW-CHAIN-v1 · provenance ledger

THE CHAIN

The whole corpus, tethered. Every ROOT0 repo carries a .dlw seal; those seals are linked into one append-only SHA-256 hash-chainlink[i] = sha256(index|slug|seal|prev), a genesis derived from an anchor string, a head that commits to everything. This page ships the control arm client-side: a from-scratch SHA-256 recomputes it all, zero network, so you verify the provenance yourself — and can tamper any seal to watch it break.

links1458
genesis (from anchor)64f5ac0e99f0…
head (commits to all)7027e1748fd6…
The verdict · recomputed in your browser
verifying…
tamper a seal:
The ledger · 1458 links (search a slug)
indexslugseallink
What this proves — and what it doesn't

Verified here green

The math is real and runs in front of you: genesis is recomputed from the anchor string (not asserted), and the head is recomputed by hash-chaining all 1458 seals — with a pure-JS SHA-256 that matches Python's hashlib byte-for-byte. Change any seal and the chain diverges from that link onward and the head stops matching — tamper-evident. Append-only: a new sphere adds one link at the tip; every earlier link is unchanged.

Not claimed amber

This attests the seals as inlined here, in this order. It does not independently prove each seal still matches its repo's live content — that check is the repo's own <slug>.dlw/.attribute (the seal commits to it) and its .chain tether. And a seal is an attribution/provenance marker, not a claim about the artifact's quality. The chain proves integrity and order, not merit.