The annotation continues, off-ramp endpoint:

• PIPCOUNTS’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 PIPCOUNTS off-ramp wallet against historical laundering throughput.
• The PIPCOUNTS packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for PIPCOUNTS, 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. Triage on PIPCOUNTS, submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on PIPCOUNTS, deposit pathway mapped across chains, captured with chain of custody hashes.
3. Identify on PIPCOUNTS, off-ramp endpoint matched to a named exchange counterparty.
4. File the PIPCOUNTS 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 PIPCOUNTS, the Professor stays on the casefile until a documented next step exists.

Boundaries on every PIPCOUNTS casefile, never crossed:

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