Summary

Memory, retrieval, and wiki synthesis solve different problems. Confusing them creates architectural mess.

Key points

• Memory preserves continuity, identity, durable preferences, and notable decisions.
• RAG / corp KB retrieves relevant source evidence at question time.
• Wiki synthesis stores working conclusions, comparisons, and evolving interpretations.

Operational relevance

A healthy stack uses all three:

• memory for continuity
• RAG for evidence lookup
• wiki for compounding understanding

The conflict appears only when the wiki starts pretending to be canonical truth.

Open questions

• What deserves promotion from chat or notes into the wiki?
• What stale-age thresholds make sense for fast-moving runtime pages?

Sources

• docs/FIT_ASSESSMENT.md
• wiki/sources/karpathy-llm-wiki-gist.md