decision-extraction

# Decision Extraction ## Purpose / When to Activate Activate after: - Discovery produces epics, scope clarifications, or priorities - Delivery resolves technical trade-offs or architectural constraints - QA surfaces systemic issues requiring policy decisions - Product direction materially changes Do NOT use for trivial steps, implementation details, brainstorming, or reversible micro-choices. --- ## Process 0. **Decision Consistency Gate (mandatory).** Before extracting any new decision: - Read `contexts/memory/index.md` → scan the Decision Registry by domain to identify relevant existing decisions - Load the specific `decisions/DEC-{ID}.md` files for decisions in the affected domain(s) - Verify the proposed decision does NOT contradict any active decision - If contradiction found: either explicitly supersede (set `superseded_by` in old file + `supersedes` in new file) with rationale, or STOP and escalate to human. <!-- Impact list added before escalation to give the human full ripple-effect context at decision time. Prevents escalations that lack scope — the human needs to know what else references the contradicted decision before resolving it. Drift prevention. --> **When escalating due to contradiction:** before surfacing the escalation, grep `contexts/` for all occurrences of `DEC-{id}` (where `{id}` is the contradicted decision's ID). Collect every file path that references the contradicted DEC — memory files, sto...