Authority rows: the release-prep bump follows the family norm - #176
Merged
Merged
Conversation
The version-bump row's trigger now reads "a release bead the operator has named (in the campaign plan or their own words)", restating the file's Release preps paragraph: the bump is the family norm, not a grant a campaign consent has to name; its tag follows the tagging row once the prep is merged, and the publish stays the operator's (ruled by the operator, 2026-09-27). release.md and commit.md drop the consent condition they carried for the bump in the same words. The push/PR row's trigger says a human invoking /wurk:mr satisfies "the user asks for it in their own words", while a conductor, orchestrator or parent session invoking it needs the campaign's consent (ruled by the operator, 2026-09-29). Every other row is byte-identical. Refs: sui-nblt
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.
Rewords two rows of the authority table in
CLAUDE.mdand the two sentences in.claude/wurk/release.mdand.claude/wurk/commit.mdthat made the release-prep version bump wait on a campaign consent. Documentation and agent-tooling text only; no code, no version, no tag.The version-bump row (
CLAUDE.md)It said: trigger "an operator-authorized release bead, inside a campaign carrying the operator's explicit consent". It now says: "a release bead the operator has named (in the campaign plan or their own words); the bump is the family norm, not a grant a campaign consent has to name - its tag follows the tagging row once the prep is merged to
origin/main, and the publish stays the operator's". This restates the same file's Release preps paragraph (the bump and the tag of a release prep are the family norm; the prep lands on a named release bead; the tag once merged; publishing is the operator's) and the norm ruled by the operator, 2026-09-27. It grants nothing more: the forbidden cell is unchanged, and the tagging row and the publish row are untouched.The push/PR row (
CLAUDE.md)It said: trigger "the user asks for it in their own words". It now adds, in the shape statifier-ex's table already uses: "a human invoking
/wurk:mrsatisfies this, so the skill does not stop to ask again; a conductor, an orchestrator or a parent session invoking it on the user's behalf does not, and needs the campaign's consent". Ruled by the operator, 2026-09-29. The forbidden cell is unchanged; the wording clarifies who satisfies the existing trigger and grants nothing beyond it..claude/wurk/release.mdIt said the bump is authorized "only on" the old row's trigger, quoted with its consent condition. It now quotes the new trigger, "a release bead the operator has named (in the campaign plan or their own words)", with no campaign consent to name it. The next sentence already cited the Release preps paragraph; the publish sentence is unchanged.
.claude/wurk/commit.mdIt said the recipe "runs on an operator-authorized release bead". It now says it runs "on a release bead the operator has named". The tagging and publish sentences that follow are unchanged.
Review
In-turn review against the bead's acceptance:
git diff origin/main -- CLAUDE.mdchanges exactly two table lines, the push/PR row and the version-bump row, and only their trigger cells; every other row of the table is byte-identical (no other line of the file appears in the diff). A re-grep ofrelease.md,commit.mdandmr.mdfor "consent", "operator-authorized" and "authoriz" found no other sentence that makes the bump wait on a consent; the remaining hits are the publish sentences, which stay. Each new sentence restates the Release preps paragraph or the ruled push/PR wording in the file's own voice. No changelog fragment:changelog.d/README.mdexcludes documentation and agent tooling changes.Gate: full
mix qualitygreen on this tree before the commit.