IOSOR

IOSOR Learn

Catalog Live gate must match vault reality

Flip Live on a catalog product only when vault and delivered smoke are green — never because sales needs a checkbox.

A Live chip in the service catalog is a production promise. If vault secrets are missing or smoke never delivered, the chip is theatre — prepaid buyers pay for a path that cannot run. This page is the catalog Live ↔ vault gate, not a rich-channel template deep-dive and not day-1 runway.

Related: Live / In setup / Coming next: honest buyer path, Failover gates before any Live badge, traffic_ok gate before pilot volume, Template catalog before channel Live, Wallet stop-lines before production.

IOSOR is white-label prepaid. USD 20 funds vault+smoke evidence on one product; soft review near USD 1,000/month prices a sales-only Live flip as incident debt. Clients never see upstream rail brands on the chip.

Live means vault + smoke, not a sales checkbox

Catalog Live only when: (1) vault entries for that product are present and scoped, (2) delivered smoke under pilot keys shows an exportable terminal outcome, (3) client status stays white-label. Miss any → keep In setup. Sibling: Live / In setup / Coming next: honest buyer path. Do not promote from a slide while vault is orange.

Gate evidence before the chip flips

Gate Pass evidence Keep In setup
Vault Secrets present, scoped, rotated Missing / expired / shared paste
Smoke Delivered pilot send, exportable outcome UI green without delivery
Money path Hold + one debit identity under smoke Second settle or unpaid accept
White-label Statuses without upstream brand strings Brand leak in webhook or UI
Owner Named human who may flip / demote Live “Anyone in sales”

Soft USD 1,000/month treats checkbox Live as a catalog incident; USD 20 proves one product through the table once. Wallet stops bind: Wallet stop-lines before production.

Not rich-channel vault gates and not day-1 runway

Rich-channel vault/template gates ask whether WhatsApp or RCS templates and secrets are ready. Day-1 runway asks which launch signals must be green for traffic_ok. This page asks: does the Live chip for product X match vault+smoke for X today? Voice can be vault-green while WA stays In setup. Failover Live gates are adjacent — not a substitute: Failover gates before any Live badge. Heartbeat: traffic_ok gate before pilot volume.

Demote when vault goes red

Live is not sticky. If vault expires, smoke regresses, or brand strings leak, demote to In setup the same day. Log who flipped, who demoted, which gate failed. Template classes still need approved catalog before class-level Live: Template catalog before channel Live.

Buyer checklist for Live ↔ vault match

  1. Vault green for this product — not shared paste lore?
  2. Delivered smoke exported under pilot keys?

Start with IOSOR

Open the catalog chip for one product. Check secrets for that product only: present, scoped, not a shared paste. Run a delivered pilot send under those keys and export the terminal outcome. Flip Live only when both rows exist. If secrets expire or the pilot send regresses, demote to In setup the same day and log who flipped.

IOSOR takeaway

Do: treat the Live chip as a production promise for this product today. Secrets green plus an exportable delivered outcome — then the chip. Demote when either gate goes red.

Don't: leave Live up as a sales checkbox while secrets are missing. A green UI without a delivered export is theatre. Voice being ready does not make another channel Live.

Was this guide helpful?

Related guides