concept_gatelisted

# Concept Gate — self-learning working-method archive Apply this gate once at the END of any non-trivial task, immediately before declaring "done," alongside ADR Gate. Most tasks will not produce a concept — that is the correct and expected outcome. ## The bar is HIGH The default answer is: **no concept needed.** ADR Gate asks "does this decision need a record?"; Concept Gate asks "did I just execute or discover a reusable WAY OF WORKING — not a one-off decision, not a one-off bug fix — that would save real time if a future agent had it pre-loaded?" **Do NOT write a concept for:** - A single bug fix with nothing generalizable about it - A one-off tooling workaround - Anything already fully captured by an existing concept — amend that one instead - Anything a ≤8KB SkillForge skill snippet genuinely already covers on its own ## Write or amend a concept only when at least one holds 1. **Recurrence:** the same investigation/fix/verification SHAPE showed up across 2+ distinct tasks in ways that weren't already duplicated code. 2. **Generalizable structural fix:** a root-cause fix (not a symptom patch) generalizes beyond the one bug it closed, worth naming so the next similar bug gets the deep fix on the first pass. 3. **Decisive verification technique:** a live-VM proof, wheel-content inspection, deploy-then-curl-the-real-URL, or similar check caught something static analysis alone would have missed, and the same class of risk will recur. **Gut-check:** *"Would a future age