/MOTET
4,218 req/slive4.21ms p50
MAP/Registry/34 · MOTET/Plane VII · Awareness

MOTET.

Logs, metrics, traces, attestations composed into one polyphonic record.

Protocol · Stateless
VII
Stable · v0.1.0
0.3ms (emit)

Overview

Polyphonic observability.

MOTET is the multi-stream telemetry plane. Logs, metrics, traces, attestations, audit entries — each is a voice in the polyphony. W3C trace propagation threads them: a single trace ID weaves through every voice for any request, providing end-to-end correlation. OpenTelemetry-native; vendor-agnostic at the wire.

Methods

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

motet.emit()
Emit a telemetry event in any supported voice (log, metric, span, attestation).
motet:write
motet.trace()
Reconstruct the full trace for a trace ID across all voices.
motet:read
motet.subscribe()
Subscribe to a filtered stream of telemetry events.
motet:read

Request shape

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

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

SLA & metering

0.3ms (emit)
1.5ms (emit)
99.99%
events · GB

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:

MAX · sampled telemetry
MAXIM · sampling policy
MEAL · per-event, per-GB meter

Browse the registry.

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