The annotation continues, off-ramp endpoint:

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

The Professor’s recovery note for Fexoglobal:

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

What the casefile records, chains and counterparties:

• Chains tracked on Fexoglobal, 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 Fexoglobal, named exchange counterparties with public compliance contacts.
• Filings supported on Fexoglobal, IC3, state AG, off-ramp compliance, civil discovery, selected by the dollar value and the off-ramp’s responsiveness.

What the Professor will never do, by policy:

• Fexoglobal policy, seed phrases are never requested.
• Fexoglobal policy, remote-access logins are never requested.
• Fexoglobal policy, no upfront cash retainer to scope.
• Fexoglobal policy, no guaranteed-recovery language. None.
• Fexoglobal policy, no unsolicited calls. The Professor responds in writing only.