# Qurmmius Intelligence production-readiness gate

This gate is intentionally separate from tester feedback. It verifies the controls that can be proven with synthetic or redacted data before a real customer pilot.

## Enabled now

- **Golden evaluations:** `GET /api/qi/evaluations` runs 20 deterministic metadata-only cases for each active lane and returns counts and finding codes, never fixture payloads.
- **Durable audit:** the existing audit writer is enabled in production and remains required. Audit records contain request IDs, signed workspace identity, adapter, mode, redaction count, usage metadata, and a timestamp—not prompts, media, credentials, or plaintext.
- **Monitoring signals:** protected routes emit request IDs, structured audit log fields, rate-limit responses, and provider usage metadata. `/api/qi-health` exposes the non-secret configuration state.
- **Tenant isolation:** protected routes derive the workspace only from the signed QI session. A caller cannot select a different workspace by changing a request body or header.
- **Human approval:** `POST /api/qi/verify/action` validates reviewer metadata and, for provider enablement or customer-data access, requires a distinct second approval. It always returns `executed: false` and `execution_enabled: false`.
- **Billing staging:** `GET /api/qi/billing/catalog` exposes the non-secret Starter ($49/mo), Studio ($149/mo), and Platform ($399/mo) catalog. `POST /api/qi/checkout` is server-side only and requires explicit plan-price, terms, webhook, entitlement, audit, and signed-workspace gates.
- **Entitlement boundary:** `POST /api/qi/stripe-webhook` verifies the dedicated `QI_STRIPE_WEBHOOK_SECRET`, handles completed checkout, paid invoices, payment failures, and subscription deletion, and writes only scoped entitlement metadata. `GET /api/qi/entitlement` never returns credentials or raw Stripe payloads.
- **Cancellation path:** `POST /api/qi/customer-portal` creates a Stripe-hosted customer portal session for an already-linked customer, so customers can manage or cancel without a support-only obstacle.
- **Billing consent:** checkout requires explicit acknowledgement of the published refund policy and billing terms, and records both acknowledgements in Stripe metadata; an unchecked policy box cannot create a session.
- **Customer handoff:** the public [QI customer quickstart](/QI-CUSTOMER-QUICKSTART.md) explains first use, support contact, incident details, billing boundaries, and the non-secret health check without exposing credentials or pilot invite data.
- **Aggregate data plan:** [Data provider selection](/DATA-PROVIDER-SELECTION.md) records the staged OpenStreetMap/Open-Meteo/OpenAQ and partner-gateway choices, attribution/rate-limit requirements, and the owner-controlled activation contract.

## Intentionally gated

- **Tester review:** remains the next human step and is not automated here.
- **Live QI checkout:** enabled for invited workspaces after owner-approved verification. Production uses dedicated QI price IDs, webhook signing, entitlement and audit gates, and versioned policy acknowledgements. The production test-checkout route is disabled; re-enable it only in a non-production context for future QA. Existing company or product prices are not reused implicitly.
- **DeepFake Shield:** local preview, consent, purpose-limited, and human-reviewed only; no biometric decisions or automated takedowns.
- **LegacyVault:** synthetic dry-run only; no real unlock, release, deletion, keys, or plaintext.

Run the golden suite from the Intelligence page, then use the approval endpoint for a staged, human-reviewed change. Neither control authorizes production data access by itself.

For customer-facing operating instructions, use the [QI customer quickstart](/QI-CUSTOMER-QUICKSTART.md). Pilot invitations and tester review remain a separate owner-controlled step.