Day-1 runway: what must be green

Day-1 runway is the smallest set of greens that make a production promise honest — not a feature tour. Four truths: vault secrets present and scoped, webhook heartbeat fresh (stale ≡ blocked), wallet at the pilot floor with named stop-lines, and one channel Live with delivered smoke. Everything else stays in setup.

IOSOR is white-label prepaid CPaaS. USD 20 is the pilot wallet floor, not an entry fee. Soft review near USD 1,000/month is a volume signal, not runway evidence. Distinct from the SMS API buyer checklist and sibling traffic_ok gate before pilot volume. Money: Prepaid hold before first debit. Keys: webhooks that survive launch. Stops: Wallet stop-lines before production.

Runway is not a feature checklist

Buyers confuse many catalog tiles with safe-to-send. Runway asks whether real money and messages can move on day one without lying about status.

A feature checklist can pass while runway fails. Keep lists linked; evidence separate.

Vault and keys before any Live badge

Live means secrets authenticate without pasting API keys into tickets or chat. Vault-green: credentials present, environment-scoped, rotatable, never in mobile clients. Do not promote sandbox keys while production secrets are missing.

Hygiene: verify signatures, rotate without dual-send windows, client errors free of upstream brands. Block Live if vault is empty or shared. Sequence: vault → smoke under pilot keys → production keys → Live.

Webhook heartbeat stale means blocked

A webhook that once returned 200 is not green. Heartbeat must be fresh: recent signed events on the Live path, consumer without silent drop, correlation IDs matching ledger rows. Stale heartbeat ≡ blocked — same as a missing secret.

Without a living event path, product says delivered while finance sees orphan debits and support cannot replay. HB age is a hard gate: older than policy → blocked or in setup until smoke restores freshness.

Wallet floor and one honest channel

Fund ≥ USD 20 so pilot holds and first debits are real. Prove hold → outcome → settle or release. Name stop-lines before production so a loop cannot drain the pilot overnight.

One honest channel = one Live product with vault green, fresh HB, delivered smoke export, white-label statuses, and a finance-ready ledger row. Others stay in setup or coming next.

Buyer checklist for day-1 runway

1. Vault green for the single intended Live channel — scoped, rotatable, no paste?
2. Webhook heartbeat fresh on that path (stale ≡ blocked)?
3. Wallet ≥ USD 20 with proven hold → debit / release?

4.

Start with IOSOR

Print a day-1 runway board before any Live badge: keys present and scoped, webhook heartbeat not stale, wallet able to take one hold, one channel proved end to end. A green product tile is not a green runway. Export the board with timestamps. This is a gate list, not a catalog tour.

IOSOR takeaway

Day-1 runway is a green board, not a feature walk.

Do: keep Live dark until every gate on that board is dated and proved.

Don't: flip Live from a product checklist, or treat a stale heartbeat as a yellow that can wait.