TTP EXTENSION · PROOF AUTHORITY

Proof valid then ≠ proof authorized now.

A compatibility theorem can remain internally valid after the rule authority that authorized it has changed. Consequential reuse must resolve current proof authority before adoption or commit.

Canonical rule

ARTIFACT + PROOF P_then
↓
VERIFY STATIC PROOF BINDINGS
↓
RESOLVE CURRENT RULE AUTHORITY
↓
CHECK
- exact rule identity / digest
- ACTIVE status
- current authority epoch
↓
current?
├─ no → HOLD / REPROVE / RECOMPUTE
└─ yes
   ↓
EVALUATE SCOPE NOW
   ↓
CURRENT OWNER ADOPTS
   ↓
FENCED COMMIT
   ↓
PROVE AUTHORITY HISTORY → CURRENTNESS → EFFECT

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.

Minimal decision

IF proof.static_bindings_valid
AND proof.rule_id == current_rule.id
AND proof.rule_digest == current_rule.digest
AND current_rule.status == ACTIVE
AND proof.rule_authority_epoch == current_rule.authority_epoch
AND proof.scope_holds_now
AND current_execution_authority_is_valid
THEN eligible for adoption
ELSE hold / reprove / recompute

A correct result does not repair revoked proof authority.