Cognitive · v0.2

A memory bridge,
not a database.

Composable, durable memory bridging cognition and production systems.

Category

Composable durable memory

Combines

Stamen substrate + Heddle binding

Best for

Long-lived agents, audit, multi-tenant memory

Stage

v0.2 with compliance and audit endpoints

What Mnemo is

A memory bridge, not a database

Mnemo is the production-side face of the cognitive stack. It composes Stamen substrate dynamics with Heddle structured binding behind a durable interface, so systems that talk to it get a queryable, auditable, multi-tenant memory rather than a research demo. Compliance posture and audit streams are first-class endpoints, not retrofits.

Composition

One surface, two libraries.

Callers see one durable interface. Underneath, Mnemo keeps substrate dynamics and structured binding cleanly separated.

Substrate

Stamen

Sparse population codes, local recurrence, energy-aware routing.

Bridge

Mnemo

One durable interface. Queryable, auditable, multi-tenant.

Memory

Heddle

Structured binding, role-swap, multi-hop walk.

Bridge surfaces

How Mnemo is exposed

Mnemo is the place where cognitive memory becomes infrastructure other systems can depend on.

A1

Composable memory

A single interface composes substrate dynamics from Stamen with structured binding from Heddle. Callers see one durable surface, not two libraries.

              
                memory.bind / memory.walk
              
            
A2

Compliance posture

A live posture endpoint reports what controls are active, what tenants are scoped, and what evidence has been captured. Compliance reviewers query this directly.

              
                GET /compliance/posture
              
            
A3

Audit stream

Every memory operation is observable as an audit event. A streaming endpoint exposes the trail in real time, ready to fan into governance systems.

              
                SSE /audit/stream
              
            

One operation, end-to-end

From bind to audit, in one trace.

Every memory operation is observable. The audit event is part of the same trace, not a separate log to reconcile.

  1. Client memory.bind(g, e, tenant=acme)
  2. Mnemo bridge route → Stamen + Heddle
  3. Stamen sparse activation written
  4. Heddle structured binding stored
  5. Mnemo audit emit event {op: bind, tenant: acme, ok: true}
  6. Compliance evidence captured at /audit/stream

Releases

How Mnemo reached production shape

  1. v0.1

    Memory bridge online

    First version of the bridge composing substrate and binding behind a single durable interface, with the full test suite green.

  2. v0.2

    Compliance and audit endpoints

    Compliance posture surface and audit stream wired to the production governance connector. Both sides covered by end-to-end tests.

  3. Today

    Multi-tenant production preview

    Multi-tenant scoping and durable memory at production-grade retrieval scores. Enterprise preview is open to selected partners.

Measured

Production-grade memory

100 / 100

Mnemo tests passing

Library-level test suite, library version pinned to the production preview.

9 / 9

Governance connector tests

End-to-end coverage of the compliance and audit endpoints from the enterprise side.

P@5 1.00

Multi-hop precision through the bridge

Retrieval through the durable interface matches the underlying memory library.

Where Mnemo lives

Production memory, where it matters

Agents

Long-lived agent memory

Agents that run for days or weeks keep their bindings, plans, and decisions in Mnemo. The memory survives process restarts and tenant boundaries.

Enterprise

Compliance-aware memory

Compliance teams query posture and audit streams directly. Memory becomes evidence.

Models

Backing store for the cognitive stack

RL-X1 and RL-C1 read and write through Mnemo when running outside the research loop.

Available through

Research · Enterprise preview

All technologies →