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

MOON.

Durable workflows, replay, compensation, checkpointing.

Hybrid · Protocol + Agent
V
Stable · v0.1.0
8ms (dispatch)

Overview

The conductor.

MOON orchestrates the long-running. Built on the Flowers durable-workflow primitive, MOON gives every operation journaling, compensation, replay, and checkpointing — heterogeneous engines compose into a single durable computation. A workflow may span hours, days, treaties, and replays without losing its place. Aut0 executes through MOON; MAP records what MOON conducts.

Methods

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

moon.dispatch()
Dispatch a new durable workflow. Journaled from the first instruction.
moon:dispatch
moon.checkpoint()
Manual checkpoint during a long-running step. Survives replay.
moon:checkpoint
moon.compensate()
Run compensation logic for a failed workflow leg.
moon:admin
moon.replay()
Replay a workflow from a recorded journal. Deterministic when journaled correctly.
moon:read

Request shape

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

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

Governance posture

Every hybrid 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("moon.dispatch", body, { capability }); // 2. MCP tool — any MCP-compliant client await mcp.call("map.moon.dispatch", body); // 3. A2A task — cross-organization invocation await a2a.task("map://intent", { intent: body, treaty: "moat://0x91a" });

SLA & metering

8ms (dispatch)
60ms (dispatch)
99.99%
steps

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:

MAESTRO · plan source
MARC · ad-hoc reasoning
MAX · every step
MOTET · journal
MOMENT · workflow timing
MAXIM · workflow policy
MEAL · per-step, per-second meter

Browse the registry.

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

All Protocols→Request API access→