Memory · what the product does
Sources in. One sourced answer out.
AX0S reads the systems you already run, keeps one current record per fact, and hands the record back with its sources. Every source below is a register row with a runtime status and an evidence state.
- Sources on the integration register 20 rows · 2026-08-23
- Live ingest paths 6 of 20
- Secrets redacted before the write Verified 2026-07-20
- Prior records stay addressable Verified 2026-07-14
- Store
- LanceDB · operator-controlled filesystem
- Method published
- Data boundary
- Self-hosted by default
- Verified 2026-07-14
- Read surfaces
- Four configured, one store
- Verified 2026-07-28
- Correction
- Prior record stays addressable
- Verified 2026-07-14
- Retention window
- None on superseded records
- Verified 2026-07-28
- Secret redaction
- Seven ingest paths, before write
- Verified 2026-07-20
- Entity fabric
- Phase 0, connector migration open
- In build
Seven rows, seven claims · read the register
01 · Sources
What it reads, row by row.
Email, calendar, documents, meetings, contracts, payments, banking. Each row carries a runtime status, an evidence state and the limit of what it proves.
| Source | Mode | Runtime | Evidence |
|---|---|---|---|
| Persistent ingest 7 rows | |||
| Fathom One configured account on a scheduled polling cadence; cadence is not a delivery SLA, and source failures, network delays, and novel formats remain outside the claim. | Persistent ingest | LIVE | Verified 2026-07-15 |
| Persistent Gmail ingest One configured mailbox with an approximately five-minute polling cadence; known secret patterns are redacted before writes on the named path. Network delays, source failures, and novel formats remain outside the claim. | Persistent ingest | LIVE | Verified 2026-07-15 |
| Persistent Google Calendar ingest Events on one configured calendar (chris@ax0s.io), secret-redacted with identity-tiered pointers, on a 5-minute cycle with checkpoint and deduplication. | Persistent ingest | LIVE | Verified 2026-07-17 |
| Persistent Google Drive/Docs ingest Scoped files become dated snapshots keyed to provider modification time; prior snapshots can remain in memory. No complete provider edit-history stream is claimed. | Persistent ingest | LIVE | Verified 2026-07-17 |
| SignWell Implemented and internally configured; the account has no dated public object-ingest receipt. Contract code does not prove object ingest. | Persistent ingest | IN BUILD | Method published |
| Mercury Read-only pull of one operator-controlled Mercury business account into the finance fabric on a 5-minute cycle, secret- and PII-redacted before any write; the receipt discloses a five-hour host-network outage window on 2026-07-20 with automatic recovery. | Persistent ingest | LIVE | Verified 2026-07-20 |
| Stripe Read-only, version-pinned API contract running against the sandbox environment; the account currently holds zero objects, so connector operation is demonstrated and object ingest is not yet. | Persistent ingest | LIVE | Verified 2026-07-20 |
| Agent access 3 rows | |||
| Gmail Authorized agent read/action surface only; no continuous Memory ingest. | Agent access | LIVE | Verified 2026-07-14 |
| Google Calendar Calendar and event operations on the agent surface; persistent Calendar ingest is tracked in its own row. | Agent access | LIVE | Verified 2026-07-14 |
| Google Drive, Docs, Sheets File, document, and spreadsheet actions on the agent surface; persistent Drive/Docs ingest is tracked in its own row. Sheets content is not persistent governed state. | Agent access | LIVE | Verified 2026-07-14 |
| Connectors 6 rows | |||
| Freshdesk Source and historical tests exist; no fresh shared-fabric ingest or health receipt. | Connector query/write | IN BUILD | Re-run pending |
| Salesforce Not established as live on the shared Memory substrate. | Connector query/write | IN BUILD | Re-run pending |
| Google Sheets connector Distinct from LIVE Workspace agent access; not current governed ingest. | Connector query/write | IN BUILD | Re-run pending |
| Event operations portal Anonymous category only. One catalog records 147 tables, 1,836 scalar fields, and 1,263 relationships; no client outcome. | Schema discovery / connector query/write | IN BUILD | Re-run pending |
| Cloud logging No current persistent business-state ingest or production-health receipt. | Connector query/write | IN BUILD | Re-run pending |
| Additional business services No service is named until it has a contract, owner, acceptance criteria, and status artifact. | Connector query/write | PLANNED | In build |
| Other governed paths 4 rows | |||
| Education-sector CRM projection The source stays anonymous; no production outcome or current-health claim is published. | Governed write | IN BUILD | In build |
| Entity fabric Phase 0 only; connector migration and a customer-ready operating surface remain in build. | Governed write | IN BUILD | Internal dogfood |
| ax0s.io publication Every production deploy must pass the release validator and smoke suites that pin page content to the public claim and integration registries. Deploys are manual; no continuous publication is claimed. | Gate-checked publication | LIVE | Verified 2026-07-29 |
| SoundCloud public catalog One bounded anonymous metadata snapshot and read-back; no OAuth, playback, media download, or scheduled continuity. | Manual snapshot / read-back | LIVE | Verified 2026-08-23 |
Known secret patterns are redacted before writes on named persistent-ingest paths; source failures, novel formats, and other paths remain outside that claim.
02 · Path
How a question becomes a sourced answer.
Four stations. Each one stands on a register row, dated.
- 02.1 Ingest Connectors read a source on a schedule. Known secret patterns are redacted before the write. Verified 2026-07-20
- 02.2 Store One record per fact, on machines you control. Nothing is written back to the source. Method published
- 02.3 Recall A question returns the current record and the typed relationships around it. Scope differs · reviewed 2026-08-23
- 02.4 Receipt The answer carries its sources and what it replaced. Verified 2026-07-14
Read-only until you say otherwise.
A first connection reads. It does not write back to the source. The store sits on machines you control.
- Default self-hosted data boundary Verified 2026-07-14
- Four configured AI surfaces, one store Verified 2026-07-28
- Unified operating surface In build
What we will not put a number on yet.
The retrieval recall@10 evaluation is withheld until a fresh run and dated methodology artifact are published.
Corpus, query set, relevance labels, retrieval configuration, cutoff, run date, and result artifact are not yet published together.
Re-run pending
03 · Record
One record. Its sources travel with it.
Five fields. The numbers on the left are called out beside the figure.
- subject
- Northwind · master service agreement
- fact
- Renewal notice period: 60 days
- sources
- signwell:2026-05-11 · mail:2026-06-02
- state
- Current
- receipt
- supersedes crm:2026-04-22 (30 days)
Synthetic · not customer records
- 01 typed relationships · Scope differs · reviewed 2026-08-23
Subject
The entity a fact hangs on.
- 02 one record per fact
Fact
One current value. Not a document, not a chat log.
- 03 20 register rows
Sources
System, record id, date read. One stamp per source.
- 04 supersession · Verified 2026-07-14
State
Current, superseded, or corroborating.
- 05 no retention window
Receipt
What this record replaced, still addressable.
04 · Supersession
A correction is a write, not a delete.
The short version is here. Plate 02 on the home page draws the timeline, and the proof page holds the claim with its limits.
| Record | Notice period | State |
|---|---|---|
| crm:2026-04-22 | 30 days | Superseded |
| signwell:2026-05-11 | 60 days | Current |
receipt: signwell:2026-05-11 supersedes crm:2026-04-22
Synthetic · not customer records
- Stale facts are superseded instead of deleted, and their history stays addressable.
- Verified 2026-07-14
- 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.
- 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
- 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.
First connection