Overview
What MAP is, what it is not, and the mental model that makes the rest of the documentation cohere.
MAP — the Multi-Agentic Protocol — is the institutional operating system for autonomous organizations. It is not an agent framework, not a workflow engine, not an identity standard. It is the substrate underneath all three.
The mental model
Every autonomous organization needs the same primitives: a way to verify who is calling, a way to enforce what they may do, a way to count what they used, a way to record what was decided. Building those primitives once per organization is wasteful and error-prone. MAP centralizes them into a single, auditable, treaty-capable mesh.
A request enters MAP. Eight stages happen, in this order:
- Version Resolution — pick the best version of the named protocol
- Context Enrichment — attach tenant, correlation, trace
- Rate Limiting —
ProductionRateLimitertoken bucket per tenant - Security Gating —
SecurityGateway::is_operation_allowedagainst the caller's capability set - Circuit Breaking —
ProductionLoadBalancer::is_availableon the target endpoint - Load Balancing —
ProductionLoadBalancer::select_endpointfor redundancy - Router Invocation —
ProtocolRouter::invoke(protocol, version, operation, input, &ctx) - Result Handling — audit pipeline, metric emission, response formatting
See MapEngine::handle_request for the canonical implementation.
Refusal carries reasons. When a request is denied at any stage, MAP returns a structured refusal with the same audit weight as success. Refusals are first-class records; they are not silences. This is enforced by AuditPipeline::record in engine/core/src/engine.rs.
What MAP is
- A protocol router: 35 named services, each implementing the
ProtocolModuletrait, dispatched through one engine. - A policy engine surface: every request is checked against
SecurityGatewaypolicies (hierarchical wildcards) before reaching a protocol module. - An audit substrate: every decision — allowed or refused — flows through
AuditPipelineinto structured tracing + metrics. - An economic primitive:
MEALmeters three dimensions (tokens, seconds, watts),MANAenforces runway,MADEsettles across organizations. - An interop surface: every protocol is exposed as an MCP tool; cross-organization calls run under
MOATtreaties; agent-to-agent messaging uses A2A envelopes throughMIM.
What MAP is not
- Not an agent framework. Building agents is Forge's job. MAP verifies what Forge signs.
- Not a workflow engine. Durable orchestration is Aut0 and Flowers. MAP records what Aut0 conducts via
MOONandMAX. - Not an identity standard. That is OAS — vendor-neutral W3C DIDs. MAP consumes OAS, never owns it.
- Not a DID resolver.
MACSverifies presented identities; resolution is delegated to the OAS adapter.
Three estates
Every service in MAP has a temperament that determines how it behaves:
Protocol
Stateless infrastructure. Routes, records, validates. No judgment. Same on Tuesday as Monday.
Agent
Itself an autonomous organization built on MAP. Reasons, dialogues, learns. Examples: MARC, MACE, MOOT.
Hybrid
Infrastructure by default — fast, cold, predictable. Invokes an agent only when ambiguity demands it.
See Three Estates for the full taxonomy. The classification matters because it controls SLA expectations, metering behavior, and what kind of capability is required to invoke.
Seven planes
Services are grouped into seven functional planes. The planes are functional, not ranked.
| Plane | Question | Services |
|---|---|---|
| I — Identity | Who are you, what can you do | MACS, OAS, Arsenal, Aegis |
| II — Cognition | What do you know, what can you reason about | MIND, MARC, MANTLE, MAME |
| III — Truth | What is verified, what is trusted | MAVEN, MATA, MARE, MERIT, MANTIC, MAGI |
| IV — Governance | How decisions are made and enforced | MOAT, MAXIM, MACE, MOOT, MIMESIS, MAUSOLEUM |
| V — Execution | How work gets done | MOON, MAESTRO, MAT, MAKER, MOTE, MAGE |
| VI — Economic | How value flows | MADE, MARKET, MANA, MEAL |
| VII — Awareness | How the institution sees itself | MAX, MOTIF, MOMENT, MOTET, MARS, MAZE, MARI, MIM |
See The Seven Planes for the per-plane briefings.
The legitimacy loop
With protocols come processes. From processes come workflows. From workflows come factories.
Every successful dispatch through MAP adds a record. Records that recur across requests become processes. Processes that prove themselves become workflows other organizations adopt. Workflows that stamp out new organizations become factories — and the institution funds the next institution.
This is the legitimacy loop. It is not a slogan; MIMESIS watches the audit chain for recurring patterns and proposes formalizations through MAXIM. MAUSOLEUM archives organizations that dissolve, preserving their precedent. The institution learns by doing.
Reading the docs
- Reference docs quote the actual code: type names, function signatures, operation strings. If a doc page says
MACS::auth_negotiation, that operation exists inprotocols/macs-lib/src/lib.rs. - Conceptual docs explain the mental model behind the code. They cite specific files so you can drop into the implementation when ready.
- Recipe docs demonstrate full workflows that span multiple protocols. They are extracted from
DEFAULT_RECIPES.mdin the repo. - Agent-targeted docs (
/llms.txt,/llms-full.txt, the agents section) are machine-readable and built for autonomous consumption.
When two pages conflict, the code wins. File an issue at map@l1fe.ai with both URLs.