MAP Docs
Concepts

Planes

Functional domains, not ranked. Identity, Cognition, Truth, Governance, Execution, Economic, Awareness.

Services are grouped into seven functional planes. The planes are functional, not ranked — Identity is not "more important" than Awareness. They are seven categories that together describe everything an institution needs.

I — Identity

Who you are. What you may do.

The first question MAP asks of every caller. Identity verification and capability derivation happen before any other plane fires.

ServiceKindRole
MACSHybridThe single port of entry. Verifies signatures, derives capability sets.
OASAdapterVendor-neutral W3C-DID identity standard.
ArsenalAdapterAgent Capability Tokens, credential proxy with SSRF guard.
AegisAdapterChallenge-response auth, key management, delegation trees.

The single MAP service in this plane is MACS. The other three are external standards MAP consumes through adapters.

II — Cognition

What you know. What you may reason about.

Substrate and faculty for thought. Cognition services hold the institution's memory and reasoning capacity.

ServiceKindRole
MINDHybridThe cognitive substrate. 4 memory types, HNSW search, knowledge graph.
MARCAgentHierarchical reasoning, causal analysis, model publishing.
MANTLEHybridPerception, consolidation, EWC continual learning.
MAMEAgentMeta-learning. Curatorial edits to MIND with provenance.

III — Truth

What is verified. What is trusted.

The institution's ledger of confidence. Truth services evaluate claims, weight sources, score reliability.

ServiceKindRole
MAVENAgentEvidence verification via GLYPH. Claims-as-graphs, contradiction preservation.
MATAAgentBayesian opinion pooling across heterogeneous sources.
MAREHybridReputation built from outcomes. Stake-weighted, decay over time.
MERITAgentComposable credentials from verified history. Selective ZK presentation.
MANTICAgentCalibration scoring, reliability budgets, uncertainty quantification.
MAGIAgentMechanistic interpretability. Activation tracing, feature attribution.

IV — Governance

How decisions are made. How they bind.

Governance services are how the institution decides — not reasons, decides. The line between MARC (thinking) and MACE (ruling) lives here.

ServiceKindRole
MOATProtocolTreaty-based federation. Two charters meeting at a boundary.
MAXIMAgentConstitutional reasoning. Mandate interpretation and enforcement.
MACEAgentConsensus voting. Quorum-driven deliberation; dissent on record.
MOOTHybridDispute resolution & arbitration. Binding rulings recorded forever.
MIMESISAgentConvention, custom, precedent. Slow accretion of common law.
MAUSOLEUMAgentDissolution. Archive. Succession of obligation.

V — Execution

How work gets done. How it stays done.

Execution services are the institution's hands. They reach out to tools, devices, and durable workflows.

ServiceKindRole
MOONAgentDurable orchestration via Flowers. Manifests, deployments, replay.
MAESTROAgentCharter declaration, goal refinement, plan commit/diff/replan.
MATProtocolTool dispatch, discovery, workflow execution.
MAKERAgentKinetic action with emergency stop. Native/MCP/A2A/HTTP unified.
MOTEHybridSensors, actuators, vehicles, fabrication. Physical-world bridge.
MAGEAgentGeneration engine via ONE/MUSE. Drafts charters, treaties, blueprints.

VI — Economic

How value flows. How it settles.

Economic services let the institution earn, spend, and clear. MEAL meters; MANA budgets; MARKET trades; MADE settles.

ServiceKindRole
MADEProtocolSettlement layer. x402, multi-rail, basis-point clearing.
MARKETAgentOrderbooks, auctions, bounties, trades.
MANAAgentNegotiation, arbitration, treasury. Bidding, reputation, arbitration channels.
MEALHybridMetering. Tokens · seconds · watts. Triple-entry ledger.

VII — Awareness

How the institution sees itself.

Awareness services let the institution observe itself. Every audit record, every metric, every relationship, every research finding flows here.

ServiceKindRole
MAXProtocolThe constitutional record. Hash-chained, replayable, queryable.
MOTIFProtocolPattern detection across traces and audit.
MOMENTProtocolTime-series. Append-only, monotonic, time-travel queryable.
MOTETProtocolMulti-stream telemetry. Logs, metrics, traces, attestations.
MARSProtocolUniversal registry. Every asset of standing.
MAZEAgentTopology + ZK proofs of structural properties.
MARIAgentResearch & inquiry. Literature synthesis, hypothesis testing.
MIMProtocolMessaging. Mailbox semantics. QoS.

How planes interact

Every successful dispatch produces a record. Records record decisions; decisions reference identity, evidence, policy, treasury. Cross-plane references are the rule, not the exception. A typical MARC reasoning call:

  1. Identity: MACS verifies the caller (Plane I)
  2. Cognition: MIND snapshot bound for reasoning (Plane II)
  3. Truth: MAVEN attestation on every premise (Plane III)
  4. Governance: MAXIM policy bound; MACE may be invoked if the verdict is structural (Plane IV)
  5. Execution: MAT invoked if reasoning recommends a tool (Plane V)
  6. Economic: MEAL meters the call; MANA enforces runway (Plane VI)
  7. Awareness: MAX records; MOTET traces; MOMENT tracks latency (Plane VII)

The legitimacy of the verdict comes from every plane firing in support. A reasoning result without an audit chain is not a verdict — it is a guess.

On this page