We label what is live, beta, or skipped — so rush hour never surprises you.
OS Kitchen uses BETA, Preview, Pilot ready, and SKIPPED badges across dashboard nav and Integration Health. This page explains each label for operators, sales, and security reviewers. Security practices are summarized below.
Feature honesty
BETA, Preview, and SKIPPED — what the badges mean
OS Kitchen labels every integration and module with honest maturity. Labels appear in dashboard nav, Integration Health, and sales demos — they are not errors to hide.
Where: Order hub, storefront, KDS, production, packing, billing
Sales: Safe to demo and contract in pilot scope with Era 17 ICP gates.
Where: Marketplace, Woo/Shopify until live proof, AI modules, delivery adapters
Sales: Show Integration Health — never hide the badge in customer demos.
Where: Early nav entries, experimental dashboards
Sales: Do not promise GA dates unless on public roadmap with evidence.
Where: Integration Health Center, P0 orchestrator artifacts, channel live proof
Sales: Explain what is needed to move SKIPPED → PASS; never imply the channel is live.
Where: Nav maturity hide list, preview-only routes
Sales: Redirect to pilot_ready modules in scope.
Where: Platform admin, impersonation, ops vault
Sales: Not for prospect decks.
Where: Integration Health when smoke PASS — rare at pre-scale (June 2026 baseline: 0 LIVE in registry)
Sales: Only claim LIVE when Integration Health shows PASS with artifact link.
Integration Health rule
PASS = verified in your workspace · SKIPPED = honest “not proven yet” · FAILED = action required. We never upgrade SKIPPED to PASS in marketing copy or GO/NO-GO artifacts without captured smoke proof.
Integration capability matrix · Integration Health (sign in)
FAQ
Why show SKIPPED instead of hiding broken integrations?
Operators lose orders when a “connected” badge lies. Integration Health and SKIPPED states are our honesty moat vs Toast/Square dashboards that assume partner stacks work.
Does BETA mean broken?
No — it means not certified LIVE for every tenant yet. Many BETA modules work in staging with your credentials; sales must qualify scope in LOI/SOW.
Can sales remove badges in demos?
No — forbidden claims training requires visible BETA/SKIPPED labels. Run MARKETING_CLAIMS_STRICT=1 npm run verify-claims before external materials.
Where is the source of truth?
docs/feature-maturity-matrix.md for modules; Integration Health Center for your workspace; artifacts/pilot-gono-go-summary.json for pilot GO/NO-GO.
Security & data handling
Enterprise-ready control language below — not formal SOC 2, HIPAA, or PCI attestation claims.
Service snapshot (engineering) · AI modules (honest positioning) · Data rights template · Pilot pricing SKUs