compound

# Compound: durable project knowledge `compound` writes exactly two surfaces: - `docs/solutions/<category>/<slug>.md`: one learning per solved problem. - `CONCEPTS.md` at the repo root: one definition per project-specific term. It does not write memory files. User/preference facts are handed to `memory-update`. ## Reject-by-default gate A doc is earned, not assumed. All three filters must clear: 1. **Would I forget this?** Skip baseline knowledge anyone in this codebase already carries. 2. **Already covered?** Update an existing doc rather than duplicate it. 3. **Scope-qualified?** A repo-specific quirk qualifies; a general programming truth does not. If nothing clears the gate, say so in one line and exit. Never fabricate a doc. ## Mode routing Strip `mode:` tokens from `$ARGUMENTS`. | Mode | Trigger | What it does | |---|---|---| | **Solution** (default) | none | Document one solved problem → `docs/solutions/` | | **Vocabulary** | when a durable, reusable project term surfaces | Reconcile `CONCEPTS.md`: read `references/concepts.md` | | **Headless** | `mode:headless` | Non-interactive overlay on whichever mode is active | ## Writing a solution doc 1. Read `references/schema.yaml` and `assets/solution-template.md`. 2. Classify the problem: bug or knowledge track. 3. Check `docs/solutions/` for duplicates by grepping frontmatter (`title:`, `tags:`, `module:`, `component:`). 4. Write one file: `docs/solutions/<category>/<slug>.md`. 5. Run `python3 scripts/validate-...