The annotation continues, off-ramp endpoint:

• Off-ramp endpoint for FERGOFX resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• FERGOFX’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for FERGOFX is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the FERGOFX off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

Recovery pathway, how this casefile moves toward filing:

1. Triage on FERGOFX, submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on FERGOFX, deposit pathway mapped across chains, captured with chain of custody hashes.
3. Identify on FERGOFX, off-ramp endpoint matched to a named exchange counterparty.
4. File the FERGOFX packet, IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
5. Follow-through on FERGOFX, the Professor stays on the casefile until a documented next step exists.

What the Professor will never do, by policy:

• On the FERGOFX casefile, never request a seed phrase. Ever.
• On the FERGOFX casefile, never request remote-access logins to a wallet or exchange.
• On the FERGOFX casefile, never demand an upfront cash retainer to scope the matter.
• On the FERGOFX casefile, never promise a guaranteed recovery. The trail does not promise one.
• On the FERGOFX casefile, never call the claimant unsolicited. Written-only.