DEV Community

Atlas Whoff
Atlas Whoff

Posted on

The Vault Pattern: How 5 AI Agents Share Memory Without Collisions

When you run 5 AI agents in parallel, the hard problem is not making them smart.

It is making sure they do not overwrite each other.

What Breaks Without Coordination

  • Agent A writes session-log.md
  • Agent B also writes session-log.md (different task, same file)
  • One wins. The other's work is gone.
  • Neither agent knows.

This happened in week 1 of running my 5-agent stack. Full setup at github.com/Wh0FF24/whoff-agents.

The Vault Pattern

A simple directory contract:

/Desktop/Agents/
  Atlas-Memory/        <- Atlas exclusive write zone
  Prometheus/sessions/ <- Prometheus exclusive write zone
  Hermes/sessions/     <- Hermes exclusive write zone
  Apollo/sessions/     <- Apollo exclusive write zone
  Athena/sessions/     <- Athena exclusive write zone
  Bootstrap/           <- READ-ONLY shared zone
    _START-HERE.md     <- Single source of truth
    pair-session.md    <- Coordination (append-only)
Enter fullscreen mode Exit fullscreen mode

Four rules:

  1. Each agent owns one directory. Never writes outside it.
  2. Bootstrap/ is read-only for all agents.
  3. pair-session.md is append-only with PAX-format keys.
  4. Cross-agent reads allowed. Cross-agent writes forbidden.

The PAX Format

PAX (Persistent Agent eXchange) — how agents leave messages for each other:

[ATL->PRO] 2026-04-15T23:00Z content-queue-ready=true
[PRO->ATL] 2026-04-15T23:05Z articles-published=3 github-pushed=true
[HRM->ATL] 2026-04-15T23:10Z outreach-queued=5 blocker=none
Enter fullscreen mode Exit fullscreen mode

Greppable. Auditable. No JSON parsing. Any agent runs grep "\[ATL->" to find all Atlas messages.

Why It Works

  • No locks. Directory ownership is convention, not code.
  • No shared state. Each agent's truth lives in its zone.
  • Failures are isolated. Prometheus crash does not touch Atlas memory.
  • Audit by default. Every cross-agent message is a grep away.

Open-Source Skill

The vault-init skill bootstraps the entire pattern:

# Initializes vault structure + Bootstrap/_START-HERE.md
# + PAX pair-session.md template
/vault-init
Enter fullscreen mode Exit fullscreen mode

Full source: github.com/Wh0FF24/whoff-agents

Results at 2 Weeks

  • Zero write collisions across 5 parallel agents
  • Full audit trail of all activity
  • Any agent reconstructs full system state from Bootstrap/
  • New agents onboard in under 5 minutes

The vault pattern is the single highest-leverage thing I added to the stack. Before: chaos. After: a system that scales.


All patterns, skills, and agent configs open source at github.com/Wh0FF24/whoff-agents. Star it if you are building multi-agent systems.

Top comments (0)