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 recordsVerified 2026-07-14 · 2026-07-28
- Four configured AI surfaces, one storeVerified 2026-07-28
- Default self-hosted data boundaryVerified 2026-07-14
- Every claim carries scope, method and date39 on register
| Source | Reports | State | Record |
|---|---|---|---|
| CRM account record | Sept 12 | STALE | cal:2026-07-29 |
| Sept 19 | CURRENT | mail:2026-08-04 | |
| Project plan | Sept 19 | CURRENT | current |
| Meeting notes | “…the 19th” | CORROBORATES | corroborates |
- EmailGmailLIVE
- CalendarGoogle CalendarLIVE
- DocumentsGoogle DriveLIVE
- MeetingsFathomLIVE
- ContractsSignWellIN BUILD
- PaymentsStripeLIVE
- BankingMercuryLIVE
- RoadmapAdditional business servicesPLANNED
Ask a question. Get the answer, with the receipt.
Every source carries the date it was read.
Money and contracts are memory here, not attachments.
“Did they pay?” is three questions in three systems.
- What was signedcontract
- What was owedinvoice
- What clearedbank feed
One record. One answer, already cited.
- Supersession and addressable historyVerified 2026-07-14
- Typed N-ary relationships and graph traversalScope differs · reviewed 2026-08-23
- Capability register reviewed2026-08-23
Dated evidence for a claim or the provenance record for an answer. A future journal receipt is design intent until registered.
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.
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.
- Verified2026-07-14supersession-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.
- Verified2026-07-28supersession-no-retention-window · scope and limits →
Your people and your AI tools read the same answer.
Change providers and the memory stays put.
We are what we claim.
AX0S runs on its own memory. The cross-provider receipt exists because our agents wrote it.
- Default product egressnone
- Security dossier reviewed2026-08-25
- Record-level authorizationnot established
- Hardened multi-tenant isolationnot established
- Externally validated identity controlsnot established
scope Public current-state product boundary; not an external audit, certification, compliance scope, or service-level commitment.
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.
Verifiable memory, labelled honestly.
We are building a second receipt, one a third party can check without trusting us.
Not shippedWhere this fits. And where it doesn’t.
A system of record is a commitment, and not everyone should make it yet.
- 1.1The answer spans several systems, not one app
- 1.2Money and contracts are part of the question
- 1.3More than one AI tool, one store
- 1.4Machines you control, and someone to run them
- 2.1A hosted product with nothing to operateself-hosted
- 2.2Web search, notes, or a chatbot personalitysystem of record
- 2.3Record-level authorization or identity controlsnot established
key each tag names the register row that says why · checked 2026-08-25
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.
- Verified 2026-07-142026-07-14Stale 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-282026-07-28Superseded 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-282026-07-28Agents 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-142026-07-14The 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.
- Method published2026-07-14AX0S 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.
- In build2026-07-14Entity-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.
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.
- Emailcurrent
- Calendarcurrent
- Documentscurrent
- Meetingsstale
- Contractsstale
- Paymentsstale
- Bankingstale
3 of 7 sources agree with the current answer
Illustration · abstract diagram, not measured data
7 source categories · 39 register rows · checked 2026-08-25One question. One read-only source. Then keep going, or stop.
One question your team keeps answering differently.
One read-only source. Nothing is written back.
Acceptance criteria, written down before we start.
We hit them and keep going, or we stop.