The Professor’s off-ramp note:

• Off-ramp endpoint for Expeer resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• Expeer’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for Expeer is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the Expeer 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. Casefile triage on Expeer, the submission is read; a written assessment is delivered.
2. Forensic trace on Expeer, every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification, the Expeer endpoint is named.
4. Recovery filing on Expeer, packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of Expeer, the Professor follows the casefile until next-step documentation exists.

What the casefile records, chains and counterparties:

• Deposit-side chains in Expeer casefiles, typically the major chains (BTC, ETH) and the high-throughput stablecoin chains (Tron USDT, BSC USDT), with bridge crossings noted.
• Off-ramps named in Expeer packets, centralised exchanges that accept regulator-grade compliance filings.
• Filing options on Expeer, IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.