Off-ramp map, where the funds left the chain:

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

How a AuroraEx casefile becomes a evidence filing:

1. Casefile triage on AuroraEx, the submission is read; a written assessment is delivered.
2. Forensic trace on AuroraEx, every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification, the AuroraEx endpoint is named.
4. Recovery filing on AuroraEx, packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of AuroraEx, the Professor follows the casefile until next-step documentation exists.

What the Professor will never do, by policy:

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