The annotation continues, off-ramp endpoint:

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

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

1. Read the igwold.com aka globalfds.net submission, written go/no-go returned.
2. Map the igwold.com aka globalfds.net wallet trail, every hop captured with chain of custody hashes.
3. Name the igwold.com aka globalfds.net off-ramp, endpoint counterparty identified.
4. Build and file the igwold.com aka globalfds.net recovery packet, to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the igwold.com aka globalfds.net file, until written next steps exist.

What the Professor will never do, by policy:

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