PROVENANCE

Manifest root

230d510f4c2aeb9936f9ae40e378d8e3188b70294d1ce0cd663b6a19cbb714e8

sha256 over newline-joined, lexicographically sorted "path:sha256" and "repo@commit" entries

The root is a pure function of content, so it moves only when the work moves. The manifest itself is not what gets stamped: it embeds per-artifact commit metadata, which changes on every commit even when no artifact changed. Stamping that would go stale for no substantive reason. The root is served on its own at /provenance-root.txt.

Anchored with OpenTimestamps. A stamp is submitted to calendar servers first and folded into a Bitcoin block shortly after; only once ots upgrade has attached that block does verification stop depending on the calendars and rest on the blockchain alone. The status below is read from each proof: it says anchored only when the file actually carries a Bitcoin block attestation.

node scripts/build-provenance.mjs
node scripts/stamp-provenance.mjs
ots stamp   public/stamps/<date>-<root>.txt
ots upgrade public/stamps/<date>-<root>.txt.ots   # once mined
ots verify  public/stamps/<date>-<root>.txt.ots

Stamps accumulate rather than replace. A later change does not invalidate an earlier stamp — it covers an earlier state, which is the whole point of a timestamp.

Public artifacts

Hash any of these yourself with shasum -a 256 <path>.

Private-repository commits

These repositories are not public. A git commit SHA is itself a hash over the entire tree and history, so publishing one commits to that exact content while revealing none of it. If a repository is later opened, anyone can confirm the SHA matches what is claimed here.