ROLLBACK EQUIVALENCE

A success flag is not a rollback proof.

Byte equality, semantic invariants, authorization, exact scope, lock release, capability release, correction, invalidation, and non-resurrection must all agree.

Open developer contract

Three adapter classes, one proof meaning

Bounded adapter

Restores only the authorized side-effect scope.

MySQL/MariaDB four-role transaction

Recomputes schema and semantic state in a separate restore target.

Candidate MATM activation

Restores the prior route owner and invalidates candidate receipts.

Proof owner

concresca_runtime/rollback_equivalence.py scripts/test-v047-rollback-equivalence.py deployment/rollback/v047-equivalence.md

EVIDENCE BOUNDARY

Exact scope, owner, correction, expiry, and limitations remain authoritative.

A color, badge, HTTP status, screenshot, signature shape, witness count, or passing test cannot promote an operational proposition. Cancellation, refusal, conflict, timeout, expiry, revocation, and rollback are neutral technical states.

NO JUDGMENT WHATSOEVER. Participant-evaluation and standing effects remain NONE.