Uganda Proxies

Validate each response against the expected shape before comparing values. Keep credentials, parameters, pagination, and request body fixed; classify missing fields, type changes, timeouts, and application errors separately from location-related differences. For UGA, retain one configuration record and one result record for every attempt. Include target permission, selector, network, protocol, connection reuse, observed country, response marker, error boundary, and UTC time. Stop rather than rotate around an explicit denial. Use only an endpoint permitted for the Uganda test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

When a result changes, compare versions, headers, session behavior, connection reuse, endpoint deployment, and evidence source before blaming the country route. Unknown drift makes the comparison inconclusive. Uganda's annual record is nearest to Somalia with 3,567 and Ethiopia with 3,203 in Africa. This ordering verifies catalogue placement only. Test each requested country separately for current routing and buyer acceptance. Keep UGA comparator rows labelled and diagnose the requested Uganda route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Choose the route for browser QA only when a second clean run reproduces the accepted observation and the exit country is independently verified. Retain the profile recipe so another reviewer can repeat it. The Uganda decision is ready only when UGA evidence covers country verification, application compatibility, session behavior, response classification, usage, and stop conditions. A pilot that changes endpoints or acceptance rules midway must be rerun or labelled inconclusive. Reject any Uganda conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat UGA verification after a material configuration change.