The annotation continues, off-ramp endpoint:

• PTFX off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The PTFX 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 PTFX, the packet meets the off-ramp’s published compliance standard.
• When the PTFX off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

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

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

Lines the Professor will not cross:

• Boundary on PTFX, seed phrases are off-limits.
• Boundary on PTFX, remote logins are off-limits.
• Boundary on PTFX, upfront cash retainers are off-limits.
• Boundary on PTFX, guaranteed-recovery promises are off-limits.
• Boundary on PTFX, unsolicited outbound contact is off-limits.