Operational Memory for Businesses

The system of record for what your business actually knows.

AX0S reads the systems you already run and keeps one current, sourced answer to every question. On your machines. Portable across AI providers.

  • Corrections retain prior records Verified 2026-07-14 · 2026-07-28
  • Four configured AI surfaces, one store Verified 2026-07-28
  • Default self-hosted data boundary Verified 2026-07-14
  • Every claim carries scope, method and date 39 on register
RECALL · one question, one answer RESOLVED

“When do we actually go live?”

Current answer

September 194 sources

Source Reports State Record
CRM · account record September 12 Stale cal:2026-07-29
Email September 19 Current mail:2026-08-04
Project plan September 19 Current current
Meeting notes “…the 19th” Corroborates corroborates
Receipt mail:2026-08-04 supersedes cal:2026-07-29

Synthetic · not customer records

Sources on the integration register

What memory does with them 7 source categories · plus 1 roadmap · 6 live ingest paths of 20 rows · checked 2026-08-23

key solid edge = live · dashed = in build · dim = planned

Known secret patterns are redacted before writes on named persistent-ingest paths; source failures, novel formats, and other paths remain outside that claim.

01 · The answer

Ask a question. Get the answer, with the receipt.

Every source carries the date it was read.

RECALL · two questions, no script 2026-08-08

“Did Meridian pay invoice #204?”

No.

  • Signed SOW · June scope, $4,800 net-30 document · 2026-06-03
  • Bank feed · no matching payment received banking · checked 2026-08-08

“What changed since last week?”

One record moved.

  • receipt: mail:2026-08-04 supersedes cal:2026-07-29 provenance
  • Prior record · retained and addressable no retention window

Synthetic · not customer records

Money and contracts are memory here, not attachments.

“Did they pay?” is three questions in three systems.

  • What was signed contract
  • What was owed invoice
  • What cleared bank feed

One record. One answer, already cited.

  • Supersession and addressable history Verified 2026-07-14
  • Typed N-ary relationships and graph traversal Scope differs · reviewed 2026-08-23
  • Capability register reviewed 2026-08-23

02 · Supersession

A new answer does not erase the old one.

When an answer changes, AX0S keeps the old record and its receipt. Superseded rows are flagged, not removed.

RECORD · go-live date 2 versions
cal:2026-07-29 September 12 Superseded
mail:2026-08-04 September 19 Current
supersedes
FIG.1 · supersession timeline

receipt: mail:2026-08-04 supersedes cal:2026-07-29

Dated evidence for a claim or the provenance record for an answer. A future journal receipt is design intent until registered.

Synthetic · not customer records

Correct it once. Every view updates.

A correction is a write, not a delete. Readers see September 19 and can still walk back to September 12.

Stale facts are superseded instead of deleted, and their history stays addressable.
Verified 2026-07-14 supersession-history · scope and limits
Superseded memory records carry no retention window: every record superseded since 2026-04-04 remains stored and addressable, and no product code path deletes supersession history on a schedule.
Verified 2026-07-28 supersession-no-retention-window · scope and limits

03 · Portability

Your people and your AI tools read the same answer.

Change providers and the memory stays put.

Configured surface Claude Code
Configured surface Codex CLI
Configured surface ChatGPT desktop
Configured surface Hermes
One store ax0s-memory · operator-controlled filesystem Verified 2026-07-28
FIG.2 · four configured surfaces, one store

scope Not continuous simultaneous operation, and not an endorsement by any tool’s maker. One dated same-store receipt across the four configured agent surfaces; not a simultaneous-operation, runtime-health, or additional-surface claim.

We are what we claim.

AX0S runs on its own memory. The cross-provider receipt exists because our agents wrote it.

  • Default product egress none
  • Security dossier reviewed 2026-07-20
  • Record-level authorization not established
  • Hardened multi-tenant isolation not established
  • Externally validated identity controls not established
  • scope Public current-state product boundary; not an external audit, certification, compliance scope, or service-level commitment.

04 · In validation

Verifiable memory, labelled honestly.

We are building a second receipt, one a third party can check without trusting us. Not shipped.

04.1 Canonical journal One append-ordered journal on your machine.
04.2 Journal digest receipts One proposed digest record per segment.
04.3 Base Sepolia anchoring The design targets a digest anchor about every five minutes.
04.4 Public sandbox Re-derive the digest from a receipt.
04.5 Independent auditor Checks the chain, never the contents.
Implementation in validation no register row yet design target ≈ 5 min anchor interval

Design intent. Not yet a register row.

FIG.3 · journal → digest receipts → anchor → sandbox → auditor amber = implemented today · dashed = in validation

05 · Fit

Where this fits. And where it doesn’t.

A system of record is a commitment, and not everyone should make it yet.

Best fit

  • The answer spans several systems, not one app
  • Money and contracts are part of the question
  • More than one AI tool, one store
  • Machines you control, and someone to run them

Not the right fit

  • A hosted product with nothing to operate self-hosted
  • Web search, notes, or a chatbot personality system of record
  • Record-level authorization or identity controls not established

key each tag names the register row that says why · checked 2026-08-25

Public claims
39
Verified
18
Superseded, kept
11
Method published
4
Re-run pending
2

Counted from claims-public.json at build time · checked 2026-08-25

06 · The register

We show what each claim proves. And what it does not.

Every claim carries a scope, a method and a date. Six sit behind these headlines.

FIG.4 · one tick per claim, in register order amber = verified · dim = superseded · dashed = open
Claim Status Checked

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

A public release record is pending. The public fixture remains hand-authored mechanism data; the recorded transcript is one bounded round trip, and the mechanism does not resolve every contradiction automatically.

Verified 2026-07-14 2026-07-14

Superseded memory records carry no retention window: every record superseded since 2026-04-04 remains stored and addressable, and no product code path deletes supersession history on a schedule.

One dated receipt on the stated store; not a host-level immutability, backup, or tamper-evidence claim. Operator-initiated deletion, host storage operations, and table compaction remain possible and are outside this claim. Records from before 2026-04-04 were reduced to count-only skeleton history at the 2026-04-21 storage-engine cutover and are not addressable as full records.

Verified 2026-07-28 2026-07-28

Agents on four separately implemented provider surfaces — Claude Code, Codex, ChatGPT, and Hermes — wrote to and recalled from one shared ax0s-memory store on a recorded date.

The receipt proves one bounded write-and-recall per surface on the recorded date, not continuous cross-provider operation or externally validated identity. Provider identity per leg is established by the operating surface and the store-side source stamp, not by external attestation.

Verified 2026-07-28 2026-07-28

The default self-hosted product path keeps stored product data on operator-controlled machines.

Public package distribution and a release receipt are unavailable in this release. Host hardening, operator-managed networking, optional external endpoints, and website services remain outside this default product-data boundary.

Verified 2026-07-14 2026-07-14

AX0S intends to publish methodology, null results, and killed ideas as part of its evidence policy.

This states a publication intent; methodology, null-result, and killed-idea artifacts remain sparse or unavailable.

Method published 2026-07-14

Entity-fabric Phase 0 is implemented in ax0s-memory; connector migration and the unified operating surface remain in build.

Phase 0 only. Connector migration, customer-ready ownership workflows, and the unified operating surface remain in build; this is not business-wide coverage.

In build 2026-07-14
Show all 39 rows, superseded ones included
Claim Status Checked

The default self-hosted product path keeps stored product data on operator-controlled machines.

self-hosted-boundary

Verified 2026-07-14 2026-07-14

Superseded implementation-path wording; the current bounded same-store receipt is recorded separately.

agent-surface-paths

Superseded 2026-07-28

Agents on four separately implemented provider surfaces — Claude Code, Codex, ChatGPT, and Hermes — wrote to and recalled from one shared ax0s-memory store on a recorded date.

same-store-cross-provider

Verified 2026-07-28 2026-07-28

Superseded memory records carry no retention window: every record superseded since 2026-04-04 remains stored and addressable, and no product code path deletes supersession history on a schedule.

supersession-no-retention-window

Verified 2026-07-28 2026-07-28

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

supersession-history

Verified 2026-07-14 2026-07-14

AX0S intends to publish methodology, null results, and killed ideas as part of its evidence policy.

evidence-publication-policy

Method published 2026-07-14

The retrieval recall@10 evaluation is withheld until a fresh run and dated methodology artifact are published.

retrieval-recall-evaluation

Re-run pending 2026-07-09

The consolidation precision evaluation is withheld until a fresh run and dated methodology artifact are published.

consolidation-precision-evaluation

Re-run pending 2026-07-09

AX0S stores memory records in LanceDB on the operator-controlled filesystem.

lancedb-storage

Method published 2026-07-09

Per-principal tokens and slug/capability grants, expiry, revocation, rate limits, default-deny enforcement, and access-audit records are implemented; record-level authorization, hardened multi-tenant isolation, and externally validated identity controls are not established.

principal-access-controls

Verified 2026-07-14 2026-07-14

Superseded Access-form boundary wording; the website no longer carries a form, and the current scheduling-path boundary is recorded separately.

access-form-boundary

Superseded 2026-08-25

Website analytics is inactive; the local analytics stub sends and stores no events.

website-analytics-inactive

Verified 2026-07-09 2026-07-09

Superseded delivery-route wording; the retired website form processor receives nothing, and the current operator mailbox route is recorded separately.

access-processor-route

Superseded 2026-08-25

Superseded provider-retention wording; the retired form processor's conflicting public statements no longer describe an active path, and the current scheduling provider is recorded separately.

access-provider-retention

Superseded 2026-08-25

Docs describe the reviewed ax0s-memory 0.5.0 source snapshot; this is not a public package release or availability statement.

documentation-version

Verified 2026-07-14 2026-07-14

AX0S is building toward one declared, structured, connected, visible, and navigable state across a business's people and systems.

business-state-direction

Direction 2026-07-11

A fleet manifest declares four nodes, expected services, monitored domains, and ownership roles.

fleet-declared-system

Internal dogfood 2026-07-11

Declared-versus-observed comparison is configured to run twice hourly; deviations are defined as drift records, and undeclared findings enter an adopt-or-kill decision queue.

fleet-drift-reconciliation

Internal dogfood 2026-07-11

Gmail and Google Calendar are live on the agent surface: authorized agents can read and act through configured Workspace tools. Their state is not yet continuously ingested into ax0s-memory.

workspace-agent-surface

Superseded 2026-07-14

A historical AX0S Live regression artifact records 190 of 190 scenarios passing across seven connector families in 176,480 ms.

live-golden-regression

Verified 2026-07-14 2026-07-14

A historical AX0S Live cross-connector stress artifact records 50 of 50 scenarios passing, including three spanning all seven connector families.

live-cross-connector-stress

Verified 2026-07-14 2026-07-14

A historical AX0S Live single-connector stress artifact records 140 of 140 scenarios passing, twenty per connector family.

live-single-connector-stress

Verified 2026-07-14 2026-07-14

One anonymized AX0S Live source catalog recorded 147 tables, 1,836 scalar fields, 1,263 relationships, and 245,161 rows when introspected on 2026-03-11.

live-schema-catalog

Verified 2026-07-14 2026-07-14

Entity-fabric Phase 0 is implemented in ax0s-memory; connector migration and the unified operating surface remain in build.

live-unified-fabric

In build 2026-07-14

Automated secret redaction is not part of current ingest paths.

ingest-secret-redaction

Superseded 2026-07-14

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

memory-roundtrip-supersession

Verified 2026-07-14 2026-07-14

The reviewed read surface names seven read-only groups: recall/search, direct record reads, context composition, currentness and timeline inspection, fabric query, graph walk, and stats.

memory-mcp-tool-snapshot

Verified 2026-07-14 2026-07-14

A historical static source-count artifact exists, but no current public test total or passing-run receipt is claimed.

memory-http-test-definitions

Superseded 2026-07-14

Ten static audit-helper tests are defined for log helpers, recording, record round-trip, and CLI behavior.

memory-audit-test-definitions

Verified 2026-07-14 2026-07-14

A historical static source-count artifact exists, but no current public test total or passing-run receipt is claimed.

research-rust-test-definitions

Superseded 2026-07-14

The published AX0S Practice method defines five stages: fit check, evidence inventory, human review, report-card readout, and optional bounded remediation.

practice-engagement-protocol

Method published 2026-07-14

Gmail and Google Calendar are live on the agent surface: authorized agents can read and act through configured Workspace tools. Inbound Gmail for one mailbox is continuously ingested into ax0s-memory; Calendar state is not.

workspace-agent-surface-2

Superseded 2026-07-15

Gmail, Google Calendar, and Google Drive (files and Docs text) are continuously ingested into ax0s-memory on 5-minute cycles; authorized agents can also read and act through configured Workspace tools. Sheets and Slides content is not ingested.

workspace-agent-surface-3

Verified 2026-07-17 2026-07-17

Automated secret redaction runs on the Fathom and Gmail persistent-ingest paths before any write; other ingest paths remain unredacted.

ingest-secret-redaction-2

Superseded 2026-07-15

Automated secret redaction runs on the Fathom, Gmail, Google Calendar, Google Drive, and SignWell persistent-ingest paths before any write; the iMessage path and other ingest paths remain unredacted.

ingest-secret-redaction-3

Superseded 2026-07-17

Automated secret redaction runs on the Fathom, Gmail, Google Calendar, Google Drive, SignWell, Stripe, and Mercury persistent-ingest paths before any write; the iMessage path and other ingest paths remain unredacted.

ingest-secret-redaction-4

Verified 2026-07-20 2026-07-20

The Access page books a founder call through an external Cal.com booking page: the name, email, and notes a visitor types there go to Cal.com, and AX0S uses them to schedule and run the call. No page on this website posts visitor input to an AX0S endpoint or to ax0s-memory.

access-scheduling-path

Verified 2026-08-25 2026-08-25

Cal.com is an outside scheduling service, not an AX0S system: what a visitor types into the booking page is held by Cal.com under its own terms and its own retention, which AX0S has not independently captured.

access-scheduling-provider

Method published 2026-08-25

The Access page also publishes founder mailbox addresses: mail written to them reaches a monitored founder mailbox directly, with no website form and no form processor in between.

access-operator-mailbox

Verified 2026-08-25 2026-08-25

Superseded claims keep their rows, like your records do. Source: claims-public.json.

The proof page claims-public.json 39 rows · checked 2026-08-25

Reconciliation

The register above lists the source categories, live and planned alike. This is the part after ingest: sources disagree for a while, one answer holds, and the record it replaced stays addressable.

RECONCILE · 7 source categories, one current answerone current answer
earlier now current answer
Sources now
  • Email current
  • Calendar current
  • Documents current
  • Meetings stale
  • Contracts stale
  • Payments stale
  • Banking stale

3 of 7 sources agree with the current answer

Illustration · abstract diagram, not measured data

7 source categories · 39 register rows · checked 2026-08-25
ACCESS · one question, one read-only source 30:00

Design partners

One question. One read-only source. Then keep going, or stop.

01 · PickOne question your team keeps answering differently.
02 · ConnectOne read-only source. Nothing is written back.
03 · AgreeAcceptance criteria, written down before we start.
04 · DecideWe hit them and keep going, or we stop.
Book a founder call Read the register first