Afghanistan Proxies

Use the same client, endpoint, protocol, browser state, and acceptance rule for both routes. Verify each observed exit independently and retain country labels on every row so results cannot be merged into an ambiguous regional total. Keep the AFG run manifest with client, protocol, network, selector, session rule, authorized endpoint, expected response, exit source, outcome code, and timestamps. Reconcile the manifest with all results before calculating a pass rate. Use only an endpoint permitted for the Afghanistan test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

Separate invalid destination responses, connection failures, duplicate observations, oversized assets, accidental retries, and client overhead. The breakdown shows what can be corrected without pretending every consumed unit produced value. Syrian Arab Republic (19,851) and Oman (17,569) are the closest Asia historical-count entries around Afghanistan. Use those labels to prevent mixed datasets, not to infer supply, quality, latency, or precision. Keep AFG comparator rows labelled and diagnose the requested Afghanistan route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Approve ongoing use only with a written retest trigger and rollback point. A historical success should not be presented as current evidence after the client, route configuration, target, or acceptance rule changes. Complete the AFG decision table before ordering Afghanistan access: product, precision, supported client protocol, rotation or stickiness need, sample and retry bounds, accepted output, usage basis, and evidence owner. Re-run it after configuration drift. Reject any Afghanistan conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat AFG verification after a material configuration change.