Repository navigation
refactor: govern delivery with Epic plans and human approvals - #48
Merged
Merged
Conversation
mattias-modernpath
force-pushed
the
feat/epic-approval-process-cleanup
branch
from
October 19, 2026 17:21
f0eb651 to
91d5010
Compare
mattias-modernpath
marked this pull request as ready for review
October 19, 2026 17:22
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.
Requirement changes previously depended on file-backed ledgers, fingerprints, generic gates and selection/receipt protocols. Replace those models with saved Epic plans, exact proposed requirement content and explicit human implementation/completion approvals, aligned with ModernPath/modernpath-v1 PR #936 at
651f9a69c9b454635de48911d1227fcd5131a124.Implementation approval atomically reserves requirements for one user and Epic. Active approved plans and owned content remain read-only through implementation and review; new scope is recorded separately. Completion atomically publishes accepted content, increments revisions, retains immutable versions and audit, and releases ownership.
Reverse engineering records native PROPOSED requirements and typed source-file traces directly. Repository/path identifies a source; revision is descriptive. Remove baseline/DERIVED modes, immutable source captures, authorization runs, publication groups and the retired mp-process-cli dependency. Verification records genuine criterion-level evidence without changing lifecycle. Separate explicit human acceptance can atomically publish verified, unowned existing behavior from PROPOSED to DONE without an implementation Epic. Behavior or test changes follow normal Epic delivery.
All 20 shared Markdown files match the process package currently embedded in PR #936. Preserve the canonical audit scripts and tests. Remove file-state templates and the retired context-worker reference; restore the existing-behavior acceptance skill.
Validation:
node --test skills/rdd-audit/audit-citations.test.mjs: 15 passed.git diff --check: passed.This changes shared agent/process instructions and is repository meta-work; the product-delivery loop does not apply. Product implementation remains in PR #936. The embedded source revision in that PR still needs repinning through its normal packaging workflow to this canonical source before release. No merge, CLI release, deployment or completion approval is included.