triage-stale-memorylisted

# Triage Stale Memory `CLAUDE.md` is the doctrine. This card is the executable procedure for one specific situation: **a session did real work in a memory-hook log but never recorded a lesson or decision for it**, so `amplify_context_load` ends its output with a stale-memory warning. Stale memory is the *second* shape of memory drift (the first is hallucinated write-success). Treat it the same way: nothing counts until Amplifier reads it back. ## When to use - `amplify_context_load` output ends with a stale-memory warning, OR - you suspect a previous session logged work to `~/.claude/memory/<date>.md` but forgot to persist any lesson/decision. ## Procedure 1. **Audit.** Run `amplify_audit_freshness` to get the exact list of stale memory days (files newer than the latest Amplifier write). 2. **Draft, don't record.** For each stale file, run `amplify_promote_from_memory_md({ memory_file: "<path>" })`. This **records nothing** — it returns DRAFT suggestions only. 3. **Classify each draft** into exactly one of: - **decision** — an architectural / tooling / process choice → record with `amplify_decisions({ op: "track", ... })`. - **lesson** — a mistake, insight, or confirmed fix → record with `amplify_learn(...)` (or `amplify_record_claim` if it is an *unverified* inference — see `record-verified-lesson`). - **discard** — noise, one-off, or already captured. Do nothing. 4. **Record only load-bearing items.** A draft is load-bearing only if