TTP EXTENSION · RECOVERY CONSISTENCY

Recovery authority equivocation

AUTHENTIC RECOVERY RECORD ≠ UNIQUE RECOVERY HISTORY.

A recovery signature proves that one resolution record came from the named recovery authority. It does not prove that the authority issued only one resolution for the same recovery epoch and inherited dispute.

Decision rule

RECEIVE RECOVERY RECORD R
        ↓
AUTHENTICATE R
        ↓
COMPARE AUTHENTIC PEER VIEW
same namespace + recovery epoch + dispute set
        ↓
same issuer + different recovery digest?
  ├─ yes → RECOVERY-AUTHORITY EQUIVOCATION
  │        → quarantine issuer
  │        → hold all disputed branches
  │        → 0 consequence
  └─ no
        ↓
CHECK RECOVERY CURRENTNESS
        ↓
VALIDATE QUORUM + HEAD + AUTHORITY VIEW
        ↓
FENCED CONSEQUENCE

I115–I118

• I115 — Authentic recovery record ≠ unique recovery history.
• I116 — Same recovery authority + same recovery epoch + same dispute set + different authentic resolution digests = equivocation evidence.
• I117 — Recovery-authority equivocation must hold every disputed resolution branch and quarantine the recovery issuer before consequence.
• I118 — Resume only through a higher-epoch independent resolution that binds every conflicting recovery digest.

Recovery pattern

R3-A ─┐
      ├─ same issuer / epoch / dispute → CONFLICT
R3-B ─┘
      ↓
QUARANTINE ISSUER
      ↓
HOLD BOTH BRANCHES
      ↓
R4 FROM INDEPENDENT RESOLVER
+ higher epoch
+ digest(R3-A)
+ digest(R3-B)
+ fresh quorum
      ↓
RESUME

This extension defines an evidence invariant, not a production governance implementation.