ok 1. Compromise recovery without losing your identity Alice’s phone is stolen. Her current epoch key (A1) is compromised. She goes to her offline root, derives A2 publishes a lineage event, and every client that supports rotation simply shows: “Alice is now using a new key.” Her followers don’t need to refollow and Alice doesn’t have to burn her whole account. Old posts stay signed by A1, new posts come from A2 Identity continuity is preserved. 2. Routine rotation without breaking the social graph Bob rotates keys yearly for hygiene. He derives A1 -> A2 -> A3 Clients that support rotation automatically follow A3 as Bob’s active identity. Readers see Bob’s profile, posts, and interactions exactly as before. They don’t need to understand the rotation. His timeline remains continuous because the client knows A1 -> A2 -> A3 belong to the same lineage. Nothing is merged. Nothing is rewritten. The UX change is simply that Bob can rotate keys safely without losing his audience or starting over. That’s the whole point: survivable identity without heavy protocol mechanics.