New Caledonia 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 NCL 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 New Caledonia test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

A successful connection can still carry an application error, while a valid JSON body can be stale or personalized. Retain response identifiers and timestamps and avoid turning any difference into a geographic claim without a matching control. The maintained Oceania ordering places New Caledonia next to Fiji, recorded at 11,572, and French Polynesia, recorded at 8,191. Catalogue adjacency describes the annual dataset only and cannot supply missing route evidence. Keep NCL comparator rows labelled and diagnose the requested New Caledonia 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 NCL decision table before ordering New Caledonia 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 New Caledonia conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat NCL verification after a material configuration change.