The annotation continues, off-ramp endpoint:

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

The Professor’s recovery note for Apex500:

1. Triage on Apex500, submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on Apex500, deposit pathway mapped across chains, captured with chain of custody hashes.
3. Identify on Apex500, off-ramp endpoint matched to a named exchange counterparty.
4. File the Apex500 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 Apex500, the Professor stays on the casefile until a documented next step exists.

Recovery scammers do these things; the Professor never does:

• Apex500 policy, seed phrases are never requested.
• Apex500 policy, remote-access logins are never requested.
• Apex500 policy, no upfront cash retainer to scope.
• Apex500 policy, no guaranteed-recovery language. None.
• Apex500 policy, no unsolicited calls. The Professor responds in writing only.