Ax0s Practice · Human-reviewed service

Find the proof gap before changing the system.

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

A proof-gap review is a human-reviewed service, not an automated score. It traces an important business decision to the records, owners, unknowns, and acceptance evidence behind it.

Worked example: a release captain needs one reliable staging-deploy window after “Staging deploys go out Friday at 17:00 UTC” is corrected to “Staging deploys go out Wednesday at 15:00 UTC.”

See the overview Inspect the blank template

One-screen overview

What it is, who it is for, and what you receive.

What it is

A bounded proof-gap review.

A person reviews one agreed decision or operating claim against the supplied sources, current state, conflicts, ownership, and missing proof.

Who it is for

People accountable for a decision.

Business sponsors, operators, product leaders, and technical owners use it when an important answer is scattered across systems or handoffs.

What you receive

An inspectable decision record.

The service returns a scoped evidence inventory, human review ledger, finding-by-finding report card, unresolved gaps, and a bounded next-action record.

FIG 1.1 · Method published

What gets handed forward at each gate?

Scope: blank service method · no client results · published 2026-07-14 · Source: published Practice protocol

  1. FitBoundary noteProceed, revise, or stop
  2. InventoryEvidence ledgerGaps made explicit
  3. ReviewFinding ledgerUnknowns preserved
  4. ReadoutReport cardDisposition recorded
  5. Optional repairChange recordAcceptance checked

Engagement boundary

A scoped engagement, not a second platform.

Practice begins with a fit decision and an agreed evidence boundary.

Website context is self-report and does not grant or imply production access.

Memory remains the implemented primary product, with a public release record pending; Practice does not replace its product boundary.

Entity-fabric Phase 0 is implemented in ax0s-memory; connector migration and the unified operating surface remain in build. In build Live may become part of a separately agreed implementation scope.

What a proof-gap review examines

The review follows the evidence around one decision.

These are plain-language review dimensions, not scoring categories. A human reviewer records what the supplied evidence supports and leaves unknowns visible.

Decision

What answer is needed?

The decision, its intended use, and what would count as an acceptable completion receipt.

Current claim

What is believed now?

The working answer, who relies on it, and whether its scope is stated clearly.

Source authority

Which record can speak for it?

The source of truth, its owner, and where another source may disagree.

Freshness

When was it last supported?

The checked date, change history, and signals that the answer may be stale.

Conflicts and unknowns

What does not reconcile?

Contradictions, missing state, silent handoffs, and facts the evidence cannot establish.

Ownership

Who can decide or change it?

The accountable decision owner, source owner, and any required change authority.

Access and retention

What boundary governs the review?

The approved sources, access route, handling constraints, and closure expectations.

Next proof

What closes the gap?

The smallest next action, responsible owner, acceptance evidence, and remaining limitation.

Published method

Five stages. Five explicit exits.

Each stage names the input, action, returned artifact, exit condition, and accountable roles before the next stage begins.

Worked example · Illustrative

One decision: which staging-deploy window is current? Systems informing it: the scoped Gmail and iMessage persistent-ingest paths, their source owners, and the release captain’s correction. Closure: Verified 2026-07-14 under memory-roundtrip-supersession.

  1. Stage 1

    Request and fit check

    Input
    The buyer supplies the desired decision, affected systems or handoffs, known constraints, and an accountable sponsor.
    Action
    The Ax0s accountable operator reviews the self-reported context, identifies obvious fit or boundary conflicts, and drafts a proposed evidence scope.
    Artifact
    Fit and boundary note with Proceed, Revise scope, or No fit. These are method labels, not simulated outcomes.
    Exit
    Both sides either stop or agree on the next-stage scope.
    Owner
    The buyer sponsor owns business context; the Ax0s accountable operator owns the fit record.
    Worked example
    Scope one decision: establish the current staging-deploy window without treating an illustrative website scenario as production access or a client result.
  2. Stage 2

    Scoped evidence inventory

    Input
    The buyer supplies the approved source list, source owners, access route, constraints, and known retention requirements.
    Action
    The Ax0s accountable operator inventories supplied evidence, source authority, provenance, missing state, and unresolved access.
    Artifact
    Scoped evidence inventory plus an explicit missing-state ledger.
    Exit
    Source authority, scope, access, retention, and success criteria are agreed or recorded as unresolved.
    Owner
    Source owners approve what is authoritative; the Ax0s accountable operator owns inventory completeness within the agreed boundary.
    Worked example
    Inventory the systems that could inform the decision: scoped persistent Gmail ingest, scoped persistent iMessage ingest, the release record, and the accountable release captain.
  3. Stage 3

    Human review

    Input
    The buyer supplies the approved evidence set and access permitted by the scope.
    Action
    The Ax0s accountable operator reviews conflicts, unknowns, provenance gaps, and change evidence finding by finding.
    Artifact
    Human review ledger containing evidence, limitation, open question, and proposed disposition for each finding.
    Exit
    The bounded evidence set has been reviewed, and every unresolved item remains explicit.
    Owner
    Source owners retain authority over business truth; the Ax0s accountable operator owns the traceability of the review.
    Worked example
    Review the conflict between “Staging deploys go out Friday at 17:00 UTC” (record:r_demo_friday) and “Staging deploys go out Wednesday at 15:00 UTC” (record:r_demo_wednesday), preserving provenance and uncertainty.
  4. Stage 4

    Finding-by-finding report-card readout

    Input
    The buyer supplies source-owner corrections and decision-maker availability.
    Action
    The Ax0s accountable operator presents each finding with its claim, evidence, limit, and proposed next decision.
    Artifact
    Inspectable report card with each finding marked Accepted, Challenged, or Unresolved. These are disposition labels, not fabricated results.
    Exit
    Each finding has a recorded disposition and the next scope decision is explicit.
    Owner
    The buyer decision owner owns dispositions; the Ax0s accountable operator owns the readout artifact.
    Worked example
    The release captain accepts Wednesday at 15:00 UTC as current while Friday at 17:00 UTC remains addressable as the superseded record.
  5. Stage 5

    Optional bounded remediation

    Input
    The buyer supplies a separately agreed remediation scope, change authority, acceptance criteria, and access and retention terms.
    Action
    The Ax0s accountable operator performs only named repairs inside that scope and preserves before-and-after evidence.
    Artifact
    Change and handoff record plus remaining gaps.
    Exit
    Agreed acceptance criteria are evaluated, remaining gaps are recorded, and access and retention closure is confirmed.
    Owner
    The buyer change owner authorizes production change; the Ax0s accountable operator owns the bounded delivery record.
    Worked example
    If correction work is separately authorized, close it only when recall returns record:r_demo_wednesday as current, keeps record:r_demo_friday addressable, and records the Verified 2026-07-14 receipt.

Blank deliverable

A report card without a score.

This blank template shows the structure of what a client receives. It contains no scores, client information, findings, or implied result.

FIG 5.1 · TEMPLATE

What does one finding record contain?

Scope: blank report-card structure · published 2026-07-14 · Source: published Practice method · No client data

TEMPLATE · BLANK · NO SCORESFinding record
Decision or claim
________________
Evidence supplied
________________
Source and checked date
________________
Limitation or unknown
________________
Decision owner
________________
Disposition
________________
Next action and owner
________________
Acceptance receipt
________________

Scope terms

Access, retention, and success are scope terms.

Production access is never implied by website context or a fit conversation.

Access, retention, success criteria, and change authority must be agreed for the specific scope before evidence review or remediation proceeds.

Pending Default Practice access and retention terms are not yet published.

Intake status

Structured intake is not yet published.

No Practice form is available on this route. The product-access gateway remains for product-access requests and is not a Practice intake.

Structured intake Not yet published