The annotation reads, wallet trace:

• Deposit confirmations from the claimant to Capital Harvest’s receiving wallet at clharvest.net.
• Forwarding-wallet pathway documented hop-by-hop with chain of custody hashes.
• Cross-chain bridge transactions where the operator routed value out of the deposit chain.
• Mixer or coin-join interactions, where applicable.
• Final off-ramp at a centralised exchange, the compliance counterparty named in the recovery filing.

Off-ramp reading, exchange counterparty for Capital Harvest:

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

How a Capital Harvest casefile becomes a evidence filing:

1. Casefile review on Capital Harvest, reading the submission against the no-go list.
2. Trace mapping on Capital Harvest, pathway documented to chain of custody standard.
3. Off-ramp naming on Capital Harvest, exchange endpoint identified.
4. Packet filing on Capital Harvest, to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on Capital Harvest.

Lines the Professor will not cross:

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