Lesotho Proxies

Treat the route as the only planned variable. Alternate reference and proxied observations, preserve their order, and compare status, redirect destination, response marker, and observed exit country instead of relying on a single screenshot. Create one LSO row per planned attempt: source permission, client version, network, protocol, redacted selector, observed exit, UTC time, response class, and decision. Keep the sample finite, preserve missing values, and stop on the declared control signal. Use only an endpoint permitted for the Lesotho test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

Separate server output from browser translation, saved preferences, experiments, extensions, and account data. If those inputs cannot be held constant, describe the observation as mixed rather than as proof of country-specific presentation. For annual catalogue context, compare Lesotho with Libya's 8,197 and Mozambique's 7,651 within Africa. Do not infer relative availability, quality, latency, or buyer value from that stored-number sequence. Keep LSO comparator rows labelled and diagnose the requested Lesotho 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 LSO decision table before ordering Lesotho 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 Lesotho conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat LSO verification after a material configuration change.