Agentic Team Protocol

What it is

The Agentic Team Protocol (ATP) is a lightweight operating model for running small, structured agent teams inside Claude Code. It defines clear roles, a seven-stage goal lifecycle, and durable memory records stored in eden-memory.

Seven-stage lifecycle

1. Intake and triage — capture the request, decide whether to accept it.
2. Scoping and charter check — verify boundaries and authority.
3. Research and options — evaluate approaches.
4. Dispatch and planning — assign to the right role.
5. Execution and verification — build and review.
6. Escalation (if needed) — route blocked or risky goals upward.
7. Recording and archival — close the loop in memory.

Default roles

Role	Responsibility
Dispatcher	Decides what gets built and who does it.
Researcher	Investigates options and writes decision-ready reports.
Builder	Implements the chosen approach.
Runtime	Executes operational actions — gated by default.
Verifier	Reviews correctness, safety, and charter compliance.
Archivist	Records the goal lifecycle and manages memory hygiene.

Runtime is not active unless your project charter explicitly authorises it.

What you need

• eden-memory installed and on your PATH.
• Claude Code CLI (the protocol is implemented as global agents and slash commands).
• Optionally, the eden-team binary for headless, non-interactive goals.

Quick install

Install eden-memory first, then install the ATP global primitives:

curl -fsSL https://0d3sa.com/eden-memory/install.sh | sh
curl -fsSL https://0d3sa.com/agentic-team-protocol/install.sh | sh

In each project where you will use ATP, wire the Eden-memory MCP server before restarting Claude Code:

cd ~/my-project
eden-memory setup claude

Then restart Claude Code completely (/exit, then reopen). The agents and commands will be available in every workspace.

See the getting started guide for the manual install path and project-local charter setup. Read the charter anatomy, lifecycle, and agent prompts for the full protocol reference.

How it uses eden-memory

The protocol does not replace eden-memory; it stores every milestone in it.

• /team-charter reads .claude/agentic-team-charter.md, computes a SHA-256 version hash, and writes a charter_ratification record to eden-memory.

• Every role uses the eden-memory MCP tools (eden_remember, eden_recall, eden_search, eden_search_semantic, eden_edit, eden_forget, etc.) to read prior context and store new records.

• Required record kinds link the lifecycle together:

  Kind	Stage	Owner	Purpose
  goal_record	goal_receipt	dispatcher	Initial request and constraints.
  dispatch_instruction	routing_and_assignment	dispatcher	Who does what, by when.
  context_summary	context_gathering	researcher	Findings and options considered.
  action_record	action	builder / runtime	What was done and how to roll back.
  verdict	verification	verifier	Green, red, or blocked assessment.
  escalation_record	escalation	dispatcher	Authority or guardrail request.
  charter_ratification	charter_ratification	archivist	Project charter approval.
  archival_record	recording_and_archival	archivist	Final outcome and links.

Each record should include metadata fields: goal_id, stage, owner_role, input_record_ids, output_record_ids, and recalled_memory_ids.

When recalling memory, only treat results with a score ≥ 0.45 as relevant, and record the IDs of memories that shaped the record in recalled_memory_ids.