Ology

The Shared Mind Problem

Designing shared memory for multi-user, multi-agent environments with privacy, access control, provenance, conflict resolution, retrieval

5 sessions · 16 readings · 1 view

Curated by Ben Lorenzo

Context Is a Budgetsession 1Crossing the Context Windowsession 2Private Notes, Shared Statesession 3When Memory Disagreessession 4Coordination Without a Single Mindsession 5

Opening

Shared memory is becoming an infrastructure problem rather than a feature. Agents now work across sessions, tools, teammates, repositories, and organizations; they inherit context from previous runs and increasingly leave durable records for whoever—or whatever—comes next.

That shift changes what “memory” means. A useful system must decide what belongs to a private conversation, a team workspace, or a global knowledge base; what should be remembered, revised, or forgotten; and how much of an agent’s reasoning should remain visible to others. Recent engineering accounts from Anthropic, OpenAI, and Hugging Face show that these decisions are already shaping production systems.

The hard cases are not simple recall. They involve stale facts, contradictory observations, hidden permissions, uncertain provenance, and context that must remain useful over hours, months, or years. A compact summary may be cheaper than replaying a trace, but it can erase the evidence needed to understand how a decision was reached.

The five sessions follow memory from context management to long-horizon continuity, from private state to shared organizational knowledge, and finally to coordination among agents with different goals and beliefs. The central question is: what kind of memory can support collective intelligence without turning shared context into a source of hidden error, leakage, or institutional confusion?

Five questions worth arguing about

  1. 1Should agent memory be treated primarily as curated context, or as a persistent record of experience?
  2. 2What should survive when an agent crosses context-window, session, or personnel boundaries?
  3. 3Can shared memory remain useful without collapsing private context and organizational knowledge into one unsafe store?
  4. 4How should a memory system represent disagreement, uncertainty, provenance, and changing facts?
  5. 5Do multi-agent systems need shared memory to cooperate, or can coordination remain mostly conversational and transactional?

The Sessions

1Session 1start here

Context Is a Budget

The problem

The first design mistake is to treat memory as a storage layer added after the agent loop. Anthropic’s account of effective agents instead places memory alongside tools, retrieval, and planning as part of an augmented language model. Its recommendation is deliberately conservative: begin with the simplest architecture that works, then add autonomy and orchestration only when they improve measured outcomes.

But Anthropic’s later context-engineering account makes the constraint sharper. Context is finite, dynamic, and continuously competing for attention. The relevant question is not how much information can be stored, but which small set of signals should enter the model at a particular moment. Just-in-time retrieval, structured notes, compaction, and subagents are different answers to that selection problem.

OpenAI’s harness-engineering experience offers a complementary systems perspective. Rather than placing all institutional knowledge in one giant instruction file, the team made a small map point toward structured sources of truth. The disagreement is important: should memory be a compressed narrative, a navigable knowledge base, or a set of raw artifacts? The next session asks what happens when the agent must cross not just a context boundary, but a time boundary.

2Session 2Crossing the Context Window3 readings3Session 3Private Notes, Shared State3 readings4Session 4When Memory Disagrees3 readings5Session 5Coordination Without a Single Mind4 readings
The Shared Mind Problem · Ology