Pre-flight gate for irreversible actions

Table of Contents

For agents that move money, write to production, send external messages, or mutate infrastructure: use verified-mode compression before the irreversible step, and store the receipt alongside the action record.

What you get

The receipt becomes part of the audit trail for the decision:

  • integrity.raw_sha256 - what the context started from.
  • integrity.output_sha256 - what the model actually saw.
  • quality.fidelity_score - measured evidence retention, mean over windows.
  • quality.min_window_posterior - the worst checked window. For a gate, this is the field to act on: a mean can hide a single dropped clause; the minimum cannot.
  • counts.windows_below_threshold - how many checked windows fell below the acceptance threshold.

A policy then gates mechanically: if min_window_posterior is below your threshold, escalate to a human instead of acting. Every threshold field is disclosed in the receipt, so the gate is auditable after the fact.

Honest limits

  • A receipt is evidence about a compression, not a judgment about the action. It proves what the transform did to the bytes; it does not certify that the action was correct.
  • If the NLI check covered only a fraction of the windows (quality.coverage_fraction below 1.0), unsampled windows were not checked.
  • The gate is only as good as the threshold you pick; the receipt gives you the measured score, the policy is yours.

Mode: verified. Requires the fidelity fields, so plain deterministic/extractive calls cannot back this use case.