The Professor’s off-ramp note:

• Bitindexcapital’s off-ramp endpoint, in this casefile, is the centralised exchange that holds compliance leverage, typically named in the packet alongside the deposit address.
• Chain-analytics datasets cross-reference the Bitindexcapital off-ramp wallet against historical laundering throughput.
• The Bitindexcapital packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for Bitindexcapital, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

Recovery pathway, how this casefile moves toward filing:

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

Boundaries on every Bitindexcapital casefile, never crossed:

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