The Professor’s off-ramp note:

• MuxCap off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The MuxCap off-ramp address is matched to known compliance feeds, the Professor’s standing dataset plus chain-analytics references.
• Compliance leverage is applied at the named counterparty for MuxCap, the packet meets the off-ramp’s published compliance standard.
• When the MuxCap off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

Recovery pathway, how this casefile moves toward filing:

1. Submission triage, MuxCap casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace, MuxCap deposit and forwarding wallets captured.
3. Endpoint identification, MuxCap off-ramp wallet named.
4. Filing, MuxCap packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow, MuxCap stays on file until a documented next step is reached.

What the Professor will never do, by policy:

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