/MAUSOLEUM
4,218 req/slive4.21ms p50
MAP/Registry/20 · MAUSOLEUM/Plane IV · Governance

MAUSOLEUM.

Dissolution, archive of record, succession of obligation.

Protocol · Stateless
IV
Stable · v0.1.0
process-bound

Overview

Organizations end. MAP records the end.

MAUSOLEUM handles what every institution must someday face: dissolution. When an organization winds down — voluntarily or by judgment — MAUSOLEUM enacts the orderly archive: assets distributed under MARS schedules, obligations transferred to successors under MOOT supervision, the audit chain sealed and preserved for offline verification in perpetuity. The end is itself recorded; the institution exits the mesh with the same rigor it entered.

Methods

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

mausoleum.initiate()
Begin the dissolution sequence under charter authority.
mausoleum:initiate
mausoleum.distribute()
Execute asset distribution schedule. Receipts recorded.
mausoleum:execute
mausoleum.seal()
Seal the audit chain. Final hash published to MARS for perpetual verification.
mausoleum:admin

Request shape

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

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

SLA & metering

process-bound
process-bound
99.9%
dissolutions

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:

MARS · asset registry
MOAT · active treaties
MANA · treasury state
MAX · every dissolution step
MARS · final attestation
MACE · dissolution charter
MOOT · contested winddowns
MADE · final distribution
MEAL · dissolution-bounded meter

Browse the registry.

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