Repository navigation
The arity ruling lands in the decision register — DDD-dec-36 and v5.14.1 - #23
Merged
Merged
Conversation
…uling) Per the DDD-dec-15 precedent: a stranger reading DDD-frame-08 reaches why it was re-scoped through the graph, and the Bovens lineage constraint — no file may claim more than authority linkage plus the tense change — is a governing decision that outlives the session. The claim's notes point at the decision. Re-landed after the #22 merge: v5.14.0 was cut before this filing reached the PR, and a cut descriptor is immutable — the original commit's edit to releases/v5.14.0.yaml is dropped here; the basis correction ships as v5.14.1 in the following commit. Notes are unhashed: the next-advance prediction is unmoved (frame-08 digest still ef5d5faf). Basis: DDD-dec-36; DDD-frame-08; term:accountability; DDD-hyp-04; DDD-dec-15 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Nt9JP3BvmfSuPfPHxQfvYt
The sequencing correction, per spec/release-format.md: v5.14.0 was cut before DDD-dec-36 reached the PR; descriptors are immutable once cut, so the filing ships as this patch. Content: the decision node and frame-08's notes pointer only; the v5.14.0 next-advance prediction stands unchanged. validate-releases: 11 descriptors valid. Basis: DDD-dec-36; DDD-frame-08 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Nt9JP3BvmfSuPfPHxQfvYt
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
2 participants
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.
The sequencing correction for #22: the GATE 5 ruling filed the accountability-arity ruling as a decision node, but #22 was merged — and
v5.14.0cut — before that commit reached the PR. A cut descriptor is immutable and corrections ship as a new version (spec/release-format.md), so this PR carries the filing plus the patch descriptor. Merging cutsv5.14.1.What this carries
core/decisions/DDD-dec-36— ruling C on theDDD-dec-15precedent: the two refused dispositions with their reasons, the test that separates the objects (an arrangement can instantiate the relation and still be incomplete — everyone knows who is responsible; nobody can sanction them), the Bovens lineage constraint as a governing decision (no file may claim more than authority linkage plus the change of tense), and the executed consequences.DDD-frame-08's notes gain the pointer to the decision that governs them. Notes are outside the instrumented fields: the digest is unchanged, and v5.14.0's published next-advance prediction (exactly one W6,cf73b307…→ef5d5faf…) stands exactly.releases/v5.14.1.yaml— patch, basisDDD-dec-36+DDD-frame-08, the divergence stated openly in the summary. v5.14.0 itself needed no content correction: the re-scoped claim, the demotions and the front-page repairs all landed in it and its basis resolves at its tag; what it lacked was the ruling's own node.The branch was restarted from main per the merged-PR rule; the original commit's now-illegal edit to the cut
v5.14.0descriptor is dropped, verified restored byte-for-byte from the tag.Validation
All gates green at head:
validate-releases.py11 descriptors valid; 13 decisions valid; 63 claims, 32 warnings (count unchanged);validate-core-order.py core/exit 0, zero W4.🤖 Generated with Claude Code
https://claude.ai/code/session_01Nt9JP3BvmfSuPfPHxQfvYt
Generated by Claude Code