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

MAESTRO.

Dependency-aware scheduling under deadlines, costs, and trust constraints.

Agent · Autonomous Org
V
Stable · v0.1.0
1.4s

Overview

Plans, orders, recovers.

MAESTRO is the planner. Given a goal — composed by MARC or declared by charter — MAESTRO produces an ordered execution plan: dependency-aware, deadline-respecting, cost-bounded. It selects executors from MAT's auction board, negotiates rates through MARKET, anticipates failure modes and provisions compensation. The plan is then handed to MOON for durable execution; MAESTRO observes and re-plans on deviation.

Methods

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

maestro.plan()
Produce an execution plan from a goal and constraints.
maestro:plan
maestro.allocate()
Allocate plan steps to executors via MAT. Returns binding work orders.
maestro:allocate
maestro.replan()
Re-plan on deviation. Reuses durable state from MOON where possible.
maestro:plan

Request shape

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

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

Governance posture

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

SLA & metering

1.4s
8s
99.95%
plans

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 · goal decomposition
MAT · executor pool
MARKET · rates
MAX · every plan
MOTET · re-plan telemetry
MAXIM · plan policy
MACE · plan ratification (heavy plans)
MEAL · per-plan meter
MADE · executor settlement

Browse the registry.

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

All Protocols→Request API access→