The annotation reads, wallet trace:

• Deposit-side hashes from claimant wallets into AH Capital’s receiving addresses.
• Operator forwarding wallets, deposit consolidation documented to chain of custody standards.
• Inter-chain bridge transactions when value moves toward off-ramp liquidity.
• Mixer/obfuscation events the operator routed through, where present.
• Final off-ramp endpoint and named counterparty exchange.

The annotation continues, off-ramp endpoint:

• AH Capital off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The AH Capital off-ramp address is matched to known compliance feeds, the Professor’s standing dataset plus chain-analytics references.
• Compliance leverage is applied at the named counterparty for AH Capital, the packet meets the off-ramp’s published compliance standard.
• When the AH Capital off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

The Professor’s recovery note for AH Capital:

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

What we read in a AH Capital casefile:

• Chains the Professor reads for AH Capital casefiles, BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
• Off-ramps named in AH Capital, major centralised venues with compliance desks that accept regulator-grade packets.
• Filing pathways available on AH Capital, IC3 for US claimants, state AG offices, off-ramp compliance, and civil-discovery overlay for high-value loss.