The annotation continues, off-ramp endpoint:

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

Recovery sequence, from on-chain reading to filed packet:

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

Reading-list, chains and exchanges in scope:

• Chains tracked on Stoctex, Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on Stoctex, named exchange counterparties with public compliance contacts.
• Filings supported on Stoctex, IC3, state AG, off-ramp compliance, civil discovery, selected by the dollar value and the off-ramp’s responsiveness.

Lines the Professor will not cross:

• Boundary on Stoctex, seed phrases are off-limits.
• Boundary on Stoctex, remote logins are off-limits.
• Boundary on Stoctex, upfront cash retainers are off-limits.
• Boundary on Stoctex, guaranteed-recovery promises are off-limits.
• Boundary on Stoctex, unsolicited outbound contact is off-limits.