The developer protocol: run the nightly by hand, no Nexus, and submit its evidence in the PR #135

New Issue

2026-11-07T20:15:18Z

rajames commented

2026-11-07 20:15:18 +00:00

Ruled

Captain Bob, 2026-11-07: "We can simply run nightly as developers to further make sure nothing sneaks in. Just no Nexus push. ... a protocol for programmers. Then the protocol evidence can be submitted in the PR."

Built (to do)

scripts/nightly.sh protocol: every nightly stage in order -- accept amd64|aarch64|riscv64|stick-high, test-32, proofs (capped), images, docs -- and never publish.
It writes logs/<TS>/PROTOCOL.md: the commit and whether the tree was clean; each stage's result and log directory; POST counts and dict_hash per architecture, the three compared; test-32's totals; the proofs' result; the images' SHA-256.
The developer commits that directory; the PR template asks for it ("PROTOCOL.md for the head commit").
acceptance.yml checks the PR carries a PROTOCOL.md for a commit whose tree is the head's, so stale evidence cannot ride along.
What each alpha's release did by hand on 2026-11-07, made one command.

Done when

scripts/nightly.sh protocol runs the stages and writes PROTOCOL.md; .claude/CLAUDE.md names it as the acceptance a developer runs
The PR template and the CI check
Verified: a PR without it, and one with evidence for another tree, are refused; one with it passes

🤖 Filed with Claude Code -- the review after v4.0.0-alpha.3 (Captain Bob, 2026-11-07: "a list of problems, deficiencies, smells and so on placed in issues by rank priority").

### Ruled Captain Bob, 2026-11-07: "We can simply run nightly as developers to further make sure nothing sneaks in. Just no Nexus push. ... a protocol for programmers. Then the protocol evidence can be submitted in the PR." ### Built (to do) - `scripts/nightly.sh protocol`: every nightly stage in order -- `accept amd64|aarch64|riscv64|stick-high`, `test-32`, `proofs` (capped), `images`, `docs` -- and never `publish`. - It writes `logs/<TS>/PROTOCOL.md`: the commit and whether the tree was clean; each stage's result and log directory; POST counts and `dict_hash` per architecture, the three compared; test-32's totals; the proofs' result; the images' SHA-256. - The developer commits that directory; the PR template asks for it ("PROTOCOL.md for the head commit"). - `acceptance.yml` checks the PR carries a PROTOCOL.md for a commit whose tree is the head's, so stale evidence cannot ride along. - What each alpha's release did by hand on 2026-11-07, made one command. ### Done when - [ ] `scripts/nightly.sh protocol` runs the stages and writes PROTOCOL.md; `.claude/CLAUDE.md` names it as the acceptance a developer runs - [ ] The PR template and the CI check - [ ] Verified: a PR without it, and one with evidence for another tree, are refused; one with it passes 🤖 Filed with [Claude Code](https://claude.com/claude-code) -- the review after v4.0.0-alpha.3 (Captain Bob, 2026-11-07: "a list of problems, deficiencies, smells and so on placed in issues by rank priority").

rajames added this to the v4.0.0-alpha.4 milestone 2026-11-07 20:15:18 +00:00

rajames added the

labels 2026-11-07 20:15:18 +00:00

rajames referenced this issue