The session ends.
The proof remains.

The default self-hosted product path keeps stored product data on operator-controlled machines.

Scope: The default storage path implemented in ax0s-memory 0.5.0; optional model calls, website forms, analytics, and agent-provider traffic are separate paths. · Checked 2026-07-14 · method · artifact · artifact
Limitation: A public release record is pending. Host hardening, operator-managed networking, optional external endpoints, and website services remain outside this default product-data boundary.

Agents 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.

Scope: One dated same-store receipt across the four configured agent surfaces; not a simultaneous-operation, runtime-health, or additional-surface claim. · Checked 2026-07-28 · Supersedes agent-surface-paths · method · artifact · artifact
Limitation: 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.

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.

Scope: Application-level retention behavior of the ax0s-memory record store: superseded rows are flagged, not removed, and stay recallable with include-superseded reads and provenance walks. · Checked 2026-07-28 · method · artifact
Limitation: 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.

Stale facts are superseded instead of deleted, and their history stays addressable.

Scope: The supersession behavior implemented and test-covered in ax0s-memory 0.5.0. · Checked 2026-07-14 · method · artifact · artifact
Limitation: 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.

Ax0s intends to publish methodology, null results, and killed ideas as part of its evidence policy.

Scope: Public evidence policy; not a certification or audit claim. · Checked 2026-07-14 · method
Limitation: This states a publication intent; methodology, null-result, and killed-idea artifacts remain sparse or unavailable.

The retrieval recall@10 evaluation is withheld until a fresh run and dated methodology artifact are published.

Scope: Previously published retrieval evaluation; no value is asserted in this registry. · Checked 2026-07-09 · method
Limitation: Corpus, query set, relevance labels, retrieval configuration, cutoff, run date, and result artifact are not yet published together.

The consolidation precision evaluation is withheld until a fresh run and dated methodology artifact are published.

Scope: Previously published human-adjudicated consolidation evaluation; no value is asserted in this registry. · Checked 2026-07-09 · method
Limitation: Label protocol, class definition, evaluation population, code and configuration version, run date, and result artifact are not yet published together.

Ax0s stores memory records in LanceDB on the operator-controlled filesystem.

Scope: The reviewed self-hosted storage path. · Checked 2026-07-09 · method · artifact
Limitation: This claim does not establish an application-managed backup, restoration, retention, or at-rest encryption control.

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.

Scope: Authentication and authorization controls in the reviewed self-hosted product source and tests. · Checked 2026-07-14 · method · artifact · artifact
Limitation: 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.

The Access form is outside the self-hosted product boundary.

Scope: The public website form and its processor path, separate from ax0s-memory. · Checked 2026-07-14 · method · artifact · artifact
Limitation: 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.

Website analytics is inactive; the local analytics stub sends and stores no events.

Scope: The public website JavaScript included in this release. · Checked 2026-07-09 · method · artifact · artifact
Limitation: This is the current website state, not a promise about a future analytics provider or configuration.

Submissions are delivered by Web3Forms (the form processor) to a monitored founder mailbox at chris@ax0s.io.

Scope: The public Access form processor and currently configured receiving mailbox; the existing form key and destination remain in use. · Checked 2026-07-14 · method · artifact · artifact
Limitation: Processor acceptance confirms delivery only; it does not approve access, begin an engagement, or promise a response time.

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.

Scope: A dated local note of the provider's public pricing and FAQ statements; not an independent primary capture. · Checked 2026-07-09 · method · artifact
Limitation: The exact statements were not independently captured and may have changed; Ax0s does not claim a shorter provider retention period.

The public documentation targets ax0s-memory 0.5.0; the CLI parser, MCP stdio startup, and recall serialization paths are implemented and test-covered.

Scope: The public MCP, module CLI, and recall serialization implementation and static test-definition boundary for product version 0.5.0. · Checked 2026-07-14 · method · artifact
Limitation: Implemented and test-covered does not mean a current full-suite run, compatibility certification, coverage report, or support promise.

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

Scope: The Ax0s operating thesis across people and systems; not a statement of current business-wide product coverage. · Checked 2026-07-11 · method
Limitation: This is direction, not a shipped capability, complete accountability model, customer outcome, or finished company operating plane.

A fleet manifest declares four nodes, expected services, monitored domains, and ownership roles.

Scope: The declared manifest for the Ax0s internal fleet first instance. · Checked 2026-07-11 · method
Limitation: 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.

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.

Scope: The configured declare-observe-adjudicate loop for the Ax0s internal fleet. · Checked 2026-07-11 · method
Limitation: The row has no dated reconciliation receipt; it does not establish successful cadence, completed business-wide reconciliation, or a customer operating surface.

A historical Ax0s Live regression artifact records 190 of 190 scenarios passing across seven connector families in 176,480 ms.

Scope: One historical stored golden regression result across seven connector families. · Checked 2026-07-14 · method · artifact
Limitation: Historical stored regression receipt — not current health. It does not establish current production health, live customer integrations, freshness, or persistent ingest into ax0s-memory.

A historical Ax0s Live cross-connector stress artifact records 50 of 50 scenarios passing, including three spanning all seven connector families.

Scope: One historical stored multi-source stress result containing scenarios across two to seven connector families. · Checked 2026-07-14 · method · artifact
Limitation: Historical stored regression receipt — not current health. It does not establish production uptime, current connector freshness, customer availability, or persistent ingest.

A historical Ax0s Live single-connector stress artifact records 140 of 140 scenarios passing, twenty per connector family.

Scope: One historical stored stress result with twenty scenarios for each of seven connector families. · Checked 2026-07-14 · method · artifact
Limitation: Historical stored regression receipt — not current health. It does not establish production uptime, current connector freshness, customer availability, or persistent ingest.

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.

Scope: One historical anonymized event-operations source catalog; separate from every multi-source registry snapshot and regression result. · Checked 2026-07-14 · method · artifact
Limitation: 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.

Entity-fabric Phase 0 is implemented in ax0s-memory; connector migration and the unified operating surface remain in build.

Scope: Phase 0 entity rows, receipt-gated writes, provenance, query, ownership roles, and supersession on the Memory substrate. · Checked 2026-07-14 · method · artifact · artifact
Limitation: Phase 0 only. Connector migration, customer-ready ownership workflows, and the unified operating surface remain in build; this is not business-wide coverage.

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

Scope: Recorded ax0s-memory 0.5.0 product transcript covering write, recall, human-confirmed supersession, current recall, history recall, session close, and cleanup. · Checked 2026-07-14 · method · artifact
Limitation: One recorded product round trip on the stated environment; not a compatibility, concurrency, durability, or universal contradiction-resolution claim.

The current source snapshot registers 34 MCP tools; four are documented as the public core subset.

Scope: Anchored count of MCP tool decorators in the current ax0s-memory source snapshot and the four-tool public documentation subset. · Checked 2026-07-14 · method · artifact
Limitation: A static registration count is not a startup, invocation, health, compatibility, or customer-availability receipt.

The ax0s-memory HTTP surface has 48 test functions defined in the current source snapshot.

Scope: Static count of HTTP test-function definitions in the current source snapshot. · Checked 2026-07-14 · method · artifact
Limitation: Test definitions are not a current test run, passing-suite receipt, coverage report, security review, or runtime-health claim.

Ten static audit-helper tests are defined for log helpers, recording, record round-trip, and CLI behavior.

Scope: Static test-function definitions for the audit-helper file in the current source snapshot. · Checked 2026-07-14 · method · artifact
Limitation: This narrow count does not establish broad access-event coverage, tamper evidence, a current passing run, or coverage percentage.

The experimental Rust research engine contains 245 explicit Rust test definitions.

Scope: Static count of explicit Rust test definitions in the scoped experimental research engine. · Checked 2026-07-14 · method · artifact
Limitation: The engine is experimental and not integrated into the product. This count is not a current passing run or product-capability claim.

The published Ax0s Practice method defines five stages: fit check, evidence inventory, human review, report-card readout, and optional bounded remediation.

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. · Checked 2026-07-14 · method · artifact
Limitation: 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.

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.

Scope: 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. · Checked 2026-07-17 · Supersedes workspace-agent-surface-2 · method · artifact · artifact
Limitation: 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.

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.

Scope: 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. · Checked 2026-07-20 · Supersedes ingest-secret-redaction-3 · method · artifact · artifact
Limitation: 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.