AccessThree request paths

Start with the decision. Name the receipt.

Request ax0s-memory product access, a connected-state implementation engagement, or a Practice proof-gap review. A submission asks for consideration; it does not create an account, approve access, place an order, or promise a response time. No public price list exists in this release: scope and cost are settled in the exchange that follows a request.

1 · Product access

Request consideration for ax0s-memory: an operator-hosted memory product with source-linked records and non-destructive correction history.

Review the product record

2 · Connected-state implementation

Start with one business decision, the systems that inform it, the current source of truth, an accountable sponsor, and a receipt that would show the work is complete.

Review the connected-state ledger

3 · Practice proof-gap review

Request a human-reviewed examination of the gap between an important claim and the evidence available to support it. This is not an automated score.

Review the Practice method

Current fit

The default self-hosted product path keeps stored product data on operator-controlled machines. A suitable request needs an environment where you can run and maintain the memory store.

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.

Review the self-hosting scope Review the scoped access-control boundary

Not accepted here

Do not send passwords, API keys, production data, files, security incidents, support emergencies, or purchase orders. This gateway cannot provide instant approval.

Access and engagement

Send a reviewable request.

Required fields are marked. Enter only enough information to describe the decision, boundary, owner, and expected proof.

The name a human should use when replying.

Used to route and reply to this request.

Choose the path closest to the work you want considered.

State the decision, not a general wish for better data.

Use system categories or public product names; do not paste credentials or data.

Name the declared authority and any source that overrides it in practice.

A role is enough if a personal name is unnecessary.

Describe the artifact or observable result you would accept as complete.

Consent

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

Privacy · A local note records conflicting Web3Forms retention statements that were not independently captured. Ax0s has no formal mailbox-retention policy; the delivered email remains in the mailbox until manually deleted.

No-form route: email chris@ax0s.io

DisclosureCollection and routing

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

Website form data leaves your browser for a third-party processor. It is not written to ax0s-memory by this page and is used only to consider and respond to the request.

Inspect the product and website data boundaries

Collected

Name; email; request path; business decision; systems involved; current source of truth; accountable sponsor; acceptable completion receipt; and required service-request consent. Web3Forms may also receive network and server-log metadata.

Route and purpose

Submissions are delivered by Web3Forms (the form processor) to a monitored founder mailbox at chris@ax0s.io. The fields are used only to consider and respond to the selected request path.

Processor retention

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. This site does not claim a shorter period.

Ax0s retention and rights

Ax0s has no formal mailbox-retention or deletion policy. Delivered mail remains in the monitored founder mailbox until manually deleted. To ask for access, correction, or deletion of the email copy, email chris@ax0s.io. No completion time is promised.

Retention · Ungoverned by policy

Failure behavior

Timeout, rejection, rate-limit, provider-limit, and network failures remain visible and never produce a success message. The direct email route stays available.

What happens next

Only explicit Web3Forms acceptance produces “Received — Web3Forms accepted the request for email forwarding.” The accountable operator reviews the submission. Any next step is a reply from a monitored mailbox; the acknowledgement is not approval, onboarding, or a response-time commitment.