The Separation report finds the links; this is how you clear them. Every link it shows carries a one-click remedy, and each roll-up carries one too. You'll press them in one of two places, both wired to the same executors so a fix behaves identically wherever it's pressed: each link on the separation board has its own button, and the drop-day fix queue ("What to fix, in order") merges those same jobs into one ranked list — blockers first, then by how many Accounts each fix helps.
A de-link that partly landed: two Accounts moved, one had no free exit and stays flagged.shot-go · fix queue with a shared-exit de-link row just pressed, result note reading 'Moved 2 onto their own exit. 1 had no free exit and stays flagged — add more connections.'
One link, one remedy
Identical fingerprint → re-roll
Hands every duplicate but the first a fresh canvas/audio seed, so they stop hashing to the same device. No network, no spend.
Shared exit / same subnet → de-link
Moves each linked Account but the first onto a genuinely unused exit, planned as one isolation-preserving batch so the move can't re-forge the link it just removed.
No connection → de-link
Every Account in the group is exit-less, so all of them get an exit rather than all-but-one.
Shared payment / shipping → distribute
Reassigns each Account a distinct card or address label drawn from your identity pool. It picks a label you already hold; it does not conjure a new card.
De-link only ever hands out a free, eligible exit
De-link is a proxy-pick path, like rotation and first assignment, and it runs the same eligibility rule as all of them.
A de-link can partly succeed
This is the one to read twice. A de-link can only move an Account onto an exit that is genuinely free — held by no other Account. If the pool has no free exit for one of the group, that Account keeps the shared exit it already had and stays flagged. It is never dropped to a direct connection to complete the move.
The result note says exactly what happened — "Moved 2 onto their own exit. 1 had no free exit and stays flagged — add more connections." — because a fix that changed nothing must not look identical to one that worked.
Distribute-identity has the same shape: it only draws labels not already used outside the group, so it can't forge a new link — and if your identity pool can't cover everyone, the overflow Account is left unset rather than sharing, so it too may still show until you add another label.
Realign a drifted clock
A proxied Account whose clock contradicts its exit region shows under Clock / region mismatch. Realign re-syncs it in one click — no network, no spend.
Each fix is its own decision
There's no "fix everything" button, and that's deliberate — a single button that bundles the harmless fixes with the costly ones is how an operator ends up doing something they didn't choose. The two that can cost you something confirm first: de-link and cycle-off-dead move exits behind a confirmation, and arming the token pool spends your solver balance behind one. Re-roll and realign just run.