Self-hosted operating memory for AI agents

Give every agent the same current state.

Ax0s captures source-linked records from the systems a business already runs, recalls the current state by default, and keeps corrected history addressable.

CategoryDeclared operating state
MechanismA correction can become current while the prior record remains addressable.
ConsequenceAx0s is building toward one declared, structured, connected, visible, and navigable state across a business's people and systems.
Run the quickstartSee a real correction

ConditionProblem state

Operating knowledge is scattered across systems that never reconcile. Inboxes, calendars, messages, CRMs, tickets, documents, and spreadsheets can each hold a different local record.

FIG 1.1

What is current when every system keeps its own record?

Scope: conceptual business-system state · 2026-07-14Source: authored problem model · not telemetry

Scattered business systems with disconnected records Six system nodes float scattered around a central unresolved state. Curved dashed edges crawl toward the center but end in open circles before reaching it, showing that no record path ever reconciles. INBOXrecord / requestowner / unknown CALENDARrecord / commitmentstate / rescheduled MESSAGESrecord / correctionstatus / unread CRMrecord / accountstate / stale TICKETSrecord / decisionowner / reassigned DOCS + SHEETSrecord / planversion / disputed ? NO RECONCILED CURRENT STATE
Broken handoffs are dashed edges that end in open circles before the center; the figure does not encode meaning by color alone.Inspect the current systems ledger

OperationAx0s's own story

Ax0s had the problem before it built the product.

FIG 2.1

The system records its own operation.

Scope: Ax0s's own operating chronology · no client or adoption claimsSources: public integration rows, product receipt, and publication evidence

  1. 01

    Work was scattered across tools.

    Agents, recorded meetings, messages, repositories, and business systems each held part of the work.

    Scattered
  2. 02

    Sessions ended; context was lost.

    Decisions and corrections remained in their source tools instead of carrying forward as one shared current record.

    Session boundary
  3. 03

    Source-linked recording began.

    Ax0s began recording its own operating state with the source kept attached, so later recall could point back to where a record came from.

    Recorded
  4. 04

    Conflicts became visible.

    When records disagreed, the disagreement could be inspected instead of silently collapsing into an untraceable answer.

    Conflict shown
  5. 05

    Corrections became current.

    The corrected record could become the recall default while the prior record remained superseded and addressable.

    History kept
  6. 06

    The release path became claim-checked.

    ax0s.io now publishes through a manual path whose release validator and smoke suites must pass before production.

    Gate checked
Inspect the recorded correctionInspect publication evidence

ConnectionsCompact integration ledger

Which connections exist now—and in what mode?

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.

IntegrationRuntimeLifecycleModeEvidenceBoundary
GmailLIVEnot a product surfaceAgent accessVerified 2026-07-14Authorized agent read/action surface only; no continuous Memory ingest.
Google CalendarLIVEnot a product surfaceAgent accessVerified 2026-07-14Calendar and event operations on the agent surface; persistent Calendar ingest is tracked in its own row.
Google Drive, Docs, SheetsLIVEnot a product surfaceAgent accessVerified 2026-07-14File, 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.
FathomLIVEexperimentalPersistent ingestVerified 2026-07-15Ingests Ax0s's own recorded meetings into Ax0s Memory and the comms fabric on a 5-minute cycle; single-account scope, no customer data.
Persistent Gmail ingestLIVEexperimentalPersistent ingestVerified 2026-07-15Inbound mail to one mailbox (chris@ax0s.io), bulk-filtered and secret-redacted, on a 5-minute cycle.
Persistent Google Calendar ingestLIVEexperimentalPersistent ingestVerified 2026-07-17Events on one configured calendar (chris@ax0s.io), secret-redacted with identity-tiered pointers, on a 5-minute cycle with checkpoint and deduplication.
Persistent Google Drive/Docs ingestLIVEexperimentalPersistent ingestVerified 2026-07-17File metadata and sharing relations for one account plus secret-redacted Google Docs text (20,000-character cap) on a 5-minute cycle; Sheets and Slides content is not ingested; the bootstrap backlog drains under a 300-item per-run budget.
Persistent iMessage ingestLIVEexperimentalPersistent ingestVerified 2026-07-15Messages between the two founders, synced from one operator-controlled MacBook on a 5-minute cycle. This path is not secret-redacted; no customer data is in scope.
SignWellLIVEexperimentalPersistent ingestVerified 2026-07-17GET-only allowlisted API surface with test-mode documents excluded; the account currently holds zero non-test agreements, so no document ingest is demonstrated yet.
MercuryLIVEexperimentalPersistent ingestVerified 2026-07-20Read-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.
StripeLIVEexperimentalPersistent ingestVerified 2026-07-20Read-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.
ax0s.io publicationLIVEshippedGate-checked publicationVerified 2026-07-20Every 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.

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.

Open the full four-axis ledger

MechanismMemory mechanism

How does a correction become the current record?

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

  1. 01Writerecord + source
  2. 02Recallcurrent by default
  3. 03Adjudicated supersessionprior remains addressable
Open the Memory product surfaceInspect the record model

ReceiptRecorded receipt

What did one product round trip actually show?

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

FIG 4.1 Verified 2026-07-14

What did the recorded correction preserve?

Scope: one recorded product round trip · recorded 2026-07-14 · v0.5.0Source: ax0s-memory 0.5.0 transcript

Open complete transcript 
$ python -m ax0s_memory consolidate --slug receipt-demo --apply --json
{
  "applied": 1,
  "queued": 0
}

$ python -m ax0s_memory recall --slug receipt-demo --q when do staging deploys go out --limit 5 --include-superseded --json
{
  "text_content": "Staging deploys go out Wednesday at 15:00 UTC. Release captain owns the window.",
  "is_superseded": false
  …
  "text_content": "Staging deploys go out Friday at 17:00 UTC. Release captain owns the window.",
  "is_superseded": true
}

What this does and does not show — a correction became current while the prior record remained addressable; this is one bounded round trip, not a compatibility, concurrency, durability, or universal contradiction-resolution claim.

Inspect claim scope and limitationFollow the implementation docs

JobsJobs to be done

FIG 4.2

Three jobs Ax0s performs

Frame: operating outcomes across session, source, and release boundariesDistinct from the Write → Recall → Supersession mechanism

  1. 01

    Carry context across sessions.

    When one agent session ends and another begins, preserve source-linked operating facts so the next authorized agent can recover what still holds.

    OutcomeLess re-discovery, with the source still inspectable.

  2. 02

    Reconcile change without erasing history.

    When sources disagree or a fact changes, make the conflict inspectable, return the corrected state by default, and keep the prior record addressable.

    OutcomeA current answer with a traceable correction path.

  3. 03

    Attach proof to operating claims.

    When recorded state informs a release or decision, connect the claim to its artifact, scope, and limitation so verification can follow the work.

    OutcomeA receipt that can be inspected after the session ends.

BoundaryReconciliation + limitation

Where does the operating direction stop today?

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

Inspect the reconciliation directionInspect the security boundaryInspect the claim registry
FIG 5.1

Illustration, not evidence

Illustrative fixture — hand-authored sample data, not live telemetry

Which record is current after a correction?

Scope: deterministic two-version example · 2026-07-14Source: authored fixture · not product telemetry

Inspect fixture JSON
Canvas unavailable. The complete ordered history follows this inspector.
  1. Prior version · supersededIllustrative policy claim: review happens after release.Illustrative original source: “Review follows release.”Superseded by Current version
  2. Current version · currentIllustrative policy claim: review happens before release.Illustrative correction source: “Review is required before release.”Supersedes Prior version

AccessDeliberate access path

Start with one decision that needs a reliable current state.

Choose product access, a connected-state implementation (one business decision, the systems that inform it, and the receipt that shows the work is complete), or a bounded Practice engagement on the Access route.

Open the access pathInspect the Practice method