The Professor’s off-ramp note:

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

How a TradelogicFx casefile becomes a evidence filing:

1. Read the TradelogicFx submission, written go/no-go returned.
2. Map the TradelogicFx wallet trail, every hop captured with chain of custody hashes.
3. Name the TradelogicFx off-ramp, endpoint counterparty identified.
4. Build and file the TradelogicFx recovery packet, to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the TradelogicFx file, until written next steps exist.

Chains and off-ramps the Professor follows:

• Chains in scope for TradelogicFx, the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
• Off-ramps in scope for TradelogicFx, named centralised exchanges with compliance leverage.
• Filings supported on TradelogicFx, IC3, state AG, off-ramp desk, civil discovery as applicable.

Boundaries on every TradelogicFx casefile, never crossed:

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