/MAXIM
4,218 req/slive4.21ms p50
MAP/Registry/16 · MAXIM/Plane IV · Governance

MAXIM.

Cedar/Logos policy authoring, evaluation, and explanation.

Protocol · Stateless
IV
Stable · v0.1.0
0.6ms

Overview

Rules with reasons; refusal with receipts.

MAXIM is the policy engine. Every dispatch passes a policy check: caller, capability, target, context — evaluated against the institution's active maxims. Authored in Cedar (or Logos for the institutionally inclined), evaluated in microseconds, every decision explained — what rule fired, what facts triggered it, what alternatives were considered. Refusal carries reasons; the institution does not say no without telling you why.

Methods

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

maxim.evaluate()
Evaluate a request against active policy. Returns allow/deny with full explanation.
maxim:eval
maxim.author()
Author or update a policy. Versioned; changes recorded for review.
maxim:author
maxim.explain()
Produce a human-readable explanation of a decision: rules fired, facts considered.
maxim:read

Request shape

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

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

SLA & metering

0.6ms
3ms
99.99%
evaluations

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 · capability context
MOAT · treaty envelope
MAX · every decision
MOTET · denial telemetry
MACE · policy ratification
MOOT · policy disputes
MEAL · per-evaluation meter

Browse the registry.

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