The annotation continues, off-ramp endpoint:

• Swiss KMS casefiles end at a centralised exchange, Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
• Off-ramp wallet for Swiss KMS is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for Swiss KMS, the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Swiss KMS casefile.

Recovery sequence, from on-chain reading to filed packet:

1. First read on Swiss KMS, incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
2. Wallet trace on Swiss KMS, deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
3. Counterparty identification, the off-ramp endpoint for Swiss KMS is named to a centralised exchange wallet.
4. Packet filing on Swiss KMS, IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
5. Casefile follow-through, the Professor stays with Swiss KMS until a documented outcome or escalation step is on file.

Boundaries on every Swiss KMS casefile, never crossed:

• What the Professor will not do on Swiss KMS, ask for a seed phrase.
• What the Professor will not do on Swiss KMS, request remote-access logins.
• What the Professor will not do on Swiss KMS, demand cash up front.
• What the Professor will not do on Swiss KMS, promise a guarantee.
• What the Professor will not do on Swiss KMS, call you out of the blue.