Repository navigation
The release-head guard (S-1), and the Track 1 banners struck (proposes v5.15.2) - #26
Merged
Merged
Conversation
… 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>
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
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.
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-designmeta/sessions/2026-10-26-housekeeping/prompt.md). Merging this PR is the ratification act, and it cutsv5.15.2.What lands
d4fff7eDDD-dec-26andDDD-frame-02lose the[PROPOSED]banners they carried since v5.8.0, the release that ratified them;DDD-frame-02's duplicated "One / One" fixed. Notes only.1097055spec/release-format.mdformat 2 (additive): mandatoryratified_head, rule 7.scripts/check-release-head.pyimplements it;release.ymlruns it at the commit under release,validate.ymlat the PR head for not-yet-cut descriptors. Format 1 descriptors are valid unchanged.0849ab8DDD-dec-39, the ruling: the class, the guard, the hit-list, the banners.630475creleases/v5.15.2.yaml, format 2,ratified_head: 0849ab8. The guard's first instance.Hit-list, run before the class was chosen
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, andvalidate.ymlwill refuse the PR head otherwise.🤖 Generated with Claude Code