thalarch-memorylisted

# Thalarch Memory Memory is a **retrieval aid**, not an authority layer. Current user/repository/runtime evidence wins. Core invariant: **current repository/runtime evidence wins over retrieved memory**. ## 1. Four memory classes Classify every candidate before persistence: - `IGNORE` — task noise, obvious facts, duplicated information, weak guesses, transient logs; - `SESSION` — useful only for the active task/session; keep in the evidence ledger, not durable storage; - `PROJECT` — stable knowledge specific to one repository/product, such as invariants, commands, architecture decisions, regressions, design rules, or integration contracts; - `GENERAL` — transferable engineering knowledge that is useful beyond one repository. Do not promote a memory merely because it was expensive to discover. ## 2. Authority and freshness Retrieved memory has trust level `MEMORY` until checked. Before a memory drives a load-bearing decision: 1. identify what current fact it predicts; 2. verify that fact against current repository/runtime/primary-source evidence when practical; 3. compare project/version/environment scope; 4. reject or retire the memory if current evidence contradicts it. A stale project memory must never override current source, manifests, tests, dependency versions, or runtime observations. ## 3. Persistence gate Durable persistence requires all of the following: - the lesson is useful again; - evidence and provenance are recorded; - scope is explicit; - tran