From the marginalia, the deposit pathway:

• Claimant-to-platform deposit transactions on the deposit chain used by Apex Signals.
• Operator-controlled forwarding wallets where deposits consolidate ahead of laundering or off-ramping.
• Cross-chain bridge events to chains with deeper exchange liquidity.
• Privacy-service interactions, where present in the trail.
• Off-ramp wallet, the named centralised-exchange endpoint.

The annotation continues, off-ramp endpoint:

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

How a Apex Signals casefile becomes a evidence filing:

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

What the Professor will never do, by policy:

• Hard line on Apex Signals, no seed-phrase requests, period.
• Hard line on Apex Signals, no remote logins requested.
• Hard line on Apex Signals, no upfront cash retainer.
• Hard line on Apex Signals, no guarantee language.
• Hard line on Apex Signals, no unsolicited phone outreach.