Barbados Proxies

Begin with the smallest harmless request that proves the configuration. Preserve permission evidence and the effective scope beside the run, and stop when a quota, denial, challenge, access-control message, or owner instruction says to stop. The BRB audit trail should pair each request ID with allowed source, client configuration, network and protocol, session behavior, requested country, observed exit, response classification, time, and retry relation. Preserve stop signals without circumvention. Use only an endpoint permitted for the Barbados test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

A changed exit, expired application session, closed connection, and rejected request are different failures. Preserve which layer broke first so an application cookie issue is not reported as proxy instability. Guadeloupe's 14,447 and Saint Lucia's 13,395 form the nearest North America count references for Barbados. Use them to explain catalogue placement only; present supply, response quality, subnational accuracy, and permitted workload still require separate evidence. Keep BRB comparator rows labelled and diagnose the requested Barbados 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 Barbados decision is ready only when BRB 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 Barbados conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat BRB verification after a material configuration change.