IOSOR Learn
Sandbox reach is not production coverage
Sandbox destinations are for tests only. Never quote them as Live zones on a finance sheet or runway score.
Sandbox reach proves plumbing, not a sellable corridor. A green sandbox DLR must never become a Live zone claim on a quote, a day-1 runway board, or a catalog tile that finance already treated as sold.
IOSOR keeps test destinations labeled so engineering can smoke a path without inventing coverage. The moment a sandbox-only prefix lands on a Live sheet, the buyer is buying fiction — and the ledger will not save that conversation later. Treat sandbox greens as staging evidence only.
Label test destinations as non-Live
Tag every sandbox destination list as test-only in the console export. If a prefix appears only in sandbox reach, it must not land on the Live coverage sheet. Finance quotes Live zones only — never “it worked in sandbox so we can promise it”.
Keep a short owner for the export: who tagged the list, when it was pulled, and which key lane produced the DLR. Untagged exports are how sandbox noise becomes a quote attachment that sales forwards without reading the footer.
Block sandbox success from coverage claims
Wire a gate so a sandbox DLR cannot flip a catalog row to Live. Catalog Live still needs vault green and production smoke on the real corridor. Sandbox success is evidence the key and webhook path work — not that the corridor is sold or that quiet-hours routing is proven for paying traffic.
If product ever shows a Live badge after sandbox-only proof, demote the row and open an honesty ticket before the next sales call. Do not wait for a buyer dispute to discover the badge lied.
Export gap lists without sandbox noise
When you export coverage gaps for finance, strip sandbox-only prefixes first. Keep the gap list honest so quotes do not invent reach that only exists in the test lane. Pair the cleaned gap list with the Live sheet so finance sees one story end to end.
Re-export after any sandbox campaign so temporary test prefixes do not linger in the finance folder under last week’s filename.
Day-1 runway ignores sandbox greens
Runway score reads Live vault, webhook heartbeat freshness, and traffic_ok — not sandbox ticks from staging. Do not paint day-1 green because a staging OTP passed in the sandbox lane overnight.
If runway looks green while Live coverage still shows gaps, trust the coverage export — not the sandbox dashboard screenshot attached to the standup notes.
Related ops paths
- Coverage gap list for finance quote
- Catalog live gate matches vault
- Day-1 runway: what must be green
Start with IOSOR
Export sandbox reach and Live coverage side by side. Delete any sandbox-only prefix from the quote sheet. Re-run the catalog Live gate against vault and production smoke, not against sandbox DLR. Only then update the runway board and share the cleaned gap list with finance.
IOSOR takeaway
Sandbox reach is staging evidence. Strip sandbox-only prefixes from every finance quote, keep catalog Live behind vault and production smoke, and never paint day-1 runway green from a sandbox DLR.
Was this guide helpful?
Related guides
- Sandbox traffic must not hit the wallet
A Live key in a test harness is an incident. Detect leaked Live credentials, freeze holds, and rotate before pilot volume.
- Sandbox credentials that do not burn Live debit
Issue sandbox API keys that never hold or debit the prepaid wallet. Keep Live keys out of CI and prove cutover under Developers.