From the marginalia, the deposit pathway:

• Claimant deposit hashes, provided in the case submission and verified against the public ledger for Arbionswift.
• Forwarding wallets on the deposit chain, each hop documented with the forwarding tx hash and the consolidating wallet.
• Bridge events into chains where the operator can off-ramp at scale.
• Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
• Off-ramp endpoint, the centralised exchange deposit address holding the compliance lever.

The annotation continues, off-ramp endpoint:

• On the Arbionswift casefile, the off-ramp endpoint resolves to a centralised exchange, Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
• The off-ramp wallet for Arbionswift is run against chain-analytics datasets and the Professor’s own compliance feeds.
• A evidence packet is delivered to the named counterparty, the Arbionswift casefile is built to the off-ramp’s compliance standard.
• Where the off-ramp will not engage, Arbionswift escalates to IC3, state AG, and civil-discovery overlay.

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

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

What the Professor will never do, by policy:

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