Summary

A shared memory substrate and a compiled markdown wiki solve related but different problems. Mixing them up creates bad design choices.

Key points

• Shared memory is structured operational state that multiple agents can read and write.
• A compiled wiki is a human-readable synthesis layer for evolving judgments, comparisons, and explanations.
• Shared memory optimizes continuity and cross-agent state.
• A wiki optimizes understanding and reusable interpretation.
• Some systems need both.

Operational relevance

For Kalen’s stack, the wiki is a better first move for AI-dev research synthesis. A shared memory substrate becomes more compelling when the workflow needs structured entities, updates, and operational reads/writes across agents.

Open questions

• Where is the cut line between structured facts and markdown synthesis in future systems?
• Which pilot workflows would justify adding a true shared-memory substrate?

Sources

• wiki/sources/openbrain-shared-memory-pattern.md
• wiki/sources/ai-first-operating-model-from-voice-memo.md
• wiki/concepts/memory-vs-rag-vs-wiki.md