Implemented product · self-hosted · public release record pending

Operating memory that keeps the correction.

Ax0s stores memory records in LanceDB on the operator-controlled filesystem. Connection paths are implemented separately for Claude Code, Codex, ChatGPT, and Hermes; a dated same-store four-surface receipt is pending. Stale facts are superseded instead of deleted, and their history stays addressable.

Read the quickstart Read the capability boundary
Supersession receipt · current view

The correction becomes current. The prior record remains addressable.

Source lineage records where the correction came from; current recall follows the live record; history recall retains the superseded record and its relationship.

Source, current, and superseded memory record strata A recorded operator message is the source lineage for the highlighted Wednesday correction. The correction is current and points to the dimmed Friday record retained in superseded history. SOURCE · LINEAGE operator message · assistant recorded correction origin agent · operator-cli lineage → r_demo_wednesday recorded from CURRENT · CORRECTION record:r_demo_wednesday Wednesday · 15:00 UTC is_superseded · false default recall · returned related record SUPERSEDED · HISTORY record:r_demo_friday Friday · 17:00 UTC is_superseded · true history recall · addressable

Scroll horizontally on a narrow screen to inspect all three strata.

Record lifecycle

Capture. Trace. Retrieve. Correct.

The product follows a record from capture to correction. Parser, startup, and serialization paths are implemented and test-covered, and a recorded 0.5.0 round trip now shows the correction path.

  1. Capture

    Write a record.

    MCP exposes brain_remember; the module CLI exposes remember. Both write to the selected project slug. The public contract includes source, entrypoint, role, record type, collection, tags, and optional source-local identifiers.

    Read the documented commands · Inspect the field contract

  2. Recall

    Recall current memory.

    MCP brain_recall and CLI recall return the documented recall shape. Superseded records are excluded by default.

    Read retrieval semantics

  3. Adjudication

    Confirm, then apply.

    A near-duplicate candidate enters the consolidation queue. A person confirms the proposed keeper and retire IDs, then applies the decision.

  4. Supersession

    Replace without erasing.

    A correction can become current while the prior record remains addressable.

    Open the recorded 2026-07-14 product transcript · Review implemented scope

Data flow

One store. A visible record path.

This is an authored mechanism diagram, not telemetry. It shows the documented path from an interface call to current recall, with superseded history remaining addressable.

FIG 2.1

How does a record move from capture to retained history?

Scope: implemented record-path model · 2026-07-14Source: authored mechanism from the public interface contract

Ax0s memory data flow Capture through MCP or CLI, retain provenance, retrieve current records, and preserve superseded history. CAPTURE MCP + CLI PROVENANCE source fields RETRIEVAL current records SUPERSESSION history retained current path addressable history

Interfaces and boundaries

Interfaces, with the unknowns visible.

Implemented

MCP over stdio

The documented entry point is python -m ax0s_memory mcp-serve. The exact config is in the MCP guide.

MCP guide
Implemented

Module CLI

remember, recall, describe, and stats are documented from the current parser contract.

CLI reference
Current limitation

Access-control scope

Authorization claims are kept in the canonical capability matrix. This page does not extend that scope.

Capability limitation