Auxtho Release Core

Three outcomes.
One release contract.

An exact match completes once. A changed artifact is blocked. An uncertain result is held for reconciliation instead of being retried blindly.

Versioned synthetic scenarios Local execution No external providers Separate verifier

Inspect the three outcomes View Singapore source-review proof Read accessible transcript Download the six-page proof

The release object

Approval is only valid while every required relationship remains valid.

Auxtho keeps the reviewed state and the permitted action connected at the consequence boundary.

01Exact reviewed output

02Evidence and policy state

03Accountable human authority

04Authorized downstream action

05Receipt or reconciliation state

Release object diagram connecting exact output, evidence and policy, human authority, authorized action, and resulting state

Implemented outcomes

The same boundary handles denial, uncertainty, and success.

These results come from three frozen, synthetic Level A scenarios. They are not customer or production results. Each scenario reports the observed consequence count for one attempted release.

RC02 / Changed artifact

The reviewed state changed. Release stopped.

Artifact version A was reviewed. Version B reached the release boundary. Revalidation failed before any downstream action began.

BLOCKED0 downstream actions

RC02 local proof: changed artifact blocked with zero downstream actions

RC10 / Uncertain receipt

The action may have started. Certainty was not invented.

The separate local verifier observed one effect in the synthetic path, but Release Core could not establish a trustworthy receipt. The state required reconciliation and the path did not retry automatically.

UNKNOWN / RECONCILIATION REQUIRED1 verifier-observed local effect / 0 automatic retries

RC10 local proof: unknown state, reconciliation required, and no automatic retry

RC01 / Exact match

The reviewed state remained valid. The path completed once.

The exact reviewed state reached the boundary, one controlled action completed, and one linked receipt remained available for readback.

COMPLETED ONCE1 action / 1 linked receipt

RC01 local proof: exact match completed once with one action and one receipt

Proof boundary

What was verified

Versioned synthetic inputs and expected states
Persisted state readback, response bytes, and digests
One separate local verifier
Provider-free Level A release mechanics

Claim boundary

What is not claimed

Customer deployment
Production operation
External-provider delivery
Operating effectiveness

Verification anchors

Dated and hash-pinned

Internal frozen Level A commit (private): 1d1a4fdd252178766d0f58b3c980e151b423a235
Public proof PDF SHA-256: 113AB18459E6EDB95DD6EC67F280FA4B6D9C6C25707BF5677968ED1A4D7E8B7B
Public proof asset manifest: Open machine-readable manifest
Separate source-review proof: Open Singapore source-review proof
Public LinkedIn proof: Published August 19, 2026

Three outcomes.One release contract.