Memory -> knowledge migration plan

decision Fri Jun 26 2026 00:00:00 GMT+0000 (Coordinated Universal Time) decisionknowledge-bundlememorymigration

Memory -> knowledge migration

Decision

Migrate every durable entry in C:\Users\C5420321\.claude\projects\C--d-oriz\memory\MEMORY.md (and per-topic memory files) into proper OKF knowledge files under knowledge/. After migration, MEMORY.md retains only:

• ephemeral session state (current task, scratch notes),
• pointers to knowledge files (one-liners with links, not duplicated content).

Why

User locked this on 2026-06-26 (Q17). MEMORY.md had grown into a parallel database of decisions — exactly the dual-write antipattern that knowledge-only-no-memory-dual-write forbids going forward. One-shot migration is cleaner than gradual.

How to apply

• Sibling agent owns execution (task #48 in TaskList).
• For each MEMORY.md bullet: determine type field (rule / decision / service / glossary / etc.), route to correct knowledge/<type>/<slug>.md per memory-mapping-by-type-field.
• Preserve supersession chains — if memory bullet says "SUPERSEDED 2026-06-25 by X", the new knowledge file gets superseded_by: and the superseding file gets supersedes:.
• After migration, MEMORY.md is rewritten to pointer-only form.
• One commit for the migration: docs(knowledge): migrate MEMORY.md -> knowledge/ (N files).

Captured

2026-06-26 session, Q17 of 24-question grill.

Related

• knowledge-only-no-memory-dual-write
• memory-mapping-by-type-field
• hierarchy-add-log-concepts-playbooks-2026-06-26