MIM.

Overview

The mesh, made addressable.

MIM is the messaging plane. Every agent in the mesh has a mailbox; every message carries a signed envelope, a delivery guarantee, and an audit reference. Synchronous request/response, asynchronous mailbox, broadcast under topic, A2A bridge for cross-organization conversation — MIM unifies them. When one agent must speak to another, MIM is the line.

Methods

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

Request shape

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

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.

SLA & metering

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: