fix(gate): stop flagging exclusion rows and prose out-of-scope destinations as structural failures - #18
Open
beomeodev wants to merge 1 commit into
Open
Conversation
…ations as structural failures The structural checker (added with the 2026-07-19 three-layer adoption) rejected two conventions that predate it and passed every prior audit: - Commitment Index rows of type Exclusion carry an explicit "— (non-goal)" owner marker, not an owning Feature. The checker now requires the em-dash marker for Exclusion rows (empty owners still fail) while non-Exclusion rows keep the exactly-one-Feature rule. - Explicitly-out-of-scope destinations may be non-Feature prose (a successor PRD, a backlog, a frozen branch). The deterministic layer now checks only the arrow-and-named-destination form; destination validity stays with the Layer-2 semantic verifiers. Surfaced by spade-ace-backtester's /ms.expand (Amendment 2), where the legacy map — immutable inside that command — failed 14 index rows and 17 out-of-scope items that had passed the 2026-07-14 global audit. Co-Authored-By: Claude Fable 5 <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
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.
Summary
structuralchecker (2026-07-19 three-layer adoption) rejected two map conventions that predate it and passed every prior audit.Exclusionlegitimately have no owning Feature; the established convention marks them— (non-goal). The checker now requires the explicit em-dash marker for Exclusion rows (empty owners still fail); non-Exclusion rows keep the exactly-one-Feature rule.Context
Surfaced by spade-ace-backtester
/ms.expand(Amendment 2): the legacy map — immutable inside that command — failed 14 index rows and 17 out-of-scope items that had passed the 2026-07-14 global audit.Test plan
uv run pytest tests/specter/→ 224 passed🤖 Generated with Claude Code