/MAME
4,218 req/slive4.21ms p50
MAP/Registry/08 · MAME/Plane II · Cognition

MAME.

Redaction with provenance, schema migration, knowledge correction with auditable lineage.

Protocol · Stateless
II
Stable · v0.1.0
45ms

Overview

Curatorial access to the substrate.

MAME is the curator of MIND. When knowledge must be corrected, redacted, migrated, or annotated, MAME holds the keys. Every edit carries provenance — who, why, and on whose authority. Schema migrations preserve historical reads through versioned views. Redactions leave a tombstone, never a silence. Meta-learning loops observe the consequences of edits and propose corrections to upstream models.

Methods

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

mame.edit()
Edit a memory cell with full provenance. Old value preserved as tombstone.
mame:edit
mame.redact()
Redact a memory under policy authority. Leaves an auditable tombstone, never silence.
mame:redact
mame.migrate()
Schema migration with versioned views. Historical reads continue under old schema.
mame:admin

Request shape

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

// POST /v1/protocol/mame.edit // MAP envelope (provided by MACS): { "caller": "did:oas:l1fe:agent:0xa3f…", "capability": "mame:edit", "signature": "ed25519:0x9c…", "trace": "00-4f81b3a…-…-01" } // MAME body (example): { "intent": "Curatorial access to the substrate.", "budget": { "tokens": 200000, "deadline_ms": 8000 }, "return": ["result", "audit"] } // Response: { "result": "…", "audit": "max://record/0x4f81b3a-mame-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("mame.edit", body, { capability }); // 2. MCP tool — any MCP-compliant client await mcp.call("map.mame.edit", body); // 3. A2A task — cross-organization invocation await a2a.task("map://intent", { intent: body, treaty: "moat://0x91a" });

SLA & metering

45ms
320ms
99.9%
edits

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:

MIND · target memory
MAXIM · redaction authority
MAX · every edit
MOTET · migration progress
MAXIM · policy
MOOT · contested edits
MEAL · per-edit meter

Browse the registry.

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