Questions this page must answer
- Does the storefront check actually require a Jordan network-origin sample?
- First reproduce the owned flow directly with explicit language and currency controls. Add a Jordan route only for a written network-origin hypothesis; if those controls answer the question, a proxy adds cost without decision value.
- How will the Jordan test separate language direction and JOD display from the exit?
- Run Arabic and English as named cases, set the locale deliberately, and record writing direction, currency label, item total and error copy. Hold the URL, catalogue fixture, cookies, account, address and device constant so a difference is not automatically attributed to the route.
- Which Jordan product and geographic precision can the current evidence support?
- Use only a network reported by the fresh compatibility response. The observed live route was empty, and the repository derives country and ASN coverage from active source configurations; without an unambiguous active selector record, country is the maximum authored precision and even that remains runtime-gated.
- Does the smallest current order fit the bounded Jordan checkout matrix?
- Read the payable minimum, traffic unit and validity from the current product row. Budget a direct control and the permitted Arabic-English cases, keep failed and inconclusive observations in the ledger, and do not scale because of a historical country count.