Seal the Public Candidate: exact-head receipts for rows 31 to 33 - #4
Merged
Merged
Conversation
The adoption and closure merges moved all eight repositories, so the manifest names the final revisions and the inventory is re-digested. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The final heads are gated: POSIX rehearsal 22 of 22, MSVC 44 test targets, go/no-go with no fatal findings, reconstruction verified. Rows 31, 32 and 33 now cite these receipts instead of the 2026-09-12 set, which stopped being final when the release-integrity fixes, the rows 27/37 closure and the adoption READMEs moved the tree. Earlier receipts are retained unedited. HEADS.json records the eight release revisions and .github separately. The final mcl-core revision is the merge commit of this change, which cannot name itself; it goes in the row 36 external-review issue. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The ledger is an inventoried release artifact, so the bundle digests have to follow it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
mcl-release-governor
Bot
requested review from
0j0bit and
sed-boi
as code owners
September 13, 2026 03:36
0j0bit
approved these changes
Sep 13, 2026
0j0bit
left a comment
0j0bit
left a comment
Contributor
There was a problem hiding this comment.
Reviewed as 0j0bit: release-closure scope only (seal receipts, rows 31-33, rebuilt bundle); confirmation rehearsal 22/22 on this head; build (gcc) and build (clang) green.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Seals the Public Candidate. This PR contains only release-closure records: no README, protocol, evidence or adoption changes.
What changed
conformance/independent/20260913-public-candidate-seal/: the exact-head software closure on the final heads. POSIX rehearsal 22/22, MSVC 44 test targets, go/no-go with no fatal findings, reconstruction verified.HEADS.jsonlists the eight release revisions and.githubseparately. The logs are scrubbed of local identity, then digested.governance/RELEASE_GATE_V1.md: rows 31, 32 and 33 now cite these receipts. The 2026-09-12 set stopped being final when the release-integrity fixes, the rows 27/37 closure and the adoption READMEs moved the tree. Earlier receipts are kept unedited.releases/v1.0.0/: the bundle is rebuilt onto the final heads, then again after the ledger update, because the ledger is an inventoried artifact.Verified before opening
.githubare public and governed, with zero tags, zero Releases and no other open PRs.The final
mcl-corerevision is this PR's merge commit, which cannot name itself. It will be recorded in the row 36 external-review issue. No tag and no Release.