Mali Proxies

Hold the endpoint, protocol, credentials, and request constant while reopening the transport according to the documented client behavior. Report unique exits, repeats, failed observations, and sample size together; requests multiplexed on one connection are not independent rotations. Make the MLI log append-only during the pilot. Capture permission basis, intended selector, network and protocol, connection boundary, exit result, target response class, bytes where relevant, and UTC time. Apply the original stop condition without rewriting earlier rows. Use only an endpoint permitted for the Mali 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. Mali is positioned between the Africa records for Kenya at 21,970 and Equatorial Guinea at 16,685. These manually maintained totals are comparison context, not live product observations or substitutes for the requested country. Keep MLI comparator rows labelled and diagnose the requested Mali 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 multi-step work only if the authorized flow completes within the stated window often enough for the buyer-defined threshold. Re-test after changing the client or session rule; do not silently change both. The buyer's MLI acceptance sheet should state required protocol, product, country observation rate, continuity or rotation rule, maximum retries, and valid-response evidence. The Mali plan advances only when the pilot meets that sheet without excluding failures. Reject any Mali conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat MLI verification after a material configuration change.