Israel Proxies

Use the same endpoint, timeout, and acceptance rule for the pilot. Preserve raw status and a safe evidence marker beside the assigned class, and review ambiguous cases without relabeling them merely to improve the reported result. The ISR result table should expose the denominator: planned attempts, valid responses, explicit failures, unresolved rows, and retries. Attach route and client configuration, exit evidence, response class, and time to each row so the calculation can be repeated. Use only an endpoint permitted for the Israel test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

A higher or lower stored count does not predict latency, availability, response quality, or destination acceptance. Use catalogue neighbours to discuss recorded breadth only and let controlled observations determine route fitness. Israel is positioned between the Asia records for Turkey at 248,694 and Iraq at 168,030. These manually maintained totals are comparison context, not live product observations or substitutes for the requested country. Keep ISR comparator rows labelled and diagnose the requested Israel route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Purchase only for a documented use that remains within source permissions and operational controls. Technical reachability is not an acceptance criterion by itself. ISR decision review should answer whether the Israel pilot met product support, country observation, protocol, session, valid-response, usage, and evidence requirements. If a necessary field is absent or the success rule moved, do not approve volume. Reject any Israel conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat ISR verification after a material configuration change.