Trust & feature honesty

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.

Integration matrix Pilot pricing & SKUs

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.

Pilot ready

Core workflow is qualified for design partner or paid pilot SOW. Documented caveats apply — not “production certified for all tenants.”

Where: Order hub, storefront, KDS, production, packing, billing

Sales: Safe to demo and contract in pilot scope with Era 17 ICP gates.

BETA

Engineering shipped; partner credentials, staging smoke, or migration may still be required before a LIVE claim.

Where: Marketplace, Woo/Shopify until live proof, AI modules, delivery adapters

Sales: Show Integration Health — never hide the badge in customer demos.

Preview

UI and routes exist; behavior may change. Visible when “Show all modules” is on — not default pilot nav.

Where: Early nav entries, experimental dashboards

Sales: Do not promise GA dates unless on public roadmap with evidence.

Skipped

SKIPPED

Honest state: smoke not run, credentials missing, or ops vault not configured. SKIPPED is not PASS — we refuse fake green tiles.

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.

Placeholder

Shell route or scaffold without operational backend. Do not sell until matrix promotes to BETA or LIVE.

Where: Nav maturity hide list, preview-only routes

Sales: Redirect to pilot_ready modules in scope.

Internal

Platform or CS tooling — not a customer-facing product promise.

Where: Platform admin, impersonation, ops vault

Sales: Not for prospect decks.

Live

LIVE

Your workspace passed live-integration definition of done: real credentials, webhook proof, honest artifact on file.

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.

Security overview

Tenant-scoped queries, server-side secrets, Prisma-backed data access, and production safety docs — designed with enterprise-ready controls.

Data handling

Customer data export tools are available; destructive deletion is handled through reviewed workflows.

Infrastructure

Designed for managed Postgres/Supabase, Vercel deployment, encrypted env vars, and audit-ready setup docs.

Authentication

Supabase Auth-backed sessions with owner/staff roles and billing-aware access controls.

Payment security

Stripe handles payment processing. OS Kitchen stores subscription identifiers, not raw card data.

Integrations security

Credentials are stored server-side; production access depends on proper customer-provided credentials.

Webhook security

Webhook signing checks are documented and used where provider secrets are configured.

Data export

Workspace exports exist for orders, customers, products, and integration metadata.

Responsible AI note

AI/copilot experiences should be treated as assistance, not authoritative legal, tax, nutrition, or operational decisions.

Compliance roadmap

Formal compliance certifications are future roadmap items, not current claims.

Platform / admin access

Platform routes are internal-only; end-customers are redirected. Sensitive support actions should be permission-gated and audited when enabled.

Security questions

Contact support with security questions, vendor review forms, or responsible disclosure notes.

OS Kitchen does not currently claim SOC 2, HIPAA, PCI compliance, GDPR compliance, or food labeling compliance. Full enterprise SSO/SCIM is roadmap unless explicitly enabled for your tenant in writing. SKIPPED integration states are honest — not production LIVE claims.

Service snapshot (engineering) · AI modules (honest positioning) · Data rights template · Pilot pricing SKUs

OSKitchen