wellmate-memory

Record durable facts like architecture decisions, locked systems, and rollback points in a dedicated memory file such as PROJECT_STATE.md. Before significant changes, read existing memory, compare it against current code, and update only when a durable fact changes.

Record architecture decisions, canonical data ownership, fragile subsystems, known regressions, dependency behavior, validation requirements, rollback points, and rejected approaches. Exclude temporary thoughts, trivial details, secrets, credentials, and facts trivially rediscoverable from code.

No. Memory never overrides source code or primary docs like CLAUDE.md. When memory conflicts with the repository, inspect the repository, resolve the discrepancy, and then update the memory to match verified reality.

Update memory after discovering an important failure by recording the root cause, the affected subsystem, the successful resolution, and the validation performed. Skip fixes that are trivial or do not change durable architecture facts.

Memory can drift from reality if not verified against the current code, and it cannot capture runtime validation that never occurred. It requires discipline to read before changes and honesty about unverified capabilities such as browser or native testing.