Repository navigation
docs: qualify the brief.outputs rule so it agrees with the change_set exclusion (#338) - #494
Merged
Merged
Conversation
… exclusion (#338) DESIGN stated both that execute.request.brief.outputs contains this movement's declared outputs and, in §5, that the declared change_set is excluded from it. §2 rule 15 makes a change_set a declared output of every repo_write movement, so the general sentence was false for every write movement. The exclusion is the specialized contract and is right; the general sentence now reads "…declared outputs other than the core-synthesized change_set, which §5 excludes." One sentence changed, same bullet, same marker id (execute-brief.outputs) re-supplied as a changed anchor. The clause-staging ledger is regenerated with cmd/partitur-spec-regions from the pre-edit blob with that one anchor as the delta: 2718 of 2719 anchors and every non-normative range byte-identical apart from a +65 offset shift, the 33-region universe line-identical, activation valid. Baseline pins for regions 6-33 re-emitted; the docmarker carrier hash that pins this bullet's prose is updated. No Go behaviour changes: adapterkit already skips change_set when rendering the brief. Produced by a Partitur run (claude writer, eight acceptance criteria including go test ./...). The codex verifier attempt died on an adapter stream protocol error before reviewing; the operator reproduced the ledger regeneration from the writer's delta and found it byte-identical. 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.
Closes #338.
DESIGN stated both that
execute.request.brief.outputscontains this movement's declared outputs and, in §5, that the declaredchange_setis excluded from it; §2 rule 15 makes achange_seta declared output of everyrepo_writemovement, so the general sentence was false for every write movement. Per the issue's verdict the exclusion is right and the general sentence is qualified: "…declared outputs other than the core-synthesizedchange_set, which §5 excludes." One sentence, same bullet, same marker idexecute-brief.outputsre-supplied as a changed anchor.Ledger. Regenerated with
cmd/partitur-spec-regions -regenerate -emit-pins -classification-deltafrom the pre-edit blob with that single anchor as the delta: 2718 of 2719 anchors and all 1621 non-normative ranges byte-identical apart from a +65 byte shift; 33-region universe line-identical;-check-activationvalid. Baseline pins for regions 6–33 re-emitted;internal/docmarker's carrier hash for the block containing this bullet updated.go test ./...green. No Go behaviour change (adapterkitalready skipschange_setin the brief).How it was produced. A Partitur run: claude writer, eight acceptance criteria. Two verifier attempts on the codex adapter failed before reviewing — one on a vendor "model at capacity" error, one on an adapter stream
protocol_errorthat Partitur treats as movement-terminal without trying the cast fallback (filed separately). The operator therefore reproduced the regeneration from the writer's delta against the pre-edit ledger and found it byte-identical, and ran the doc suites.🤖 Generated with Claude Code