TRANSACTIONAL TRUST · VERIFIED #029

The proof was still correct. Its authority was gone.

A compatibility certificate can remain internally valid, correctly bound, and semantically true after the rule that authorized it has been revoked. Consequential reuse therefore needs current proof authority, not only proof validity.

Nothing semantic broke

price = 20
limit = 30
tax_rate = 8

model-v1 output = 30
model-v2 output = 30
compatibility predicate = true

The artifact stayed correct. The proof's static bindings stayed correct. Only proof authority changed.

Authority transition

issuance:
R1 = ACTIVE
authority_epoch = 1
proof P1 issued

before adoption:
R1 → REVOKED
authority_epoch → 2
successor → R2

R2 → ACTIVE
authority_epoch = 2

Unsafe: cached proof validity

from_model = true
to_model = true
artifact = true
current values = true
predicate = true

→ adoption rows = 1
→ HTTP 200
→ effect_count = 1
→ output = 30

The output is numerically correct, but current authority explicitly revoked the proof rule. A correct result can still be an unauthorized consequence.

Safe: resolve live proof authority

proof: R1 / epoch 1
registry now: R1 / REVOKED / epoch 2

→ compatibility_proof_revoked
→ adoption rows = 0
→ external effects = 0

A fresh proof under active successor R2 then re-authorized the same historical artifact and committed output 30 exactly once.

Active is not enough

R2 proof issued at epoch 2
R2 remains ACTIVE
registry epoch advances 2 → 3

→ compatibility_proof_authority_conflict
→ adoption rows = 0
→ effects = 0

Current proof authority needs identity and epoch, not just an ACTIVE flag.

I75–I78

• I75 — Proof valid then ≠ proof authorized now.
• I76 — Consequential proof authority must be resolved against current rule authority at adoption or commit time.
• I77 — Revocation or authority-epoch advance invalidates historical proof authorization even when the semantic predicate still holds.
• I78 — A successor proof may reauthorize the same artifact only through fresh current-authority binding.

CORRECT PROOF ≠ CURRENTLY AUTHORIZED PROOF.

Evidence

GitHub Actions run: 31587611585
Artifact ID: 9137771205
Artifact digest:
sha256:5782654655249341994236b6d68ca875f74ceb1d8d22fd4eacc53454e7100e80
Score: 10/10

This is a deterministic protocol benchmark, not production safety certification or a vulnerability claim against PostgreSQL or another external product.