Define the carve-changesets operating contract - #39
Merged
Conversation
## Summary - Define the changeset model and preserved decomposition rules - Establish truth promotion, terminal states, and explicit authority levels - Bound the review, PR-lifecycle, propagation, safety, and interoperability seams ## Why - Give every remaining epic child one normative greenfield contract - Keep proposal state ephemeral while making git and GitHub authoritative
## Summary - Enumerate reusable chain validation evidence for `prs_open` - Keep the local-only no-publication condition scoped to `chain_ready` - Preserve the distinction between materialized and published terminal states ## Why - Remove a contradictory terminal-state requirement found by repository review - Let downstream implementations report publication deterministically
Closed
10 tasks
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.
TL;DR
Defines the normative
carve-changesetscontract that the remaining #28 implementation children will follow.Summary
plan_ready,chain_ready,prs_open,all_merged, andblockedterminal states with candidate-bound evidence.review-code-changeandbabysit-prseams while keeping decomposition and propagation ownership here.Non-goals
SKILL.mdauthoring.skills/prepare-changesetsreference implementation.Validation
just lint— pass.just format— pass.just lint-md— pass.just test— pass (179 unit tests plus 2 eval cases).git diff --check— pass.review-code-change— clean atedeb2f5f5f7b4cfa4e73e8289d34157b192f92abversus4570e9093fdce85eeec90e62869f02b9104cf1d2after one correctness fix/re-review cycle.Issue #29 has an explicit, issue-only exception to the repository-wide candidate
just lintgate: clean-basejust lintplus candidatejust lint-md,just test,just format, andgit diff --checksatisfy validation for this intentionally incomplete pre-packaging child. Full candidatejust lintwould require the futureSKILL.mdthat #29 explicitly forbids and a later child owns. This exception authorizes noSKILL.md, script,justfile/lint-discovery, frozenprepare-changesets, sibling, ticket-body, dependency-graph, manual-transition, parent-close, deployment, production, or destructive changes.Tickets
Fixes #29