fix: exclude excellence proposals from compiled briefs - #21
Merged
Conversation
Close the remaining WOR-62 downstream gap: EXC-* proposal IDs are not authoritative source scope. Planning and the brief compiler now fail closed instead of compiling deferred or rejected excellence text. Co-authored-by: Ldsystem <Ldsystem@users.noreply.github.com>
Ldsystem
marked this pull request as ready for review
August 30, 2026 08:33
# Conflicts: # references/evals/orchestration/evals.json
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.
Summary
Independent review of merged PR #20 found a remaining WOR-62 gap: the specification-stage excellence scan was present, but planning and the brief compiler still treated
EXC-*proposal IDs as ordinary source IDs. A deferred proposal recorded as- **EXC-001**: ...could compile into executorrequirements.This change binds the already-accepted exclusion at the downstream boundary:
orch-create-implementation-plancompiles only verified authoritative scope and does not allocateEXC-*or rejected/deferred/not-material proposalsEXC-*source IDs and omits proposal records from source extractionAccepted excellence work still enters planning only through the stable REQ/CON/API/AC/TEST IDs it projected to.
Validation
test_build_task_brief_fails_closed_for_excellence_proposal_source_idcompiled successfully before the compiler changebin/work-bundle-skill validate: okebd8e59c4e90e9b24571550e4bc2d6d20139a314Linear: WOR-62
Linear Issue: WOR-62