The Professor’s off-ramp note:

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

How a ITB casefile becomes a evidence filing:

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

What the casefile records, chains and counterparties:

• Deposit + forwarding chains for ITB, Bitcoin, Ethereum, Tron USDT-TRC20, plus the smart-contract chains (BSC, Polygon, Avalanche, Arbitrum, Optimism) that cross via bridges.
• Off-ramps the ITB casefile may resolve to, centralised exchanges that respond to compliance filings.
• Filing pathways on ITB, IC3, state AG, off-ramp compliance, and civil-discovery overlay.

Boundaries on every ITB casefile, never crossed:

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