Ax0s Live · Integration status ledger
Connect the services your business already runs into one navigable state.
Ax0s is designed to add business services through evidence-labeled adapters. The ledger below shows exactly which services are live for agents, which connectors are in build, which ingest paths are planned, and what artifact earned each status.
LIVE means runnable now only within the named mode. It does not imply persistent ingest, customer availability, bidirectional sync, product shipment, or business-wide state.
Illustrative source topology
Which live connector could carry this deploy-window fact?
Two persistent-ingest routes in the live ledger could carry the same release-captain correction into governed memory. The diagram shows transport capacity, not evidence that this illustrative fact was ingested.
Recorded: “Staging deploys go out Friday at 17:00 UTC” record:r_demo_friday
Corrected: “Staging deploys go out Wednesday at 15:00 UTC” record:r_demo_wednesday
Receipt claim: memory-roundtrip-supersession. The highlighted connector labels correspond to the two persistent-ingest rows in FIG 1.1 below.
Which services are connected, in which mode, and what earned each status?
| Integration | Runtime | Lifecycle | Mode | Evidence | Checked | Artifact | Limitation | Owner role | Next gate |
|---|---|---|---|---|---|---|---|---|---|
| Gmail | LIVE | not a product surface | Agent access | Verified 2026-07-14 | Workspace receipt | Authorized agent read/action surface only; no continuous Memory ingest. | Ax0s integration operator | Publish a persistent sync, checkpoint, deduplication, and later-recall receipt before changing the ingest row. | |
| Google Calendar | LIVE | not a product surface | Agent access | Verified 2026-07-14 | Workspace receipt | Calendar and event operations on the agent surface; persistent Calendar ingest is tracked in its own row. | Ax0s integration operator | Publish a refreshed workspace agent-surface receipt when the configured tool surface changes. | |
| Google Drive, Docs, Sheets | LIVE | not a product surface | Agent access | Verified 2026-07-14 | Workspace receipt | 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. | Ax0s integration operator | Publish a refreshed workspace agent-surface receipt when the configured tool surface changes. | |
| Freshdesk | IN BUILD | experimental | Connector query/write | Re-run pending | Golden regression | Source and historical tests exist; no fresh shared-fabric ingest or health receipt. | Ax0s integration operator | Publish a fresh shared-fabric ingest, query/write, and current-health receipt. | |
| Education-sector CRM projection | IN BUILD | experimental | Governed write | In build | Public artifact pending | The source stays anonymous; no production outcome or current-health claim is published. | Ax0s integration operator | Publish an anonymized projection contract and accepted write/read-back receipt. | |
| Salesforce | IN BUILD | experimental | Connector query/write | Re-run pending | Golden regression | Not established as live on the shared Memory substrate. | Ax0s integration operator | Publish a fresh connector and persistent-ingest receipt on the shared substrate. | |
| Fathom | LIVE | experimental | Persistent ingest | Verified 2026-07-15 | Persistent-ingest receipt | Ingests Ax0s's own recorded meetings into Ax0s Memory and the comms fabric on a 5-minute cycle; single-account scope, no customer data. | Ax0s integration operator | Publish a multi-account contract and a 30-day continuous-operation receipt before any customer-facing claim. | |
| Google Sheets connector | IN BUILD | experimental | Connector query/write | Re-run pending | Golden regression | Distinct from LIVE Workspace agent access; not current governed ingest. | Ax0s integration operator | Publish a current governed-ingest and later-recall receipt. | |
| Event operations portal | IN BUILD | experimental | Schema discovery / connector query/write | Re-run pending | Schema catalog | Anonymous category only. One catalog records 147 tables, 1,836 scalar fields, and 1,263 relationships; no client outcome. | Ax0s integration operator | Publish a fresh anonymized discovery and connector-operation receipt. | |
| Cloud logging | IN BUILD | experimental | Connector query/write | Re-run pending | Golden regression | No current persistent business-state ingest or production-health receipt. | Ax0s integration operator | Publish a current bounded-query and persistent-ingest receipt. | |
| Entity fabric | IN BUILD | experimental | Governed write | Internal dogfood | Phase 0 claim | Phase 0 only; connector migration and a customer-ready operating surface remain in build. | Ax0s product maintainer | Publish connector migration, ownership-model, governed-write, and operating-surface receipts. | |
| Persistent Gmail ingest | LIVE | experimental | Persistent ingest | Verified 2026-07-15 | Persistent-ingest receipt | Inbound mail to one mailbox (chris@ax0s.io), bulk-filtered and secret-redacted, on a 5-minute cycle. | Ax0s product maintainer | Publish a 30-day continuous-operation receipt before widening the claim. | |
| Persistent Google Calendar ingest | LIVE | experimental | Persistent ingest | Verified 2026-07-17 | Persistent-ingest receipt | Events on one configured calendar (chris@ax0s.io), secret-redacted with identity-tiered pointers, on a 5-minute cycle with checkpoint and deduplication. | Ax0s product maintainer | Publish a 30-day continuous-operation receipt before widening the claim. | |
| Persistent Google Drive/Docs ingest | LIVE | experimental | Persistent ingest | Verified 2026-07-17 | Persistent-ingest receipt | File 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. | Ax0s product maintainer | Publish a completed-bootstrap receipt and a 30-day continuous-operation receipt before widening the claim. | |
| Persistent iMessage ingest | LIVE | experimental | Persistent ingest | Verified 2026-07-15 | Persistent-ingest receipt | Messages 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. | Ax0s integration operator | Publish a secret-redaction contract for this path and a 30-day continuous-operation receipt before widening the claim. | |
| SignWell | LIVE | experimental | Persistent ingest | Verified 2026-07-17 | Connector contract | GET-only allowlisted API surface with test-mode documents excluded; the account currently holds zero non-test agreements, so no document ingest is demonstrated yet. | Ax0s integration operator | Publish a document-ingest and later-recall receipt once the first non-test agreement exists. | |
| Mercury | LIVE | experimental | Persistent ingest | Verified 2026-07-20 | Persistent-ingest receipt | 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. | Ax0s integration operator | Publish a 30-day continuous-operation receipt before widening the claim. | |
| Stripe | LIVE | experimental | Persistent ingest | Verified 2026-07-20 | Connector contract | 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. | Ax0s integration operator | Publish an object-ingest and later-recall receipt once the first real object exists in the connected environment. | |
| ax0s.io publication | LIVE | shipped | Gate-checked publication | Verified 2026-07-20 | Publication receipt | 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. | Ax0s product maintainer | Publish an automated per-deploy receipt trail before claiming continuous publication. | |
| Additional business services | PLANNED | roadmap | Connector query/write | In build | No service-specific artifact | No service is named until it has a contract, owner, acceptance criteria, and status artifact. | Ax0s accountable operator | Publish a service-specific contract, owner, acceptance criteria, and status artifact. |
Scroll horizontally to inspect mode, evidence, artifact, limitation, owner, and next gate.
Evidence boundary
A live surface is not the same thing as persistent ingest.
Historical connector implementations and regression receipts exist across seven connector families. These receipts do not establish current production health, live customer integrations, or persistent ingest into ax0s-memory.
Connector-family coverage
A historical Ax0s Live cross-connector stress artifact records 50 of 50 scenarios passing, including three spanning all seven connector families.
Open stored artifactA historical Ax0s Live single-connector stress artifact records 140 of 140 scenarios passing, twenty per connector family.
Open stored artifactOne 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.
Open catalog artifactGoverned state
Implemented substrate. In-build ownership. Direction stays direction.
Memory preserves the correction.
A correction can become current while the prior record remains addressable.
Read MemoryEntity fabric adds a governed layer.
Inspect the boundaryBusiness-wide state is not current coverage.
The combined operating state remains direction, not a shipped platform claim.
Read VisionIngest gate
Review the source before enabling the path.
Source permissions, integration scope, retention, and data handling must be reviewed before persistent ingest is enabled.
Source declaredReview gate remains closed by defaultIngest withheld
Starting point
Start with one service, one state domain, one owner, and one receipt.
A scoped path begins with the decision the connected state must support, the system of record, an accountable owner role, and the artifact that will count as acceptance.