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

MANTLE.

Sleep-cycle consolidation, EWC continual learning, generative replay. Long-term knowledge formation.

Protocol · Stateless
II
Stable · v0.1.0
background

Overview

Where facts settle into foundation.

MANTLE is the consolidation layer beneath conscious thought. While MIND holds the working memory of the institution, MANTLE handles what happens when the institution sleeps: episodic memories are compressed into procedural skills, EWC (Elastic Weight Consolidation) protects what must not be forgotten, generative replay rehearses rare events to prevent their loss. The result: long-term knowledge formation without catastrophic forgetting. Today's facts become tomorrow's foundations.

Methods

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

mantle.consolidate()
Run consolidation pass: dedup, compress, distill, replay. Protected by EWC anchors.
mantle:write
mantle.anchor()
Declare a knowledge anchor — protected from rewriting during future consolidations.
mantle:admin
mantle.replay()
Generative replay of rare event classes for memory rehearsal.
mantle:write

Request shape

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

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

SLA & metering

background
background
99.9%
consolidations

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 · source memories
MARE · importance weights
MAX · consolidation events
MOTET · loss curves
MAXIM · retention policy
MEAL · per-consolidation meter

Browse the registry.

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