thalarch-experiencelisted

# Thalarch Experience Experience is the bridge between **what happened once** and **what may help next time**. The output is not a diary and not chain-of-thought. It is a compact evidence-backed engineering card. ## 1. Activation gate Extract an experience only when the task produced at least one non-obvious reusable result: - a root cause with a useful discriminator; - a failed approach that looked plausible and should be avoided under similar conditions; - an ownership/lifecycle/state invariant; - a measured optimization mechanism; - a migration/deprecation lesson; - a product/design rule proven by actual acceptance evidence; - a repeatable diagnostic or operational workflow. Skip routine edits, formatting, obvious compiler fixes, and task-specific details unlikely to recur. ## 2. Evidence-first extraction Start from the final evidence ledger, not from the producer's narrative. Separate: - `OBSERVED` — direct repository/runtime/test/benchmark/visual evidence; - `MECHANISM` — causal explanation supported by the evidence; - `DISPROVEN` — plausible alternatives contradicted by evidence; - `TRANSFER` — conditions required for reuse; - `UNKNOWN` — unresolved surfaces that must not be smuggled into the lesson. A successful patch is not by itself proof that every explanation offered during debugging was true. ## 3. Experience card Use this schema: ```text ID: stable local identifier DOMAIN: e.g. android-media3 / kotlin / sql / ui / ci TRIGGER: symptom/task pattern th