The annotation continues, off-ramp endpoint:

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

How a Capital Swift casefile becomes a evidence filing:

1. Triage on Capital Swift, submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on Capital Swift, deposit pathway mapped across chains, captured with chain of custody hashes.
3. Identify on Capital Swift, off-ramp endpoint matched to a named exchange counterparty.
4. File the Capital Swift 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 Capital Swift, the Professor stays on the casefile until a documented next step exists.

Reading-list, chains and exchanges in scope:

• Deposit-side chains in Capital Swift casefiles, typically the major chains (BTC, ETH) and the high-throughput stablecoin chains (Tron USDT, BSC USDT), with bridge crossings noted.
• Off-ramps named in Capital Swift packets, centralised exchanges that accept regulator-grade compliance filings.
• Filing options on Capital Swift, IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.