A registry check date records review of the public row. It does not turn a pending artifact into a verified result. External-provider facts are dated because they can change.
Claim IDs are stable identifiers; retired IDs are not reused.
FIG 1.1 · Registry distribution
How do the 34 public claims distribute across evidence state and lifecycle?
Scope: all canonical public claim scan rowsSource: authored data-claim-status and data-claim-lifecycle attributesChecked 2026-07-20
A public release record is pending. Host hardening, operator-managed networking, optional external endpoints, and website services remain outside this default product-data boundary.
The paths were reviewed separately. This does not establish simultaneous operation against one store, current runtime health, any additional surface, or externally validated identity.
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.
The row has no dated runtime artifact; it does not establish that all four nodes are operating, current cadence, customer deployment, or business-wide coverage.
The row has no dated reconciliation receipt; it does not establish successful cadence, completed business-wide reconciliation, or a customer operating surface.
7 claims
Integrations
Which connected-state claims have mode-specific evidence?
The receipt proves server startup, tool registration, and one bounded authorized read on the recorded date. It does not prove continuous operation, persistent ingest, production health, or customer availability.
The receipts prove agent access, one bounded authorized read, and one persistent-ingest cycle with checkpoint, deduplication, and later recall on the recorded dates. They do not prove continuous operation, production health, or customer availability; Calendar and Drive state is not persistently ingested.
The receipts prove agent access and persistent-ingest cycles with checkpoint, deduplication, and later recall on the recorded dates. They do not prove continuous operation, a completed Drive bootstrap, production health, or customer availability; Sheets and Slides content is not ingested.
Historical stored regression receipt — not current health. It does not establish current production health, live customer integrations, freshness, or persistent ingest into ax0s-memory.
Historical stored regression receipt — not current health. It does not establish production uptime, current connector freshness, customer availability, or persistent ingest.
Historical stored regression receipt — not current health. It does not establish production uptime, current connector freshness, customer availability, or persistent ingest.
Historical stored regression receipt — not current health. This one-source catalog must not be combined with a separate multi-source schema scope and does not establish client outcomes or persistent ingest.
Phase 0 only. Connector migration, customer-ready ownership workflows, and the unified operating surface remain in build; this is not business-wide coverage.
Publication documents the method and blank report-card structure only; it supplies no client scores or completed-engagement evidence. Structured intake and default access and retention terms are not yet published.
Record-level authorization, hardened multi-tenant isolation, and externally validated identity controls are not established. A legacy shared-bearer compatibility path remains when no principal registry is seeded or an explicit unexpired compatibility block remains. Routine full-access owner allows are intentionally omitted from access-audit records.
4 claims
Website operations
What happens on the public website rather than in the product?
Submitting sends the enumerated request fields to Web3Forms for email delivery to the monitored founder mailbox; the page does not write them to ax0s-memory.
Redaction is pattern-based over known secret shapes and is applied at the write chokepoint of the two named ingest paths only; it is not a guarantee against novel secret formats, and other ingest paths remain unredacted.
Redaction is pattern-based over known secret shapes and is applied at the write chokepoint of the five named ingest paths only; it is not a guarantee against novel secret formats, and other ingest paths remain unredacted.
Redaction is pattern-based over known secret shapes and is applied at the write chokepoint of the seven named ingest paths only; it is not a guarantee against novel secret formats, and other ingest paths remain unredacted.
A public release record is pending. Host hardening, operator networking, optional external endpoints, and website services remain outside this default boundary.
C-02Verified 2026-07-14
Connection paths are implemented separately for Claude Code, Codex, ChatGPT, and Hermes; a dated same-store four-surface receipt is pending.
Status / date
Verified
Scope
Four separately reviewed agent-surface implementation paths; not a combined runtime claim.
The paths were reviewed separately. This does not establish simultaneous operation against one store, current runtime health, any additional surface, or externally validated identity.
C-03Verified 2026-07-14
Stale facts are superseded instead of deleted, and their history stays addressable.
Status / date
Verified
Scope
The supersession behavior implemented and test-covered in ax0s-memory 0.5.0.
A public release record is pending. The fixture remains hand-authored mechanism data; the recorded transcript is one bounded round trip, and the mechanism does not resolve every contradiction automatically.
C-04Method published
Ax0s intends to publish methodology, null results, and killed ideas as part of its evidence policy.
Status / date
Method published · Checked
Scope
Public evidence policy; not a certification or audit claim.
This does not establish application-managed backup, restoration, retention, or at-rest encryption.
C-08Verified 2026-07-14
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.
Status / date
Verified
Scope
Authentication and authorization controls in the reviewed self-hosted product source and tests.
Record-level authorization, hardened multi-tenant isolation, and externally validated identity controls are not established. A legacy shared-bearer compatibility path remains when no principal registry is seeded or an explicit unexpired compatibility block remains. Routine full-access owner allows are intentionally omitted from access-audit records.
C-09Method published
The Access form is outside the self-hosted product boundary.
Status / date
Method published · Checked
Scope
The public website form and processor path, separate from ax0s-memory.
Submitting sends the enumerated request fields to Web3Forms for email delivery to the monitored founder mailbox; the page does not write them to ax0s-memory.
C-10Verified 2026-07-09
Website analytics is inactive; the local analytics stub sends and stores no events.
Status / date
Verified
Scope
The public website JavaScript included in this release.
Processor acceptance confirms delivery only; it does not approve access, begin an engagement, or promise a response time.
C-12Re-run pending
Per Web3Forms' public statements (not independently captured), its retention information conflicts: 30-day free-plan submission history, no stored submissions with server-log deletion every two months, and retention of up to three years.
Status / date
Re-run pending · Checked
Scope
A dated local note of the provider's public pricing and FAQ statements; not an independent primary capture.
The exact statements were not independently captured and may have changed; Ax0s does not claim a shorter provider retention period.
C-14Verified 2026-07-14
The public documentation targets ax0s-memory 0.5.0; the CLI parser, MCP stdio startup, and recall serialization paths are implemented and test-covered.
Status / date
Verified
Scope
The public MCP, module CLI, and recall serialization implementation and static test-definition boundary for product version 0.5.0.
The row has no dated runtime artifact; it does not establish that all four nodes are operating, current cadence, customer deployment, or business-wide coverage.
C-17Internal dogfood
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.
Status / date
Internal dogfood · Checked
Scope
The configured declare-observe-adjudicate loop for the Ax0s internal fleet.
The row has no dated reconciliation receipt; it does not establish successful cadence, completed business-wide reconciliation, or a customer operating surface.
C-18Superseded
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.
The receipt proves server startup, tool registration, and one bounded authorized read on the recorded date. It does not prove continuous operation, persistent ingest, production health, or customer availability.
C-31Superseded
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.
LIVE — AGENT SURFACE for the configured Google Workspace tools recorded in the sanitized receipt, plus persistent inbound-Gmail ingest for one mailbox recorded in the dated ingest receipt.
The receipts prove agent access, one bounded authorized read, and one persistent-ingest cycle with checkpoint, deduplication, and later recall on the recorded dates. They do not prove continuous operation, production health, or customer availability; Calendar and Drive state is not persistently ingested.
C-33Verified 2026-07-17
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.
LIVE — persistent Gmail, Calendar, and Drive/Docs ingest for one account recorded in the dated ingest receipts, plus the agent surface for the configured Google Workspace tools recorded in the sanitized receipt.
The receipts prove agent access and persistent-ingest cycles with checkpoint, deduplication, and later recall on the recorded dates. They do not prove continuous operation, a completed Drive bootstrap, production health, or customer availability; Sheets and Slides content is not ingested.
C-19Verified 2026-07-14
A historical Ax0s Live regression artifact records 190 of 190 scenarios passing across seven connector families in 176,480 ms.
Status / date
Verified
Scope
One historical stored golden regression result across seven connector families.
Historical stored regression receipt — not current health. It does not establish current production health, live customer integrations, freshness, or persistent ingest into ax0s-memory.
C-20Verified 2026-07-14
A historical Ax0s Live cross-connector stress artifact records 50 of 50 scenarios passing, including three spanning all seven connector families.
Status / date
Verified
Scope
One historical stored multi-source stress result containing scenarios across two to seven connector families.
Historical stored regression receipt — not current health. It does not establish production uptime, current connector freshness, customer availability, or persistent ingest.
C-21Verified 2026-07-14
A historical Ax0s Live single-connector stress artifact records 140 of 140 scenarios passing, twenty per connector family.
Status / date
Verified
Scope
One historical stored stress result with twenty scenarios for each of seven connector families.
Historical stored regression receipt — not current health. It does not establish production uptime, current connector freshness, customer availability, or persistent ingest.
C-22Verified 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.
Status / date
Verified
Scope
One historical anonymized event-operations source catalog; separate from every multi-source registry snapshot and regression result.
Historical stored regression receipt — not current health. This one-source catalog must not be combined with a separate multi-source schema scope and does not establish client outcomes or persistent ingest.
C-23In build
Entity-fabric Phase 0 is implemented in ax0s-memory; connector migration and the unified operating surface remain in build.
Status / date
In build · Checked
Scope
Phase 0 entity rows, receipt-gated writes, provenance, query, ownership roles, and supersession on the Memory substrate.
Phase 0 only. Connector migration, customer-ready ownership workflows, and the unified operating surface remain in build; this is not business-wide coverage.
C-24Superseded
Automated secret redaction is not part of current ingest paths.
Redaction is pattern-based over known secret shapes and is applied at the write chokepoint of the two named ingest paths only; it is not a guarantee against novel secret formats, and other ingest paths remain unredacted.
C-34Superseded
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.
The ax0s-ingest Fathom, Gmail, Google Calendar, Google Drive, and SignWell persistent-ingest paths; the iMessage path and all other Memory and Ax0s Live ingest paths remain unredacted.
Redaction is pattern-based over known secret shapes and is applied at the write chokepoint of the five named ingest paths only; it is not a guarantee against novel secret formats, and other ingest paths remain unredacted.
C-35Verified 2026-07-20
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.
The ax0s-ingest Fathom, Gmail, Google Calendar, Google Drive, SignWell, Stripe, and Mercury persistent-ingest paths; the iMessage path and all other Memory and Ax0s Live ingest paths remain unredacted.
Redaction is pattern-based over known secret shapes and is applied at the write chokepoint of the seven named ingest paths only; it is not a guarantee against novel secret formats, and other ingest paths remain unredacted.
C-25Verified 2026-07-14
A correction can become current while the prior record remains addressable.
Status / date
Verified
Scope
Recorded ax0s-memory 0.5.0 product transcript covering write, recall, human-confirmed supersession, current recall, history recall, session close, and cleanup.
The engine is experimental and not integrated into the product. This count is not a current passing run or product-capability claim.
C-30Method published
The published Ax0s Practice method defines five stages: fit check, evidence inventory, human review, report-card readout, and optional bounded remediation.
Status / date
Method published · Checked
Scope
The public Practice engagement method and its five stages; a human-reviewed service method, not an automated score, customer outcome, or service-performance claim.
Publication documents the method and blank report-card structure only; it supplies no client scores or completed-engagement evidence. Structured intake and default access and retention terms are not yet published.
