Production readiness

1. Catalog and mappings — every offered item has an active, validated laboratory mapping.
2. Program — configuration is complete and the Program is eligible for Production promotion.
3. Fulfillment and serviceability — collection models, geography and locations produce safe decisions.
4. Laboratory connection — Production uses its own validated adapter, endpoint and credentials.
5. Clinical and order requirements — provider, subject and additional-order-question authority resolves without an unsafe fallback.
6. Commercial and governance — the applicable agreement, entitlement, evidence and approval gates are satisfied.
7. Activation — the server re-derives every requirement and creates the paired live Production workspace only when all gates pass.
8. Production Program — the eligible Program is promoted to Production, active and enabled independently of the workspace's LIVE label.
9. Partner API — register an active client, grant the Production Program, complete MFA step-up and issue the one-time Production credential.
10. Webhooks and external smoke — configure public HTTPS, retain the signing secret, verify signatures and complete a real external order/result rehearsal.

Activation is self-serve. When the owner requests activation, the server re-derives every canonical requirement itself — Production deployment facts, a validated adapter and a passing Production validation run, agreement, data-flow evidence, acceptance testing, the Production entitlement, and commercial eligibility — and finalizes the laboratory only if all of them are genuinely satisfied.

• Nothing is taken from the browser: the requesting client cannot assert readiness, and no screen can mark a laboratory live.
• Finalization is idempotent. Re-requesting an already-live laboratory changes nothing, and a live laboratory never returns to onboarding.
• An unmet requirement is returned as a named blocker instead of a pending human queue.

Human review is exception handling, not the normal path. A launch request can still be returned, blocked or rejected by Solia, and those states remain authoritative until the underlying issue is resolved.

Commercial authorization alone never grants live status: it satisfies only the commercial requirement, and every technical requirement is still re-derived and enforced.

• An active paid subscription, or a paid invoice on the commercial path, satisfies the commercial requirement.
• An authorized complimentary arrangement recorded by Solia also satisfies it. It is an authorization, not a payment, and is never presented as paid.
• A recorded waiver, where one exists, satisfies it on the same terms.
• A trial or setup-validation arrangement lets a laboratory configure, connect and validate, but is not sufficient for live operation.

Whatever the source, the outstanding requirement is stated truthfully in the Control Plane, and an expired authorization removes eligibility without altering configuration or Sandbox access.

A successful deployment is terminal for the laboratory: the six setup steps stay complete, no activation action is offered again, and the paired Sandbox remains available for synthetic testing. Partner API setup and the optional consumer Experience become ongoing management surfaces.

Production · LIVE means the Production workspace passed its activation gates. Individual Programs retain their own lifecycle and availability; a live workspace does not make every draft, paused or ungranted Program orderable.