product

Same Brain

Pillar ② · Memory. Recaps, shared prompts, MCP tools, and project knowledge.

What Memory is

Memory is the project’s shared brain. It holds:

  • Recaps. Every Thread that ends on any docked Node generates a one-paragraph summary — what the user wanted, which files were touched, what the outcome was. Anyone in the project can read it later, even if they weren’t around when it was running.
  • Prompts that worked. When a teammate’s prompt produced a good result, it lands in Memory for the rest of the team’s agents to use.
  • MCP tools the team built. Custom MCPs no longer live in one developer’s ~/.claude/; they live in the project, scoped to it, accessible to every docked agent.
  • Project memory. The agent’s understanding of the project — recent decisions, naming conventions, gotchas — accumulates in one place rather than per-machine.

v0.1 vs Phase 2+

The first deliverable is Recaps. Every Thread, every Node, every member: when a Thread ends, a summary lands in Memory and shows up on the project board. That alone changes how teams catch up on each other’s work.

The shared prompt / MCP / skill library follows in Phase 2 — it’s the part that depends on having enough material accumulated to be worth sharing. The architecture page for Memory has the full breakdown.

Why this matters more than it sounds

Without Memory, every developer’s agent starts cold. With Memory, the agent that joined yesterday is as informed as the one that has been on the project for six months. Onboarding becomes a problem of attaching a Node, not transferring tribal knowledge.

Where Memory lives

In v0.1, Memory is a SaaS-side store (Postgres + object storage). Project members read and write it through the Manifoldone API.

In Phase 2+, a .memory/ directory at the project root mirrors selected items so the project travels with its brain even when the SaaS is unreachable. Schema sketch:

project/
├── .memory/
│   ├── prompts/          ← shared prompt library
│   ├── mcps/             ← custom MCP tools
│   ├── knowledge/        ← accumulated project notes
│   └── skills/           ← reusable agent skills

The directory is committed to the project’s VCS so it lives next to the code.

Future: the marketplace

When teams produce especially useful prompts, MCPs, or skills, they can choose to publish them. Other teams can install them with the same command pattern that docks a Node. This is parked for Phase 3 — it depends on having a meaningful number of teams using Memory first.

Naming note

Memory was previously called “Aerepo” (Aether + Repo). We renamed it for clarity — Memory says what it does and lines up directly with this pillar’s name (Same Brain).