/MOMENT
4,218 req/slive4.21ms p50
MAP/Registry/№ 33 · MOMENT/Plane VII · Awareness

MOMENT.

Append-only, monotonic, time-travel queryable.

Protocol · Stateless
VII
Stable · v0.1.0
0.2ms (write)

Overview

Every observable as a moment.

MOMENT is the time-series spine. Every observable — request rate, latency, queue depth, cardinality, energy draw — is recorded at a monotonic timestamp into an append-only structure. Queries support time-travel: ask of any past moment what the metrics were, and MOMENT replies. Aggregation rollups happen offline; the source remains exact, never lossy.

Methods

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

moment.observe()
Record an observation. Timestamp monotonic per source.
moment:write
moment.query()
Query observations by time window, source, predicate.
moment:read
moment.rollup()
Trigger an offline aggregation rollup. Source preserved.
moment:admin

Request shape

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

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

SLA & metering

0.2ms (write)
1ms (write)
99.99%
observations · 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 · rollup events
MAXIM · retention policy
MEAL · per-observation, per-GB meter

Browse the registry.

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

All Protocols→Request API access→