DIAGNOSTIC METHOD / RB–M / ORDER BEFORE INFERENCE

Check the contract, then the path

The route desk separates address, edition, local attempt, alternate connection, and external status evidence. Each step answers a narrower question.

RULE 01 / INSTRUMENT SEPARATION

Methods stay separate

Name resolution, edition compatibility, a player’s connection attempt, and a destination status source are different observations. The Routeboard keeps them ordered and never averages them into one regional score or labels browser timing as Minecraft game ping.

RULE 02 / SEVEN RECEIPT FIELDS

REQUIRED

A measured claim needs its receipt

Any imported observation must name its method, target, vantage, address family, collection window, sample count, checked date, and caveat. This release imports none; ping, route, and player values therefore remain unavailable.

Method
Target
Vantage
Address family
Window
Sample count
Caveat

RULE 03 / HIGHER EVIDENCE BAR

Do not promote a symptom into a regional claim

A failed attempt can come from an address error, edition mismatch, account setting, local firewall, transient path fault, or destination issue. Deliberate restriction claims require sustained multi-network evidence and authoritative corroboration; this route desk does not make them.

RULE 04 / LOCAL BY DEFAULT

Privacy

01
The site sets no cookies, runs no analytics, and calls no data API at page load.
02
The route ticket and event conversion run in the browser; entered values are not transmitted.
03
With JavaScript unavailable, the static method, default ticket, source receipts, and manual recovery guidance remain readable.