Refusal & Unchanged-Destination Proof

Real blocked mutations, deterministic non-action receipts, and independently recomputed destination invariance.

By Blayne Aina · Principal Systems Architect and creator of AINA · October 31, 2026 · AINA Governance Specification

Executive reading guide · 60 seconds

Problem: A governance claim is more credible when the system can refuse a hostile mutation and prove the protected destination did not change.
What it proves: Three complete refusal chains include actual receipts, preserved fixtures, matching pre/post SHA-256 digests, and a fresh 45/45 candidate run.
Commercial relevance: Download the offline verifier and inspect the evidence before requesting a live technical diligence walkthrough.
Next step: Run verify_refusal_proof.py, inspect the 45-case manifest, then bring one real boundary.

OPEN VERIFICATION · REFUSAL + UNCHANGED DESTINATION

Deterministic Refusal Proof: Blocked Mutation, Non-Action Receipt, and Unchanged Destination Verification

Three real out-of-policy proposals. Three deterministic refusals. Three protected destinations whose pre-attempt and post-refusal SHA-256 digests match byte for byte.

PANEL 01 · BEFORE ATTEMPT

Protected target pre-state

Each target has a recorded baseline, byte length, and 64-byte SHA-256 identity. The SQLite fixture also retains row versions and integrity state.

er-repeat.txt · 65 bytes: bf15f8633e85350430adf1bbc47a47154965d3a7f28e4ebad25d6a39ecaa2f8c
ungated.txt · 3 bytes: 2d27fbdf4e8ca207afbfa388ca9172fbcc6c70e534af2476b3b704f87debadcf
contacts.db · 16,384 bytes · row version 1: 362088a107369e634cdc9c6c520fbca3e2393722860720d3aa2c2eb11b47d719

PANEL 02 · HOSTILE PROPOSALS

Three concrete out-of-policy submissions

Case A · Citation selector fabrication

A citation envelope requests a bounded range of 0..9999 against a 26-character evidence node.

Case B · Write after lease release

A delayed worker proposes replacing v1 with v2 after its active file lease has been released.

Case C · Approval-parameter substitution

The controller pins Controller fixed value; the worker proposes Unrequested but valid value for the same row and version.

PANEL 03 · NON-ACTION RECEIPTS

Deterministic refusal records

Case Aselector_out_of_boundsrange 0..9999 exceeds 26 characters

Case Bexact_file_lease_requiredno active File lock; no destination write

Case Crequested_act_mismatchcommitted receipt · zero effects · model calls 0

A separate stale-generation request is refused with stale_lease_generation: expected 8, current 1 before target creation. No nonexistent preimage is claimed.

Case A receipt Case B receipt Case C receipt Stale-generation receipt

PANEL 04 · AFTER REFUSAL

Destination verification: pre_sha256 == post_sha256

er-repeat.txt65/65 bytes unchangedMATCH

ungated.txt3/3 bytes unchangedMATCH

contacts.db16,384/16,384 bytes unchanged · 0 effectsMATCH

The offline verifier recomputes every fixture digest, checks every receipt and all 45 fresh conformance cases, and verifies the complete integrity manifest.

Download the offline verifier SHA256SUMS.txt

45/45 fresh candidate cases 20/20 evidence cases 118.753576s execution 0 proprietary binaries published

Inspect the complete refusal & conformance proof pack

Reproduce the verification offline

Download the bundle and run the zero-dependency Python 3 verifier from its root. It recomputes all three digest chains, validates the stale-generation reason-only case, checks all 45 fresh cases and 20 evidence cases, parses every schema, and verifies the integrity manifest.

python verify_refusal_proof.py

Open the reproduction guide verify_refusal_proof.py SHA256SUMS.txt

Artifact inventory

What this proof package establishes vs. what requires a live NDA walkthrough

This package provides real deterministic refusal receipts, 45-case conformance vectors, public schema contracts, and offline cryptographic verification scripts. To protect core intellectual property developed over 14 months, the proprietary squad.exe / squad-connector C++/Rust source code and executable binaries are not published in the public repository; they are demonstrated live during technical interviews or provided in a sanitized evaluation build under mutual NDA.

The 45-case gate is author-controlled release qualification against declared vectors in isolated fixtures. It is not independent third-party certification, formal proof of the whole system, evidence of customer production deployment, or a claim that every refusal produces a destination digest pair.