Côte d'Ivoire Proxies

Run the baseline, change exactly one documented component, and repeat the same acceptance checks. Keep both result sets even when the second is better so the effect is reviewable and rollback remains possible. Prepare the CIV evidence fields before connecting: authorization, test case, client and version, selected network, protocol, selector, session setting, exit check, target response class, timestamp, and stop-rule status. Never backfill a missing field with an assumption. Use only an endpoint permitted for the Côte d'Ivoire test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

A local refusal, proxy authentication error, SOCKS handshake problem, TLS error, and destination denial belong to different owners. Preserve the earliest failing boundary and correct that layer before repeating the country test. Côte d'Ivoire sits beside Mozambique (7,651) and Mayotte (7,348) in the Africa historical-count ordering. Preserve the country labels. Combining their observations would erase the distinction the buyer is trying to validate. Keep CIV comparator rows labelled and diagnose the requested Côte d'Ivoire route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Buy country-targeted access only when the pilot meets the required observed-country rate under a declared geolocation source and sample rule. Leave narrower precision out of the promise unless separately proven. The CIV purchase gate combines confirmed Côte d'Ivoire routing with the selected product, maintained protocol, required session behavior, accepted-response definition, finite sample, retries, and cost measure. Repeat the gate after material change rather than relying on catalogue rank. Reject any Côte d'Ivoire conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat CIV verification after a material configuration change.