Public claim register · checked 2026-08-25

39 public claims. The superseded ones stay on the page.

Every row carries a scope, a method, a checked date and the limit it does not cover. A correction never deletes the row it replaces. The totals below are counted from one JSON file when this page is built.

Read all 39 rows Open claims-public.json

Rows on register 39
Verified, with a run date 18
Superseded, kept and readable 11
Open: stated, in test, or pulled 10

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.

Status: Verified 2026-07-20
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.
Limit: 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.
Owner: AX0S security operator
Supersedes: ingest-secret-redaction-3
Checked: 2026-07-20

id: ingest-secret-redaction-4 · claims-public.json

Public claims: 39
Verified: 18
Superseded, kept: 11
Method published: 4
Re-run pending: 2

Also on register: 2 internal dogfood · 1 in build · 1 direction. Counted from claims-public.json at build time.

01 · Lifecycle

How a row earns the word verified.

A row starts as a stated position or a published method, with no dated run behind it. It turns verified only when a dated run and a written scope exist. When a newer row takes over, the old row is marked superseded and stays where it was.

01 Stated 5 rows Direction · Method published A position or a published method. No dated run behind it.
02 In test 5 rows Re-run pending · In build · Internal dogfood Work we run on ourselves, or a result we pulled until it is re-run.
03 Verified 18 rows Verified, with the run date A dated run, a stated scope, and the limit it does not cover.
04 Superseded 11 rows Superseded, kept A newer row took over. The old row keeps its number and its date.

no dated run a newer row takes over

FIG.1 · the four states a row can hold, with live counts dashed = stated or in test · solid = verified · dim = superseded

What each verified row buys you How the store does the same thing

02 · Corrections

The register corrects itself the same way the store does.

6 chains run through the register today. Every link keeps its own id, status and date, so you can read what we claimed before and when it changed.

ingest-secret-redaction Superseded 2026-07-14
ingest-secret-redaction-2 Superseded 2026-07-15 supersedes ingest-secret-redaction
ingest-secret-redaction-3 Superseded 2026-07-17 supersedes ingest-secret-redaction-2
ingest-secret-redaction-4 Verified 2026-07-20 2026-07-20 supersedes ingest-secret-redaction-3

workspace-agent-surface Superseded 2026-07-14
workspace-agent-surface-2 Superseded 2026-07-15 supersedes workspace-agent-surface
workspace-agent-surface-3 Verified 2026-07-17 2026-07-17 supersedes workspace-agent-surface-2

agent-surface-paths Superseded 2026-07-28
same-store-cross-provider Verified 2026-07-28 2026-07-28 supersedes agent-surface-paths

access-form-boundary Superseded 2026-08-25
access-scheduling-path Verified 2026-08-25 2026-08-25 supersedes access-form-boundary

access-processor-route Superseded 2026-08-25
access-operator-mailbox Verified 2026-08-25 2026-08-25 supersedes access-processor-route

access-provider-retention Superseded 2026-08-25
access-scheduling-provider Method published 2026-08-25 supersedes access-provider-retention

FIG.2 · 15 rows in 6 chains, drawn from the register amber = current row · dim = kept prior row

A chain ends on the row we stand behind today.

The longest chain is 4 links long. Its current row is ingest-secret-redaction-4, checked 2026-07-20. Every earlier link stays readable in the table below and in the JSON.

2 rows were retired without a successor.

memory-http-test-definitions Superseded · 2026-07-14
research-rust-test-definitions Superseded · 2026-07-14

Source revision, counting rule, and run evidence are not published as a current passing receipt.

Supersession in the product The receipt on the homepage

03 · Open

10 rows are not verified, and say so out loud.

These carry a method, a direction or an internal run, and nothing more. Each one prints the reason it is still open.

Method published evidence-publication-policy checked 2026-07-14

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

This states a publication intent; methodology, null-result, and killed-idea artifacts remain sparse or unavailable.
Re-run pending retrieval-recall-evaluation checked 2026-07-09

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 consolidation-precision-evaluation checked 2026-07-09

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

Label protocol, class definition, evaluation population, code and configuration version, run date, and result artifact are not yet published together.
Method published lancedb-storage checked 2026-07-09

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

This claim does not establish an application-managed backup, restoration, retention, or at-rest encryption control.
Direction business-state-direction checked 2026-07-11

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

This is direction, not a shipped capability, complete accountability model, customer outcome, or finished company operating plane.
Internal dogfood fleet-declared-system checked 2026-07-11

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

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.
Internal dogfood fleet-drift-reconciliation checked 2026-07-11

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.

The row has no dated reconciliation receipt; it does not establish successful cadence, completed business-wide reconciliation, or a customer operating surface.
In build live-unified-fabric checked 2026-07-14

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

Phase 0 only. Connector migration, customer-ready ownership workflows, and the unified operating surface remain in build; this is not business-wide coverage.
Method published practice-engagement-protocol checked 2026-07-14

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

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.
Method published access-scheduling-provider checked 2026-08-25

Cal.com is an outside scheduling service, not an AX0S system: what a visitor types into the booking page is held by Cal.com under its own terms and its own retention, which AX0S has not independently captured.

No provider retention period, deletion window, or transfer mechanism is captured here, and AX0S claims none on the provider's behalf. A reader who needs those figures has to read Cal.com's own published terms.

The security boundary Capability register 10 open · 18 verified

04 · The register

All 39 rows, in register order.

Struck rows are superseded. They keep their scope, their date and their place. The filter below hides rows, and changes no number on this page.

2026-07-09 4
2026-07-11 3
2026-07-14 18
2026-07-15 2
2026-07-17 2
2026-07-20 1
2026-07-28 3
2026-08-25 6

FIG.3 · rows by the date they were last checked amber = most recent check, 2026-08-25

All rows39Verified18Superseded, kept11Open10

Claim · scope · limit	Status	Checked · method
The default self-hosted product path keeps stored product data on operator-controlled machines. The default storage path reviewed in the ax0s-memory 0.5.0 source snapshot; optional model calls, website forms, analytics, and agent-provider traffic are separate paths. Public package distribution and a release receipt are unavailable in this release. Host hardening, operator-managed networking, optional external endpoints, and website services remain outside this default product-data boundary. self-hosted-boundary	Verified 2026-07-14	2026-07-14 self-hosted-boundary source or method 2 artifacts recorded
Superseded implementation-path wording; the current bounded same-store receipt is recorded separately. Four separately reviewed agent-surface implementation paths; not a combined runtime claim. Superseded by the 2026-07-28 same-store receipt; no simultaneous-operation, continuous-runtime, or additional-surface claim is made. agent-surface-paths	Superseded superseded by same-store-cross-provider	2026-07-28 agent-surface-paths source or method 1 artifact recorded
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. One dated same-store receipt across the four configured agent surfaces; not a simultaneous-operation, runtime-health, or additional-surface claim. 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. same-store-cross-provider	Verified 2026-07-28 supersedes agent-surface-paths owner: AX0S integration operator	2026-07-28 same-store-cross-provider source or method 2 artifacts recorded
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. 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. 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. supersession-no-retention-window	Verified 2026-07-28 owner: AX0S product maintainer	2026-07-28 /docs/provenance/ 1 artifact recorded
Stale facts are superseded instead of deleted, and their history stays addressable. The supersession behavior implemented and test-covered in ax0s-memory 0.5.0. 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. supersession-history	Verified 2026-07-14	2026-07-14 /docs/memory/#supersession 3 artifacts recorded
AX0S intends to publish methodology, null results, and killed ideas as part of its evidence policy. Public evidence policy; not a certification or audit claim. This states a publication intent; methodology, null-result, and killed-idea artifacts remain sparse or unavailable. evidence-publication-policy	Method published	2026-07-14 /docs/evaluation/#publication-method no artifact recorded
The retrieval recall@10 evaluation is withheld until a fresh run and dated methodology artifact are published. Previously published retrieval evaluation; no value is asserted in this registry. Corpus, query set, relevance labels, retrieval configuration, cutoff, run date, and result artifact are not yet published together. retrieval-recall-evaluation	Re-run pending	2026-07-09 /docs/evaluation/ no artifact recorded
The consolidation precision evaluation is withheld until a fresh run and dated methodology artifact are published. Previously published human-adjudicated consolidation evaluation; no value is asserted in this registry. Label protocol, class definition, evaluation population, code and configuration version, run date, and result artifact are not yet published together. consolidation-precision-evaluation	Re-run pending	2026-07-09 /docs/evaluation/ no artifact recorded
AX0S stores memory records in LanceDB on the operator-controlled filesystem. The reviewed self-hosted storage path. This claim does not establish an application-managed backup, restoration, retention, or at-rest encryption control. lancedb-storage	Method published	2026-07-09 lancedb-storage source or method 1 artifact recorded
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. 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. principal-access-controls	Verified 2026-07-14	2026-07-14 principal-access-controls source or method 2 artifacts recorded
Superseded Access-form boundary wording; the website no longer carries a form, and the current scheduling-path boundary is recorded separately. The public website form and its processor path, separate from ax0s-memory. Superseded by the 2026-08-25 scheduling-path record; the retired form path is kept here for history and describes nothing on the current site. access-form-boundary	Superseded superseded by access-scheduling-path	2026-08-25 access-form-boundary source or method no artifact recorded
Website analytics is inactive; the local analytics stub sends and stores no events. The public website JavaScript included in this release. This is the current website state, not a promise about a future analytics provider or configuration. website-analytics-inactive	Verified 2026-07-09	2026-07-09 /assets/js/analytics.js 2 artifacts recorded
Superseded delivery-route wording; the retired website form processor receives nothing, and the current operator mailbox route is recorded separately. The retired Access form processor and its receiving mailbox, as configured before the 2026-08-25 cutover. Superseded by the 2026-08-25 operator mailbox record; the retired processor path is kept here for history and describes nothing on the current site. access-processor-route	Superseded superseded by access-operator-mailbox owner: AX0S accountable operator	2026-08-25 access-processor-route source or method no artifact recorded
Superseded provider-retention wording; the retired form processor's conflicting public statements no longer describe an active path, and the current scheduling provider is recorded separately. A dated local note of the retired form processor's public pricing and FAQ statements; not an independent primary capture. Superseded by the 2026-08-25 scheduling-provider record; no provider retention period was ever independently captured, and none is carried forward. access-provider-retention	Superseded superseded by access-scheduling-provider	2026-08-25 /privacy/#p03 no artifact recorded
Docs describe the reviewed ax0s-memory 0.5.0 source snapshot; this is not a public package release or availability statement. The reviewed MCP, module CLI, and recall serialization implementation; public package distribution is unavailable in this release. Product access is reviewed by request. No public package or install command is claimed. documentation-version	Verified 2026-07-14	2026-07-14 /data/fixtures/code-to-record.v1.json 1 artifact recorded
AX0S is building toward one declared, structured, connected, visible, and navigable state across a business's people and systems. The AX0S operating thesis across people and systems; not a statement of current business-wide product coverage. This is direction, not a shipped capability, complete accountability model, customer outcome, or finished company operating plane. business-state-direction	Direction owner: AX0S accountable operator	2026-07-11 /vision/#operating-thesis no artifact recorded
A fleet manifest declares four nodes, expected services, monitored domains, and ownership roles. The declared manifest for the AX0S internal fleet first instance. 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. fleet-declared-system	Internal dogfood owner: AX0S accountable operator	2026-07-11 /vision/#first-instance no artifact recorded
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. 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. fleet-drift-reconciliation	Internal dogfood owner: AX0S accountable operator	2026-07-11 /vision/#reconciliation-loop no artifact recorded
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. LIVE — AGENT SURFACE only for the configured Google Workspace tools recorded in the sanitized receipt. 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. workspace-agent-surface	Superseded superseded by workspace-agent-surface-2 owner: AX0S integration operator	2026-07-14 /live/#evidence-boundary 1 artifact recorded
A historical AX0S Live regression artifact records 190 of 190 scenarios passing across seven connector families in 176,480 ms. 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. live-golden-regression	Verified 2026-07-14 owner: AX0S integration operator	2026-07-14 /live/#evidence-boundary 1 artifact recorded
A historical AX0S Live cross-connector stress artifact records 50 of 50 scenarios passing, including three spanning all seven connector families. 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. live-cross-connector-stress	Verified 2026-07-14 owner: AX0S integration operator	2026-07-14 /live/#evidence-boundary 1 artifact recorded
A historical AX0S Live single-connector stress artifact records 140 of 140 scenarios passing, twenty per connector family. 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. live-single-connector-stress	Verified 2026-07-14 owner: AX0S integration operator	2026-07-14 /live/#evidence-boundary 1 artifact recorded
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. 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. live-schema-catalog	Verified 2026-07-14 owner: AX0S integration operator	2026-07-14 /live/#evidence-boundary 1 artifact recorded
Entity-fabric Phase 0 is implemented in ax0s-memory; connector migration and the unified operating surface remain in build. 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. live-unified-fabric	In build owner: AX0S product maintainer	2026-07-14 /live/#one-engine 2 artifacts recorded
Automated secret redaction is not part of current ingest paths. Current Memory and AX0S Live ingest paths described by the public product and integration boundaries. Source permissions, integration scope, secret handling, retention, and data handling require operator review before persistent ingest is enabled. ingest-secret-redaction	Superseded superseded by ingest-secret-redaction-2 owner: AX0S security operator	2026-07-14 ingest-secret-redaction source or method 2 artifacts recorded
A correction can become current while the prior record remains addressable. Recorded ax0s-memory 0.5.0 product transcript covering write, recall, human-confirmed supersession, current recall, history recall, session close, and cleanup. One recorded product round trip on the stated environment; not a compatibility, concurrency, durability, or universal contradiction-resolution claim. memory-roundtrip-supersession	Verified 2026-07-14 owner: AX0S product maintainer	2026-07-14 /docs/memory/#supersession 1 artifact recorded
The reviewed read surface names seven read-only groups: recall/search, direct record reads, context composition, currentness and timeline inspection, fabric query, graph walk, and stats. A dated contract snapshot of the supported read-only MCP/HTTP surface; not a completeness promise for future versions. A contract snapshot is not a startup, invocation, health, compatibility, or customer-availability receipt. memory-mcp-tool-snapshot	Verified 2026-07-14 owner: AX0S product maintainer	2026-07-14 /docs/mcp/#tool-contract 1 artifact recorded
A historical static source-count artifact exists, but no current public test total or passing-run receipt is claimed. Historical definition inventory checked 2026-07-14; definition counts are not run results. Source revision, counting rule, and run evidence are not published as a current passing receipt. memory-http-test-definitions	Superseded owner: AX0S product maintainer	2026-07-14 /docs/#http-surface 1 artifact recorded
Ten static audit-helper tests are defined for log helpers, recording, record round-trip, and CLI behavior. Static test-function definitions for the audit-helper file in the current source snapshot. This narrow count does not establish broad access-event coverage, tamper evidence, a current passing run, or coverage percentage. memory-audit-test-definitions	Verified 2026-07-14 owner: AX0S product maintainer	2026-07-14 /docs/#source-counts 1 artifact recorded
A historical static source-count artifact exists, but no current public test total or passing-run receipt is claimed. Historical definition inventory checked 2026-07-14; definition counts are not run results. Source revision, counting rule, and run evidence are not published as a current passing receipt. research-rust-test-definitions	Superseded owner: AX0S research maintainer	2026-07-14 /docs/#source-counts 1 artifact recorded
The published AX0S Practice method defines five stages: fit check, evidence inventory, human review, report-card readout, and optional bounded remediation. 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. practice-engagement-protocol	Method published owner: AX0S accountable operator	2026-07-14 /practice/#engagement-protocol 1 artifact recorded
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. workspace-agent-surface-2	Superseded supersedes workspace-agent-surface superseded by workspace-agent-surface-3 owner: AX0S integration operator	2026-07-15 /live/#evidence-boundary 2 artifacts recorded
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. workspace-agent-surface-3	Verified 2026-07-17 supersedes workspace-agent-surface-2 owner: AX0S integration operator	2026-07-17 /live/#evidence-boundary 4 artifacts recorded
Automated secret redaction runs on the Fathom and Gmail persistent-ingest paths before any write; other ingest paths remain unredacted. The ax0s-ingest Fathom and Gmail persistent-ingest paths; 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 two named ingest paths only; it is not a guarantee against novel secret formats, and other ingest paths remain unredacted. ingest-secret-redaction-2	Superseded supersedes ingest-secret-redaction superseded by ingest-secret-redaction-3 owner: AX0S security operator	2026-07-15 ingest-secret-redaction-2 source or method 2 artifacts recorded
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. ingest-secret-redaction-3	Superseded supersedes ingest-secret-redaction-2 superseded by ingest-secret-redaction-4 owner: AX0S security operator	2026-07-17 ingest-secret-redaction-3 source or method 5 artifacts recorded
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. ingest-secret-redaction-4	Verified 2026-07-20 supersedes ingest-secret-redaction-3 owner: AX0S security operator	2026-07-20 ingest-secret-redaction-4 source or method 7 artifacts recorded
The Access page books a founder call through an external Cal.com booking page: the name, email, and notes a visitor types there go to Cal.com, and AX0S uses them to schedule and run the call. No page on this website posts visitor input to an AX0S endpoint or to ax0s-memory. The public website source in this release: the Access page booking link, its published disclosure, and the absence of any form or submission handler; separate from the ax0s-memory product path. The check covers this website release only. What Cal.com does with a booking after the visitor submits it is outside this claim, and booking a call approves no access, begins no engagement, and promises no response time. access-scheduling-path	Verified 2026-08-25 supersedes access-form-boundary owner: AX0S accountable operator	2026-08-25 access-scheduling-path source or method 2 artifacts recorded
Cal.com is an outside scheduling service, not an AX0S system: what a visitor types into the booking page is held by Cal.com under its own terms and its own retention, which AX0S has not independently captured. The disclosed external scheduling provider behind the Access page booking link; not a statement about Cal.com's internal processing, retention periods, sub-processors, or transfers. No provider retention period, deletion window, or transfer mechanism is captured here, and AX0S claims none on the provider's behalf. A reader who needs those figures has to read Cal.com's own published terms. access-scheduling-provider	Method published supersedes access-provider-retention owner: AX0S accountable operator	2026-08-25 /privacy/#p03 2 artifacts recorded
The Access page also publishes founder mailbox addresses: mail written to them reaches a monitored founder mailbox directly, with no website form and no form processor in between. The published mailto routes in this website release; not the mail hosting behind the mailboxes. The website adds no processor of its own, but the mail providers on both sides still carry and store the message. AX0S has no formal mailbox retention or deletion policy, and no response timeframe is promised. access-operator-mailbox	Verified 2026-08-25 supersedes access-processor-route owner: AX0S accountable operator	2026-08-25 access-operator-mailbox source or method 1 artifact recorded

Claim · scope · limit

Status

Checked · method

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

The default storage path reviewed in the ax0s-memory 0.5.0 source snapshot; optional model calls, website forms, analytics, and agent-provider traffic are separate paths.

Public package distribution and a release receipt are unavailable in this release. Host hardening, operator-managed networking, optional external endpoints, and website services remain outside this default product-data boundary.

self-hosted-boundary

Verified 2026-07-14

2026-07-14

self-hosted-boundary source or method

2 artifacts recorded

Superseded implementation-path wording; the current bounded same-store receipt is recorded separately.

Four separately reviewed agent-surface implementation paths; not a combined runtime claim.

Superseded by the 2026-07-28 same-store receipt; no simultaneous-operation, continuous-runtime, or additional-surface claim is made.

agent-surface-paths

Superseded

superseded by same-store-cross-provider

2026-07-28

agent-surface-paths source or method

1 artifact recorded

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.

One dated same-store receipt across the four configured agent surfaces; not a simultaneous-operation, runtime-health, or additional-surface claim.

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.

same-store-cross-provider

Verified 2026-07-28

supersedes agent-surface-paths

owner: AX0S integration operator

2026-07-28

same-store-cross-provider source or method

2 artifacts recorded

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.

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.

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.

supersession-no-retention-window

Verified 2026-07-28

owner: AX0S product maintainer

2026-07-28

/docs/provenance/

1 artifact recorded

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

The supersession behavior implemented and test-covered in ax0s-memory 0.5.0.

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.

supersession-history

Verified 2026-07-14

2026-07-14

/docs/memory/#supersession

3 artifacts recorded

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

Public evidence policy; not a certification or audit claim.

This states a publication intent; methodology, null-result, and killed-idea artifacts remain sparse or unavailable.

evidence-publication-policy

Method published

2026-07-14

/docs/evaluation/#publication-method

no artifact recorded

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

Previously published retrieval evaluation; no value is asserted in this registry.

Corpus, query set, relevance labels, retrieval configuration, cutoff, run date, and result artifact are not yet published together.

retrieval-recall-evaluation

Re-run pending

2026-07-09

/docs/evaluation/

no artifact recorded

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

Previously published human-adjudicated consolidation evaluation; no value is asserted in this registry.

Label protocol, class definition, evaluation population, code and configuration version, run date, and result artifact are not yet published together.

consolidation-precision-evaluation

Re-run pending

2026-07-09

/docs/evaluation/

no artifact recorded

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

The reviewed self-hosted storage path.

This claim does not establish an application-managed backup, restoration, retention, or at-rest encryption control.

lancedb-storage

Method published

2026-07-09

lancedb-storage source or method

1 artifact recorded

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.

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.

principal-access-controls

Verified 2026-07-14

2026-07-14

principal-access-controls source or method

2 artifacts recorded

Superseded Access-form boundary wording; the website no longer carries a form, and the current scheduling-path boundary is recorded separately.

The public website form and its processor path, separate from ax0s-memory.

Superseded by the 2026-08-25 scheduling-path record; the retired form path is kept here for history and describes nothing on the current site.

access-form-boundary

Superseded

superseded by access-scheduling-path

2026-08-25

access-form-boundary source or method

no artifact recorded

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

The public website JavaScript included in this release.

This is the current website state, not a promise about a future analytics provider or configuration.

website-analytics-inactive

Verified 2026-07-09

2026-07-09

/assets/js/analytics.js

2 artifacts recorded

Superseded delivery-route wording; the retired website form processor receives nothing, and the current operator mailbox route is recorded separately.

The retired Access form processor and its receiving mailbox, as configured before the 2026-08-25 cutover.

Superseded by the 2026-08-25 operator mailbox record; the retired processor path is kept here for history and describes nothing on the current site.

access-processor-route

Superseded

superseded by access-operator-mailbox

owner: AX0S accountable operator

2026-08-25

access-processor-route source or method

no artifact recorded

Superseded provider-retention wording; the retired form processor's conflicting public statements no longer describe an active path, and the current scheduling provider is recorded separately.

A dated local note of the retired form processor's public pricing and FAQ statements; not an independent primary capture.

Superseded by the 2026-08-25 scheduling-provider record; no provider retention period was ever independently captured, and none is carried forward.

access-provider-retention

Superseded

superseded by access-scheduling-provider

2026-08-25

/privacy/#p03

no artifact recorded

Docs describe the reviewed ax0s-memory 0.5.0 source snapshot; this is not a public package release or availability statement.

The reviewed MCP, module CLI, and recall serialization implementation; public package distribution is unavailable in this release.

Product access is reviewed by request. No public package or install command is claimed.

documentation-version

Verified 2026-07-14

2026-07-14

/data/fixtures/code-to-record.v1.json

1 artifact recorded

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

The AX0S operating thesis across people and systems; not a statement of current business-wide product coverage.

This is direction, not a shipped capability, complete accountability model, customer outcome, or finished company operating plane.

business-state-direction

Direction

owner: AX0S accountable operator

2026-07-11

/vision/#operating-thesis

no artifact recorded

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

The declared manifest for the AX0S internal fleet first instance.

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.

fleet-declared-system

Internal dogfood

owner: AX0S accountable operator

2026-07-11

/vision/#first-instance

no artifact recorded

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.

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.

fleet-drift-reconciliation

Internal dogfood

owner: AX0S accountable operator

2026-07-11

/vision/#reconciliation-loop

no artifact recorded

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.

LIVE — AGENT SURFACE only for the configured Google Workspace tools recorded in the sanitized receipt.

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.

workspace-agent-surface

Superseded

superseded by workspace-agent-surface-2

owner: AX0S integration operator

2026-07-14

/live/#evidence-boundary

1 artifact recorded

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

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.

live-golden-regression

Verified 2026-07-14

owner: AX0S integration operator

2026-07-14

/live/#evidence-boundary

1 artifact recorded

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

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.

live-cross-connector-stress

Verified 2026-07-14

owner: AX0S integration operator

2026-07-14

/live/#evidence-boundary

1 artifact recorded

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

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.

live-single-connector-stress

Verified 2026-07-14

owner: AX0S integration operator

2026-07-14

/live/#evidence-boundary

1 artifact recorded

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.

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.

live-schema-catalog

Verified 2026-07-14

owner: AX0S integration operator

2026-07-14

/live/#evidence-boundary

1 artifact recorded

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

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.

live-unified-fabric

In build

owner: AX0S product maintainer

2026-07-14

/live/#one-engine

2 artifacts recorded

Automated secret redaction is not part of current ingest paths.

Current Memory and AX0S Live ingest paths described by the public product and integration boundaries.

Source permissions, integration scope, secret handling, retention, and data handling require operator review before persistent ingest is enabled.

ingest-secret-redaction

Superseded

superseded by ingest-secret-redaction-2

owner: AX0S security operator

2026-07-14

ingest-secret-redaction source or method

2 artifacts recorded

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

Recorded ax0s-memory 0.5.0 product transcript covering write, recall, human-confirmed supersession, current recall, history recall, session close, and cleanup.

One recorded product round trip on the stated environment; not a compatibility, concurrency, durability, or universal contradiction-resolution claim.

memory-roundtrip-supersession

Verified 2026-07-14

owner: AX0S product maintainer

2026-07-14

/docs/memory/#supersession

1 artifact recorded

The reviewed read surface names seven read-only groups: recall/search, direct record reads, context composition, currentness and timeline inspection, fabric query, graph walk, and stats.

A dated contract snapshot of the supported read-only MCP/HTTP surface; not a completeness promise for future versions.

A contract snapshot is not a startup, invocation, health, compatibility, or customer-availability receipt.

memory-mcp-tool-snapshot

Verified 2026-07-14

owner: AX0S product maintainer

2026-07-14

/docs/mcp/#tool-contract

1 artifact recorded

A historical static source-count artifact exists, but no current public test total or passing-run receipt is claimed.

Historical definition inventory checked 2026-07-14; definition counts are not run results.

Source revision, counting rule, and run evidence are not published as a current passing receipt.

memory-http-test-definitions

Superseded

owner: AX0S product maintainer

2026-07-14

/docs/#http-surface

1 artifact recorded

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

Static test-function definitions for the audit-helper file in the current source snapshot.

This narrow count does not establish broad access-event coverage, tamper evidence, a current passing run, or coverage percentage.

memory-audit-test-definitions

Verified 2026-07-14

owner: AX0S product maintainer

2026-07-14

/docs/#source-counts

1 artifact recorded

A historical static source-count artifact exists, but no current public test total or passing-run receipt is claimed.

Historical definition inventory checked 2026-07-14; definition counts are not run results.

Source revision, counting rule, and run evidence are not published as a current passing receipt.

research-rust-test-definitions

Superseded

owner: AX0S research maintainer

2026-07-14

/docs/#source-counts

1 artifact recorded

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

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.

practice-engagement-protocol

Method published

owner: AX0S accountable operator

2026-07-14

/practice/#engagement-protocol

1 artifact recorded

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.

workspace-agent-surface-2

Superseded

supersedes workspace-agent-surface

superseded by workspace-agent-surface-3

owner: AX0S integration operator

2026-07-15

/live/#evidence-boundary

2 artifacts recorded

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.

workspace-agent-surface-3

Verified 2026-07-17

supersedes workspace-agent-surface-2

owner: AX0S integration operator

2026-07-17

/live/#evidence-boundary

4 artifacts recorded

Automated secret redaction runs on the Fathom and Gmail persistent-ingest paths before any write; other ingest paths remain unredacted.

The ax0s-ingest Fathom and Gmail persistent-ingest paths; 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 two named ingest paths only; it is not a guarantee against novel secret formats, and other ingest paths remain unredacted.

ingest-secret-redaction-2

Superseded

supersedes ingest-secret-redaction

superseded by ingest-secret-redaction-3

owner: AX0S security operator

2026-07-15

ingest-secret-redaction-2 source or method

2 artifacts recorded

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.

ingest-secret-redaction-3

Superseded

supersedes ingest-secret-redaction-2

superseded by ingest-secret-redaction-4

owner: AX0S security operator

2026-07-17

ingest-secret-redaction-3 source or method

5 artifacts recorded

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.

ingest-secret-redaction-4

Verified 2026-07-20

supersedes ingest-secret-redaction-3

owner: AX0S security operator

2026-07-20

ingest-secret-redaction-4 source or method

7 artifacts recorded

The Access page books a founder call through an external Cal.com booking page: the name, email, and notes a visitor types there go to Cal.com, and AX0S uses them to schedule and run the call. No page on this website posts visitor input to an AX0S endpoint or to ax0s-memory.

The public website source in this release: the Access page booking link, its published disclosure, and the absence of any form or submission handler; separate from the ax0s-memory product path.

The check covers this website release only. What Cal.com does with a booking after the visitor submits it is outside this claim, and booking a call approves no access, begins no engagement, and promises no response time.

access-scheduling-path

Verified 2026-08-25

supersedes access-form-boundary

owner: AX0S accountable operator

2026-08-25

access-scheduling-path source or method

2 artifacts recorded

Cal.com is an outside scheduling service, not an AX0S system: what a visitor types into the booking page is held by Cal.com under its own terms and its own retention, which AX0S has not independently captured.

The disclosed external scheduling provider behind the Access page booking link; not a statement about Cal.com's internal processing, retention periods, sub-processors, or transfers.

No provider retention period, deletion window, or transfer mechanism is captured here, and AX0S claims none on the provider's behalf. A reader who needs those figures has to read Cal.com's own published terms.

access-scheduling-provider

Method published

supersedes access-provider-retention

owner: AX0S accountable operator

2026-08-25

/privacy/#p03

2 artifacts recorded

The Access page also publishes founder mailbox addresses: mail written to them reaches a monitored founder mailbox directly, with no website form and no form processor in between.

The published mailto routes in this website release; not the mail hosting behind the mailboxes.

The website adds no processor of its own, but the mail providers on both sides still carry and store the message. AX0S has no formal mailbox retention or deletion policy, and no response timeframe is promised.

access-operator-mailbox

Verified 2026-08-25

supersedes access-processor-route

owner: AX0S accountable operator

2026-08-25

access-operator-mailbox source or method

1 artifact recorded

Method and artifact paths that this site does not serve yet print as recorded text, not as links; the served JSON carries them verbatim as recorded. The whole table renders from /data/claims-public.json, the same file we ship to anyone who asks for the register.

claims-public.json · 39 rows Who signs these rows checked 2026-08-25

The raw register

Read the file, not the pitch.

One JSON file holds every row on this page, with the same scopes, dates and limits. Take it to your own review.

Open claims-public.json Book a founder call

39 rows · 18 verified · 11 superseded, kept · checked 2026-08-25