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

1. Triage on Active Resist, submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on Active Resist, deposit pathway mapped across chains, captured with chain of custody hashes.
3. Identify on Active Resist, off-ramp endpoint matched to a named exchange counterparty.
4. File the Active Resist packet, IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
5. Follow-through on Active Resist, the Professor stays on the casefile until a documented next step exists.

What we read in a Active Resist casefile:

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

Boundaries on every Active Resist casefile, never crossed:

• What the Professor will not do on Active Resist, ask for a seed phrase.
• What the Professor will not do on Active Resist, request remote-access logins.
• What the Professor will not do on Active Resist, demand cash up front.
• What the Professor will not do on Active Resist, promise a guarantee.
• What the Professor will not do on Active Resist, call you out of the blue.