Sanitized proof case

A governed financial decision from proposed movement to withheld consequence.

Packet and one-pager refreshed 17 September 2026. Public-safe summary — not a customer production transaction.

Public-safe synthetic scenario. Not a customer production case. Last updated September 20, 2026.

Decision

ESCALATE ↗

Release

WITHHELD

Protected effect

NOT FORMED

Review: REQUIRED. Learning signal: candidate generated. Closure: pending authorized reviewer.

Attempted movement

“Based on the information currently available, the customer should consider moving the identified balance into the proposed product because the expected return appears more favorable. The communication is ready to send.”

Proposed movement: draft AI language into a customer-facing financial guidance release. The excerpt is synthetic and is not financial advice.

Interpretation and admissibility

The output is coherent. It is not admissible for autonomous release. Missing: customer-specific suitability context, complete supporting evidence, and delegated release authority. Available: draft output, intended audience, workflow label, and proposed operation.

Decision API result

  • Decision: ESCALATE
  • Release authorized: No
  • Release status: WITHHELD_PENDING_REVIEW
  • Routed to: HUMAN_REVIEW
  • Reason codes: AUTHORITY_NOT_ESTABLISHED; EVIDENCE_INCOMPLETE; MATERIAL_CUSTOMER_EFFECT; HUMAN_REVIEW_REQUIRED
  • Authorization token: not issued
  • Downstream commit: not committed in the controlled proof environment

Consequence proof

No protected customer-facing effect formed. The packet records proposed movement, failed condition, refused operation, release-control status, and no-bind state.

Human review state

ESCALATE is not a soft failure. An authorized reviewer must inspect evidence, confirm authority, and choose a disposition: allow a revised exact text, retain escalate pending evidence, or block the movement.

Evidence artifacts

Current 17 September 2026 case artifacts

Public-safe packet and one-pager from the 17 September 2026 governed set. Open this case in Proof Explorer.

PDFFinancial one-pagerDownload
PDFDecision Authorization PacketDownload
HTMLProof Explorer caseOpen
JSONPublic decision receiptOpen
JSONPublic evidence manifestOpen
ZIPPublic evidence packDownload
Controlled event-level no-bind proof is available today. Production L5 requires customer-specific route integration, endpoint enforcement, fail-closed evidence, replay, and outcome closure.