Montenegro Proxies

Compare the requested country, the gateway result if exposed, and an independent observation. When the sources conflict, keep both values and classify the attempt as unresolved rather than selecting the preferred answer. For MNE, preserve a configuration snapshot and chronological observations containing the authorized source, connection boundary, requested and observed country, protocol outcome, destination response, retry number, and UTC time. Do not overwrite the first failure with a later success. Use only an endpoint permitted for the Montenegro test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

Separate invalid destination responses, connection failures, duplicate observations, oversized assets, accidental retries, and client overhead. The breakdown shows what can be corrected without pretending every consumed unit produced value. Greece (8,377) and Serbia (7,950) are the closest Europe historical-count entries around Montenegro. Use those labels to prevent mixed datasets, not to infer supply, quality, latency, or precision. Keep MNE comparator rows labelled and diagnose the requested Montenegro 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. MNE decision review should answer whether the Montenegro 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 Montenegro conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat MNE verification after a material configuration change.