learning-capturelisted

# learning-capture — voidcorp craftsman edition One intent — *capture a lesson before its context evaporates* — with three destinations. This skill replaces the former `compounding` + `capture-rule` + `harness-evolution` trio, which were three doors to the same action separated by ~200 lines of mutual boundary-policing. Here the first step is the routing decision; the three behaviors follow unchanged, each keeping its own strict Human-In-The-Loop gate. It writes nothing on its own. It names the lesson, decides where it belongs, and runs the matching capture — proposing every write and waiting for an explicit yes. **Attribution**: see `.source` (inherits compounding, capture-rule, harness-evolution). --- ## Step 0 — Recognize the signal (auto-trigger) Engage the moment any of these appears — you should not need to be asked: - **A stated rule** — imperative future ("always X", "never Y", "from now on Z"), a preference ("we don't do Y here", "I prefer X"), an anti-pattern callout ("stop doing Y"), or a memory request ("remember that Z", "n'oublie pas que"). - **A recurring / deja-vu fix** — mid-work you catch yourself solving something *already seen*. That recognition means a pattern exists and was never captured. - **An end-of-cycle pattern** — a feature, bugfix, or refactor just merged; before the next task, spend two minutes extracting the reusable lesson. - **A harness gap** — "the harness should have caught this", a skill is missing, a rule is wrong, a hook false-pos