/MIND
4,218 req/slive4.21ms p50
MAP/Registry/05 · MIND/Plane II · Cognition

MIND.

Episodic, procedural, resource, vault. HNSW search, knowledge graph, causal layers — agent-agnostic.

Hybrid · Protocol + Agent
II
Stable · v0.1.0
12ms

Overview

The cognitive substrate.

MIND is the cognitive substrate of the institution. Four memory types — episodic (what happened), procedural (how to act), resource (what we own), knowledge vault (what we hold sacred) — live atop an LSM-tree KV store with MVCC, WAL, and ACID guarantees. HNSW vector search, knowledge-graph traversal, and a causal-analysis layer compose into a single agent-agnostic memory plane. MIND is built on Akasha but exposed through MAP — any agent, any framework, may bind to it under capability scope.

Methods

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

mind.query()
Query memory by semantic, structural, or temporal predicate. Returns ranked results with provenance.
mind:read
mind.upsert()
Insert or update a memory cell. Vector, graph, and time-series indexes refreshed atomically.
mind:write
mind.snapshot()
Take a consistent snapshot of a memory subgraph for reasoning bind. MARC consumes these.
mind:read
mind.consolidate()
Trigger sleep-cycle consolidation: dedup, compression, and EWC-protected forgetting.
mind:admin

Request shape

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

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

SLA & metering

12ms
85ms
99.99%
queries · MB stored

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:

MAVEN · source attestation
MARE · evidence weight
MAX · every write
MOTET · query telemetry
MOMENT · cardinality changes
MAXIM · access policy
MAME · curatorial edit
MEAL · per-query, per-MB meter

Browse the registry.

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