Knowledge-only, no memory dual-write
Knowledge-only, no memory dual-write
Rule
When locking a durable preference, rule, or decision, write it to knowledge/ only. Do NOT also write it into the agent MEMORY.md auto-memory store. Single source of truth = knowledge/. The memory store may reference knowledge files but does not duplicate their content.
How to apply
- Lock a decision -> write
knowledge/<dir>/<slug>.md. Done. - Do NOT call any memory-write tool that would create a parallel record.
- If the harness offers to auto-memorize, decline / let the auto-memory link to the knowledge file rather than duplicate.
- Existing memory entries that duplicate knowledge are migrated to knowledge-only per
memory-to-knowledge-migration-2026-06-26. - Memory store reduces to: ephemeral session state + pointers to knowledge files (see
memory-mapping-by-type-field).
Why
User locked this on 2026-06-26 (Q16). Dual-write creates drift — the moment the two diverge, the agent must guess which is authoritative. One store, one truth.
Captured
2026-06-26 session, Q16 of 24-question grill.