thalarch-compoundlisted

# Thalarch Compound A completed task may contain knowledge worth keeping. Compounding is the **post-task learning gate**, not automatic persistence. ## 1. Candidate lesson A lesson qualifies only if: - supported by evidence from this run; - likely to matter again; - not obvious from ordinary code reading; - stable enough to outlive this task; - compact enough to retrieve without flooding future context. Examples: - a hidden build/test prerequisite; - an ownership/lifecycle invariant; - a recurring integration contract; - a reliable diagnostic command; - a repository-specific convention; - a failure pattern and its proven discriminator; - a benchmark/teacher finding that generalizes beyond one case. ## 2. Distill through experience For meaningful outcomes, use `thalarch-experience` to convert the final evidence ledger into a compact card: `trigger → context → problem → discriminator → intervention → evidence → transfer → counterexample`. Preserve useful disproven approaches when they prevent a realistic future mistake. Do not preserve the debugging transcript or private chain-of-thought. ## 3. Classify memory Pass the distilled candidate through `thalarch-memory`: - `IGNORE` — weak, obvious, duplicate, noisy, or non-reusable; - `SESSION` — useful only to finish/recover the current task; - `PROJECT` — durable repository/product knowledge; - `GENERAL` — transferable engineering knowledge with a strong generalization basis. A single successful anecdote should not au