Skip to transcript
Back to proof

Accessible HTML transcript

When approval should not travel with the output.

A text equivalent of the six-page visual proof, presented in logical reading order for screen readers and text navigation.

Six visual pages transcribed Claim scope unchanged Synthetic, local, provider-free
Read transcript Download visual PDF

Transcript scope

The text and meaning of the visual proof

This transcript preserves the meaningful text from the six-page PDF. Decorative lines, shapes, and repeated Auxtho page footers are omitted. It does not add customer, production, external-provider, or operating-effectiveness claims.

Page 1 of 6

Exact-output release control

If the output changes, the approval should not travel with it.

  • One reviewed state
  • One authorization
  • One controlled consequence
Relationship validor release is blocked

Three versioned synthetic scenarios. Run locally without external providers.

Page 2 of 6

A release object is more than an approval status.

Auxtho keeps the reviewed state and the permitted action connected.

  1. Exact output: The reviewed bytes
  2. Evidence and policy: The review context
  3. Human authority: Decision and scope
  4. Authorized action: What may happen
  5. Resulting state: Receipt or reconciliation

Release condition

Every link must still be valid at the consequence boundary.

A broken link is not a warning. It is a stop condition.

Page 3 of 6

RC02 - reviewed-version mismatch

Changed after review? Release blocked.

  1. Reviewed: Artifact version A
  2. Changed: Artifact version B
  3. Revalidated: A does not equal B
Control result: BLOCKED0 downstream actions

Authorization is not transferable to a changed artifact.

A new state requires re-evaluation and a new decision.

Page 4 of 6

RC10 - post-action uncertainty

The action may have started. The receipt is not trustworthy.

  1. Action started: One controlled attempt
  2. Receipt lost: Outcome cannot be proven
  3. State: Do not invent certainty
Control result: UNKNOWNRECONCILIATION REQUIRED / NO AUTOMATIC RETRY

Uncertainty is not failure. And it is not permission to try again.

The path preserves what is known without creating a second effect.

Page 5 of 6

RC01 - exact reviewed-state match

Nothing changed. The path completes once.

  1. Exact match: Reviewed state valid
  2. One action: Controlled consequence
  3. One receipt: Linked readback
Control result: COMPLETED ONCE1 action / 1 receipt

The control should be quiet when the reviewed state remains valid.

The same boundary handles success, denial, and uncertainty without changing the contract.

Page 6 of 6

Proof boundary

Control the exact object that leaves.

What this local proof shows

  • Versioned synthetic scenarios
  • Provider-free Level A mechanics
  • Separate verifier
  • Inputs, state readback, bytes, and digests

What it does not claim

  • Customer deployment
  • Production operation
  • External-provider delivery
  • Operating effectiveness

Which failure is harder to govern?

A changed artifact before release, or an uncertain receipt after delivery begins?

Auxtho Release Core. Synthetic, local, provider-free.