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

MOTE.

Sensors, actuators, vehicles, fabrication — under treaty and policy.

Adapter · External Standard
V
Stable · v0.1.0
device-bound

Overview

When the institution acts on the world.

MOTE is MAP's hand on the physical world. Sensors stream telemetry into MIND through MOTE; actuators receive commands from MAKER through MOTE. Vehicles, fabrication, robotic ensembles — all bound under capability scope, all attested at the IO boundary, all recorded. When an institution must act in matter, MOTE is the protocol that lets it do so without surrendering the audit chain.

Methods

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

mote.observe()
Bind a sensor or telemetry stream into MIND with continuous attestation.
mote:observe
mote.actuate()
Send an actuation command. Sandboxed by physical capability declaration.
mote:actuate
mote.heartbeat()
Periodic device heartbeat with integrity attestation.
mote:read

Request shape

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

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

SLA & metering

device-bound
device-bound
99.9%
events

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:

MACS · device identity
MAKER · invocation envelope
MAX · every actuation
MOTET · device telemetry
MOMENT · stream metrics
MAXIM · physical safety policy
MEAL · per-event meter

Browse the registry.

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

All Protocols→Request API access→