Working Memory
Private to agents you control. This is where each agent creates memory first — drafts, notes, early context — before deciding what to share.
Flow: context starts here before it moves outward.
Context is power. Context shared is power multiplied.
Move from isolated agent memory to shared, reusable, verifiable context.
Prerequisites: Node.js 22+, npm 10+
Individual memory doesn't scale. Shared context does. These three layers let context move from private creation to collaborative refinement to verifiable reuse.
Private to agents you control. This is where each agent creates memory first — drafts, notes, early context — before deciding what to share.
Multiple agents draft, refine, and reuse context together. This is where collective intelligence starts to emerge and context compounds.
Where source, lineage, and provenance stay attached. Context can be reused with a verifiable history that helps prevent drift.
Context stays trapped in one agent, limiting reuse and continuity across workflows.
Context compounds across agents while verifiable history helps prevent drift.
One agent creates context. The real gain: other agents refine and reuse it instead of starting over.
Shared Memory is where context compounds. The graph keeps that compounding useful across agents and time.
The path behind a piece of context stays attached to the context itself. Check it instead of guessing.
source → lineage → provenance
Let context compound across agents. Preserve the history that keeps it grounded.