Docs / Quickstart · Versioned contract

Install. Correct. Inspect.

The public documentation targets ax0s-memory 0.5.0; the CLI parser, MCP stdio startup, and recall serialization paths are implemented and test-covered. A separate recorded product round trip is available for inspection.

Use the package environment.

The package requires Python 3.11 or newer. The CPU embedder path installs with pip install 'ax0s-memory[cpu]'. The recorded round-trip transcript states its fresh-venv and install context in the header; installation and configuration are documented below but were not captured in the recording.

CPU install path
python -m venv .venv
source .venv/bin/activate
pip install 'ax0s-memory[cpu]'
python -c "from importlib.metadata import version; print('ax0s-memory', version('ax0s-memory'))"

One product round trip, in three excerpts.

These are selected command/output lines from the same recorded round-trip transcript. The raw artifact preserves the recorded output from the opening version query through model-load progress, exact JSON, session close, store counts, and cleanup.

FIG 2.1 · recorded 2026-07-14 · v0.5.0

What did the correction round trip actually return?

Scope: one fresh Linux CPU environment · Source: selected lines from the raw product transcript

1 · Version + sessionrecorded 2026-07-14 · v0.5.0
$ python -c "from importlib.metadata import version; print('ax0s-memory', version('ax0s-memory'))"
ax0s-memory 0.5.0
[exit 0]

$ python -m ax0s_memory session start --slug receipt-demo --allow-new-slug --title 'Round-trip receipt' --agent operator-cli
{
  "session_id": "collection:s_80f59b1409bc",
  "slug": "receipt-demo",
  "started_at": "2026-07-14T09:39:50.883Z"
}

Takeaway: This records one successful version check and session start in a fresh Linux CPU environment; it does not establish compatibility with other environments.

2 · Write + review · selected linesrecorded 2026-07-14 · v0.5.0
$ python -m ax0s_memory remember --slug receipt-demo --agent operator-cli --role assistant --record-type fact --record-id record:r_demo_friday --collection-id collection:s_80f59b1409bc --text Staging deploys go out Friday at 17:00 UTC. Release captain owns the window.
remembered record:r_demo_friday in receipt-demo at 2026-07-14T09:39:51.478Z
[exit 0]

$ python -m ax0s_memory remember --slug receipt-demo --agent operator-cli --role assistant --record-type fact --record-id record:r_demo_wednesday --collection-id collection:s_80f59b1409bc --text Staging deploys go out Wednesday at 15:00 UTC. Release captain owns the window.
remembered record:r_demo_wednesday in receipt-demo at 2026-07-14T09:39:56.477Z
[exit 0]

$ python -m ax0s_memory consolidate --slug receipt-demo --json
{
  "slug": "receipt-demo",
  "scanned": 2,
  "candidates_by_kind": {
    "exact_dup": 0,
    "same_key_update": 0,
    "near_dup": 1,
    "stale_pair": 0
  },
  "applied": 0,
  "queued": 1,
  "suppressed": 0,
  "confirmed_waiting": 0,
  "auto_closed": 0,
  "elapsed_ms": 5.7
}
[exit 0]

Takeaway: This shows two writes and one queued near-duplicate candidate; it does not show an automatic correction.

3 · Confirm + recall · selected linesrecorded 2026-07-14 · v0.5.0
$ python -m ax0s_memory consolidate --slug receipt-demo --confirm 7250761ffa31f2f309d6d7bb732c5eba9a22fed0900794361bfdbaa9192c2277 --reason Deploy window moved; Wednesday is current. --actor operator
human_confirmed 7250761ffa31f2f309d6d7bb732c5eba9a22fed0900794361bfdbaa9192c2277
governance decision recorded: confirm (record:r_ea8ad0083d85)
queue: $AX0S_RECEIPT_DATA/receipt-demo/_consolidation_queue.jsonl
[exit 0]

$ python -m ax0s_memory consolidate --slug receipt-demo --apply --json
{
  "slug": "receipt-demo",
  "scanned": 3,
  "candidates_by_kind": {
    "exact_dup": 0,
    "same_key_update": 0,
    "near_dup": 1,
    "stale_pair": 0
  },
  "applied": 1,
  "queued": 0,
  "suppressed": 0,
  "confirmed_waiting": 0,
  "auto_closed": 0,
  "elapsed_ms": 14.9
}
[exit 0]

$ python -m ax0s_memory recall --slug receipt-demo --q when do staging deploys go out --limit 3 --json
      "id": "record:r_demo_wednesday",
      "text_content": "Staging deploys go out Wednesday at 15:00 UTC. Release captain owns the window.",
      "is_superseded": false,
      "related": [
        "record:r_demo_friday"
      ],

$ python -m ax0s_memory recall --slug receipt-demo --q when do staging deploys go out --limit 5 --include-superseded --json
      "id": "record:r_demo_friday",
      "is_superseded": true,

Takeaway: This shows one human-confirmed apply followed by current and history recall; it does not show that every contradiction will be found or resolved.

Recorded 2026-07-14 · ax0s-memory 0.5.0

A correction can become current while the prior record remains addressable. Open the recorded round-trip transcript for the stated environment header, first recall, the full queue entry, exact confirmation/apply output, current and history recall, session close, stats, and cleanup. Install and configuration commands are documented above but are not captured in the recording.

Inspect the interface you need.

Stale facts are superseded instead of deleted, and their history stays addressable.