Reading the wallets — ZTMFX.COM casefile:

• Claimant deposit hashes — provided in the case submission and verified against the public ledger for ZTMFX.COM.
• Forwarding wallets on the deposit chain — each hop documented with the forwarding tx hash and the consolidating wallet.
• Bridge events into chains where the operator can off-ramp at scale.
• Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
• Off-ramp endpoint — the centralised exchange deposit address holding the compliance lever.

The annotation continues — off-ramp endpoint:

• ZTMFX.COM’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 ZTMFX.COM off-ramp wallet against historical laundering throughput.
• The ZTMFX.COM packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for ZTMFX.COM, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

Pathway to recovery — what happens after the trail is mapped:

1. First read on ZTMFX.COM — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
2. Wallet trace on ZTMFX.COM — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
3. Counterparty identification — the off-ramp endpoint for ZTMFX.COM is named to a centralised exchange wallet.
4. Packet filing on ZTMFX.COM — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
5. Casefile follow-through — the Professor stays with ZTMFX.COM until a documented outcome or escalation step is on file.

What the on-chain reading covers:

• Deposit-side chains in ZTMFX.COM 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 ZTMFX.COM packets — centralised exchanges that accept regulator-grade compliance filings.
• Filing options on ZTMFX.COM — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

Boundaries on every ZTMFX.COM casefile — never crossed:

• Recovery scammers do these things on ZTMFX.COM; the Professor never does — request seed phrases.
• Recovery scammers do these things on ZTMFX.COM; the Professor never does — request remote logins.
• Recovery scammers do these things on ZTMFX.COM; the Professor never does — demand upfront cash.
• Recovery scammers do these things on ZTMFX.COM; the Professor never does — guarantee a recovery.
• Recovery scammers do these things on ZTMFX.COM; the Professor never does — call you unsolicited.

Trace summary — funds that left yaibrokers.com:

• Deposit transaction hashes from the claimant wallet to the YAIBrokers platform receiving address.
• Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
• Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
• Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
• Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

From the lectern — off-ramp identification:

• YAIBrokers’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 YAIBrokers off-ramp wallet against historical laundering throughput.
• The YAIBrokers packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for YAIBrokers, 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. First read on YAIBrokers — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
2. Wallet trace on YAIBrokers — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
3. Counterparty identification — the off-ramp endpoint for YAIBrokers is named to a centralised exchange wallet.
4. Packet filing on YAIBrokers — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
5. Casefile follow-through — the Professor stays with YAIBrokers until a documented outcome or escalation step is on file.

What we read in a YAIBrokers casefile:

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

Lines we never cross — by published policy:

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

Reading the wallets — Phemex casefile:

• Deposit-side hashes from claimant wallets into Phemex’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.

Off-ramp map — where the funds left the chain:

• Phemex off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The Phemex 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 Phemex — the packet meets the off-ramp’s published compliance standard.
• When the Phemex off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

Recovery pathway — how this casefile moves toward filing:

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

What the Professor tracks across Phemex casefiles:

• Chains tracked on Phemex — Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on Phemex — named exchange counterparties with public compliance contacts.
• Filings supported on Phemex — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

What is never asked of a claimant:

• Recovery scammers do these things on Phemex; the Professor never does — request seed phrases.
• Recovery scammers do these things on Phemex; the Professor never does — request remote logins.
• Recovery scammers do these things on Phemex; the Professor never does — demand upfront cash.
• Recovery scammers do these things on Phemex; the Professor never does — guarantee a recovery.
• Recovery scammers do these things on Phemex; the Professor never does — call you unsolicited.

Trace summary — funds that left americanfxtrading.us:

• Deposit transaction hashes from the claimant wallet to the American FX platform receiving address.
• Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
• Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
• Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
• Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

Off-ramp summary — American FX casefile:

• American FX off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The American FX 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 American FX — the packet meets the off-ramp’s published compliance standard.
• When the American FX off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

Filing pathway — the next step after the off-ramp is identified:

1. Submission triage — American FX casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace — American FX deposit and forwarding wallets captured.
3. Endpoint identification — American FX off-ramp wallet named.
4. Filing — American FX packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow — American FX stays on file until a documented next step is reached.

What we read in a American FX casefile:

• Deposit + forwarding chains for American FX — Bitcoin, Ethereum, Tron USDT-TRC20, plus the smart-contract chains (BSC, Polygon, Avalanche, Arbitrum, Optimism) that cross via bridges.
• Off-ramps the American FX casefile may resolve to — centralised exchanges that respond to compliance filings.
• Filing pathways on American FX — IC3, state AG, off-ramp compliance, and civil-discovery overlay.

What the Professor will never do — by policy:

• On the American FX casefile — never request a seed phrase. Ever.
• On the American FX casefile — never request remote-access logins to a wallet or exchange.
• On the American FX casefile — never demand an upfront cash retainer to scope the matter.
• On the American FX casefile — never promise a guaranteed recovery. The trail does not promise one.
• On the American FX casefile — never call the claimant unsolicited. Written-only.

Reading the wallets — Market Giants casefile:

• Deposit transaction hashes from the claimant wallet to the Market Giants platform receiving address.
• Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
• Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
• Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
• Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

Off-ramp map — where the funds left the chain:

• Market Giants casefiles end at a centralised exchange — Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
• Off-ramp wallet for Market Giants is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for Market Giants — the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Market Giants casefile.

How a Market Giants casefile becomes a regulator-ready filing:

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

Reading-list — chains and exchanges in scope:

• Chains tracked on Market Giants — Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on Market Giants — named exchange counterparties with public compliance contacts.
• Filings supported on Market Giants — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

Lines we never cross — by published policy:

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

Trace summary — funds that left lloyds-capital.net:

• Deposit transaction hashes from the claimant wallet to the Lloyds Capital platform receiving address.
• Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
• Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
• Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
• Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

The Professor’s off-ramp note:

• Endpoint counterparty in the Lloyds Capital casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• Lloyds Capital’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
• Leverage is applied to that named counterparty — the Lloyds Capital packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the Lloyds Capital off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

Filing pathway — the next step after the off-ramp is identified:

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

What the Professor tracks across Lloyds Capital casefiles:

• Deposit-side chains in Lloyds Capital 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 Lloyds Capital packets — centralised exchanges that accept regulator-grade compliance filings.
• Filing options on Lloyds Capital — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

Lines we never cross — by published policy:

• On the Lloyds Capital casefile — never request a seed phrase. Ever.
• On the Lloyds Capital casefile — never request remote-access logins to a wallet or exchange.
• On the Lloyds Capital casefile — never demand an upfront cash retainer to scope the matter.
• On the Lloyds Capital casefile — never promise a guaranteed recovery. The trail does not promise one.
• On the Lloyds Capital casefile — never call the claimant unsolicited. Written-only.

On-chain reading — wallet flow for Elcomercio IX:

• Claimant deposit hashes — provided in the case submission and verified against the public ledger for Elcomercio IX.
• Forwarding wallets on the deposit chain — each hop documented with the forwarding tx hash and the consolidating wallet.
• Bridge events into chains where the operator can off-ramp at scale.
• Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
• Off-ramp endpoint — the centralised exchange deposit address holding the compliance lever.

Off-ramp reading — exchange counterparty for Elcomercio IX:

• Elcomercio IX’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 Elcomercio IX off-ramp wallet against historical laundering throughput.
• The Elcomercio IX packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for Elcomercio IX, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

Pathway to recovery — what happens after the trail is mapped:

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

What the casefile records — chains and counterparties:

• Deposit + forwarding chains for Elcomercio IX — Bitcoin, Ethereum, Tron USDT-TRC20, plus the smart-contract chains (BSC, Polygon, Avalanche, Arbitrum, Optimism) that cross via bridges.
• Off-ramps the Elcomercio IX casefile may resolve to — centralised exchanges that respond to compliance filings.
• Filing pathways on Elcomercio IX — IC3, state AG, off-ramp compliance, and civil-discovery overlay.

What the Professor will never do — by policy:

• Hard line on Elcomercio IX — no seed-phrase requests, period.
• Hard line on Elcomercio IX — no remote logins requested.
• Hard line on Elcomercio IX — no upfront cash retainer.
• Hard line on Elcomercio IX — no guarantee language.
• Hard line on Elcomercio IX — no unsolicited phone outreach.

The annotation reads — wallet trace:

• Deposit-side hashes from claimant wallets into Apex Trade’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.

Off-ramp summary — Apex Trade casefile:

• Endpoint counterparty in the Apex Trade casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• Apex Trade’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
• Leverage is applied to that named counterparty — the Apex Trade packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the Apex Trade off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

Pathway to recovery — what happens after the trail is mapped:

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

What the casefile records — chains and counterparties:

• Deposit-side chains in Apex Trade 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 Apex Trade packets — centralised exchanges that accept regulator-grade compliance filings.
• Filing options on Apex Trade — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

Lines we never cross — by published policy:

• On the Apex Trade casefile — never request a seed phrase. Ever.
• On the Apex Trade casefile — never request remote-access logins to a wallet or exchange.
• On the Apex Trade casefile — never demand an upfront cash retainer to scope the matter.
• On the Apex Trade casefile — never promise a guaranteed recovery. The trail does not promise one.
• On the Apex Trade casefile — never call the claimant unsolicited. Written-only.

The annotation reads — wallet trace:

• Deposit transaction hashes from the claimant wallet to the AES platform receiving address.
• Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
• Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
• Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
• Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

Off-ramp reading — exchange counterparty for AES:

• On the AES casefile, the off-ramp endpoint resolves to a centralised exchange — Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
• The off-ramp wallet for AES is run against chain-analytics datasets and the Professor’s own compliance feeds.
• A regulator-ready packet is delivered to the named counterparty — the AES casefile is built to the off-ramp’s compliance standard.
• Where the off-ramp will not engage, AES escalates to IC3, state AG, and civil-discovery overlay.

The Professor’s recovery note for AES:

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

What the Professor tracks across AES casefiles:

• Deposit-side chains in AES 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 AES packets — centralised exchanges that accept regulator-grade compliance filings.
• Filing options on AES — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

Lines the Professor will not cross:

• Boundary on AES — seed phrases are off-limits.
• Boundary on AES — remote logins are off-limits.
• Boundary on AES — upfront cash retainers are off-limits.
• Boundary on AES — guaranteed-recovery promises are off-limits.
• Boundary on AES — unsolicited outbound contact is off-limits.

From the marginalia — the deposit pathway:

• Claimant deposit hashes — provided in the case submission and verified against the public ledger for Win Fast Solution.
• Forwarding wallets on the deposit chain — each hop documented with the forwarding tx hash and the consolidating wallet.
• Bridge events into chains where the operator can off-ramp at scale.
• Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
• Off-ramp endpoint — the centralised exchange deposit address holding the compliance lever.

Off-ramp map — where the funds left the chain:

• Endpoint counterparty in the Win Fast Solution casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• Win Fast Solution’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
• Leverage is applied to that named counterparty — the Win Fast Solution packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the Win Fast Solution off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

Filing pathway — the next step after the off-ramp is identified:

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

What the on-chain reading covers:

• Chains tracked on Win Fast Solution — Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on Win Fast Solution — named exchange counterparties with public compliance contacts.
• Filings supported on Win Fast Solution — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

Recovery scammers do these things; the Professor never does:

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