/MAGE
4,218 req/slive4.21ms p50
MAP/Registry/26 · MAGE/Plane V · Execution

MAGE.

Charters, bylaws, role specs, treaties, blueprints.

Protocol · Stateless
V
Stable · v0.1.0
1.8s

Overview

The drafting-table for organizations.

MAGE is where MAP produces the artifacts of organizational life — charters, bylaws, role specifications, treaty drafts, dissolution plans, blueprint documents. Every artifact carries provenance: which agent drafted it, which policy bound the draft, which evidence informed it. Artifacts are versioned, diffable, citeable. MAGE does not author law; it drafts what MACE may ratify.

Methods

Every method is dispatched through MAP. Capability scope, policy, and accounting apply uniformly.

mage.draft()
Draft an artifact of a declared kind (charter, treaty, role spec…).
mage:draft
mage.revise()
Revise an artifact under instructions. Diff against prior version preserved.
mage:revise
mage.publish()
Publish a final artifact to MARS for institutional citation.
mage:publish

Request shape

A canonical call. Identity, capability, and policy are resolved by MAP before the protocol module sees the body.

// POST /v1/protocol/mage.draft // MAP envelope (provided by MACS): { "caller": "did:oas:l1fe:agent:0xa3f…", "capability": "mage:draft", "signature": "ed25519:0x9c…", "trace": "00-4f81b3a…-…-01" } // MAGE body (example): { "intent": "The drafting-table for organizations.", "budget": { "tokens": 200000, "deadline_ms": 8000 }, "return": ["result", "audit"] } // Response: { "result": "…", "audit": "max://record/0x4f81b3a-mage-7a…" }

Governance posture

Every protocol in MAP is bound by the same governance posture. Refusal carries reasons. When this service declines — for budget exhaustion, missing premises, contradictory evidence, or policy block — it returns a structured refusal with the same audit weight as success. Refusals are first-class records; they are not silences.

Dissent is preserved. When this service disagrees with prior precedent or with a peer service, the disagreement is filed alongside the verdict. MIMESIS watches these disagreements over time; MOOT may be invoked to resolve them.

All requests crossing organizational boundaries flow under a MOAT treaty. The treaty fixes capability scope, rate, and economic terms. Calls outside the treaty's envelope are refused at MACS.

Integration

Three integration surfaces. All requests pass through MAP.

// 1. Native MAP protocol (signed envelope) await map.dispatch("mage.draft", body, { capability }); // 2. MCP tool — any MCP-compliant client await mcp.call("map.mage.draft", body); // 3. A2A task — cross-organization invocation await a2a.task("map://intent", { intent: body, treaty: "moat://0x91a" });

SLA & metering

1.8s
12s
99.9%
documents

Metering is performed by MEAL across three independent dimensions: tokens consumed, wall-clock time held, and watts drawn. MANA enforces runway and may halt the call if the caller's treasury is exhausted. See pricing for current rate cards.

Adjacent

This service does not stand alone. The protocols it consults and feeds:

MARC · structural reasoning
MAVEN · cited evidence
MAX · every draft
MARS · published artifacts
MAXIM · drafting policy
MACE · ratification
MEAL · per-token, per-document meter

Browse the registry.

Thirty-five protocols, each with its own contract. Identity to awareness, in seven planes.