/MARE
4,218 req/slive4.21ms p50
MAP/Registry/11 · MARE/Plane III · Truth

MARE.

Reputation built from outcomes, attestations, and decay. Stake-weighted, transferable, revocable.

Hybrid · Protocol + Agent
III
Stable · v0.1.0
22ms

Overview

Long memory; short forgiveness.

MARE is the institution's long memory of who has proven what. Reputation accumulates from outcomes (did the verdict prove true?), attestations (did the citation hold?), and stake (what was risked on the claim?). Reputation decays with time, recovers with deeds, and can be revoked under MOOT arbitration. Reputation is transferable through delegation but never sold. The currency of standing.

Methods

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

mare.score()
Compute current reputation for a DID, scoped by domain and capability.
mare:read
mare.stake()
Stake reputation on a claim or commitment. Slashable if the claim fails.
mare:write
mare.slash()
Slash reputation under MOOT arbitration. Recorded with full justification.
mare:admin

Request shape

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

// POST /v1/protocol/mare.score // MAP envelope (provided by MACS): { "caller": "did:oas:l1fe:agent:0xa3f…", "capability": "mare:read", "signature": "ed25519:0x9c…", "trace": "00-4f81b3a…-…-01" } // MARE body (example): { "intent": "Long memory; short forgiveness.", "budget": { "tokens": 200000, "deadline_ms": 8000 }, "return": ["result", "audit"] } // Response: { "result": "…", "audit": "max://record/0x4f81b3a-mare-7a…" }

Governance posture

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

SLA & metering

22ms
120ms
99.9%
scores

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 · historical record
MAVEN · attestation outcomes
MAX · every stake
MOTET · reputation curves
MAXIM · scoring policy
MOOT · slash arbitration
MEAL · per-score meter

Browse the registry.

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