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

MOTIF.

Cross-trace pattern detection, anomaly surfacing, motif catalog.

Protocol · Stateless
VII
Stable · v0.1.0
240ms

Overview

Patterns surface.

MOTIF is the institution's pattern-recognizer. Across MOTET's traces, MOMENT's metrics, and MAX's audit chain, MOTIF searches for recurring shapes — sequences that fail together, agents that disagree systematically, treaties that erode predictably. When a motif is named, it joins the catalog and becomes a first-class signal: alertable, citeable in MOOT, formalizable through MIMESIS into convention.

Methods

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

motif.detect()
Run pattern-detection over a window of telemetry. Returns named motifs with frequency.
motif:read
motif.catalog()
Browse the catalog of known motifs.
motif:read
motif.alert()
Subscribe to recurrence of a catalogued motif.
motif:read

Request shape

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

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

SLA & metering

240ms
1.4s
99.9%
detections

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:

MOTET · traces
MOMENT · metrics
MAX · audit
MAX · motif registrations
MOTET · detection telemetry
MAXIM · pattern policy
MEAL · per-detection meter

Browse the registry.

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