You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
The ledger's recipient: the Maintainer's certificate under config/ledger/ and its pin in .github/ledger-recipients #653
A precondition of #562, "A fresh held-out gate set for the Release after v0.1.0, never replayed".
Decision 0164 (#612, merged with #628) seals a gate set's ledger to each certificate that .github/ledger-recipients pins by sha256, read from config/ledger/ (harness/eval/seal.py, RECIPIENTS and CERTS). Neither the file nor the folder exists on main yet. So, as 0164's row "With no certificate pinned" intends, a gate set's run stops at the seal with no_recipient and uploads nothing. A development set's run is untouched.
What is owed
The Maintainer, at his terminal: make a key pair for the ledger. The private key never leaves his machine and is never committed, pasted or set as a secret. Its public certificate is what gets committed.
A session, by pull request: commit that certificate under config/ledger/ and its pin, <sha256> config/ledger/<name>, in .github/ledger-recipients. Both are protected paths, and the merge is the Maintainer's.
The Maintainer, in the home, when the gate set is seated: commit its shard salt, <role>/<set>.salt, 16 to 256 random bytes, beside its cases. A gate set's shards are drawn by it, so no reader can tell which cases a shard holds. Without it, a gate set's run stops at the fetch with no_shard_salt (A case's head is read from the private home, pinned by its hash, and the run is sharded #611 PR 2, the Factory Builder's ruling (a) of 2026-11-09).
Show on the PR that the seal accepts the pin: tests/test_evals.py's seal tests pass, and a sealed test ledger opens with his key at his terminal alone.
Not in scope
Where ledgers are kept past the artifact's 90 days. 0164 leaves that to a later record, near gate-v1.
Done when
The pin and the certificate are on main, the gate set's salt is in the home, and a gate set's run stops at neither no_recipient nor no_shard_salt.
Activity