Use the memory directly.

$ 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]

Takeaway: This shows two successful CLI writes to one bounded store; it does not decide which fact should be current.

$ 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]

$ 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)
[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]

Takeaway: This records one candidate that changed current state only after a human confirmation; it does not promise that every candidate is correct.

$ 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"
      ],
[exit 0]

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

      "id": "record:r_demo_friday",
      "text_content": "Staging deploys go out Friday at 17:00 UTC. Release captain owns the window.",
      "is_superseded": true,
      "valid_until": "2026-07-14T09:40:02.109Z"
[exit 0]

Takeaway: Default recall returned Wednesday while history recall also returned the retained Friday record; it does not establish a retention policy or durability guarantee.

$ python -m ax0s_memory session end --slug receipt-demo --session-id collection:s_80f59b1409bc --summary Recorded a fact, corrected it through adjudicated consolidation, verified current and historical recall.
{
  "session_id": "collection:s_80f59b1409bc",
  "slug": "receipt-demo",
  "ended_at": "2026-07-14T09:40:07.715Z",
  "summary": "Recorded a fact, corrected it through adjudicated consolidation, verified current and historical recall."
}
[exit 0]

$ python -m ax0s_memory stats --slug receipt-demo
stats(receipt-demo):
  collection   2
  edge         1
  origin       1
  record       3
[exit 0]

$ rm -rf $AX0S_RECEIPT_DATA/receipt-demo
[exit 0]

$ ls $AX0S_RECEIPT_DATA
_tmp
[exit 0]

Takeaway: This shows one session close and explicit deletion of its isolated directory; it does not show an application-managed retention or recovery policy.