Tag: route rebinding

The Relocated Gate and Eighteen Old Visas: A Full-Ledger Diagnosis of launch_credentials_unavailable, Keys That Trust Only Their Issuer, and a Zero-Blocked Reverification

A recovery-failed popup on the Hermes desktop opens a full-ledger diagnosis: old sessions pinned their routes to the relocated 127.0.0.1:3000, and the gateway refused to resume them because a key trusts only the gate that issued it — not a fault, but a victory of security. 41 fixed routes censused, 18 rebound to the living port, originals double-backed-up as JSON, then re-verified one by one with the gateway itself: still blocked, zero.