Skip to content

The release-head guard (S-1), and the Track 1 banners struck (proposes v5.15.2) - #26

Merged
Hafeok merged 4 commits into
mainfrom
claude/release-head-guard
Oct 26, 2026
Merged

Hafeok merged 4 commits into
mainfrom
claude/release-head-guard

Conversation

@Hafeok

@Hafeok Hafeok commented Oct 26, 2026

Copy link
Copy Markdown
Collaborator

Ruled as a whole by Emil at the downstream housekeeping session of 2026-10-26 ("agreed on all execute it"; charter committed at decision-driven-design meta/sessions/2026-10-26-housekeeping/prompt.md). Merging this PR is the ratification act, and it cuts v5.15.2.

What lands

Commit What
d4fff7e DDD-dec-26 and DDD-frame-02 lose the [PROPOSED] banners they carried since v5.8.0, the release that ratified them; DDD-frame-02's duplicated "One / One" fixed. Notes only.
1097055 The release-head guard, successor item S-1. spec/release-format.md format 2 (additive): mandatory ratified_head, rule 7. scripts/check-release-head.py implements it; release.yml runs it at the commit under release, validate.yml at the PR head for not-yet-cut descriptors. Format 1 descriptors are valid unchanged.
0849ab8 DDD-dec-39, the ruling: the class, the guard, the hit-list, the banners.
630475c releases/v5.15.2.yaml, format 2, ratified_head: 0849ab8. The guard's first instance.

Hit-list, run before the class was chosen

v5.13.0    ok   (assumed 1c58dd6)   control
v5.14.0    MISS (assumed 75cc767)   ratified head is not an ancestor of 8ddcd5a
v5.15.0    MISS (assumed cc0abf8)   ratified head is not an ancestor of 13128a7
v5.15.1    ok   (assumed 7266306)   control
nine others unguarded (format 1)

Both recorded misses fire; the mirror case (unratified commits merged after the ratified head) was exercised separately and fires on the diff check.

Pin consequence downstream

None predicted: notes are outside the hashed fields. The downstream advance v5.15.1 → v5.15.2 is predicted at E12 0 · E13 0 · W5 0 · W6 0 · W7 1 and is staged against this branch in the companion downstream PR.

If a change is ruled before merge

Re-commit the descriptor last with the new ratified_head. That is rule 7's own pattern, and validate.yml will refuse the PR head otherwise.

🤖 Generated with Claude Code

Hafeok and others added 4 commits October 26, 2026 14:53
… fix the duplicated word

Both records were ratified at v5.8.0 (PR #15, merge 9e92099) and carried their
banners for seven releases. Notes only; no statement, status, region or
canonical_md moves, so no downstream pin digest moves.

Basis: DDD-dec-26; DDD-frame-02; DDD-agent-01

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…se merged head moved (S-1)

spec/release-format.md gains §4 (format 2, rule 7): the merged head must be the
ratified head plus at most the descriptor. scripts/check-release-head.py
implements the ancestry and diff checks; release.yml runs it at the commit under
release, validate.yml at the pull request head for not-yet-cut descriptors.
Format 1 descriptors are valid unchanged and unguarded.

Hit-list, run before the class was chosen, with the two recorded misses
reconstructed from the record: v5.14.0 (ratified 75cc767, cut 8ddcd5a) MISS;
v5.15.0 (ratified cc0abf8, cut 13128a7) MISS; v5.13.0 and v5.15.1 as controls ok.
The mirror case (unratified commits merged after the ratified head) is caught
by the diff check.

Basis: DDD-dec-39; DDD-agent-01; DDD-dec-37

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Basis: DDD-dec-39; DDD-agent-01; DDD-dec-37; DDD-dec-26

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Basis: DDD-dec-39

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant