Production readiness

1. Catalog and mappings — every offered item has an active, validated laboratory mapping.
2. Program — where a partner Program is offered, its configuration is complete and it 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.

A laboratory founder can start and complete the guided six-step setup and Sandbox testing without Solia involvement. Production activation is not self-serve today: when activation is requested, 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 Production promotion additionally remains paused in the platform until Solia's release authorization is in place.

• Nothing is taken from the browser: the requesting client cannot assert readiness, and no screen can mark a laboratory live.
• Step 6 separates technical readiness (fresh, environment-scoped reads; a failed or refreshing read counts as not ready) from business activation (plan, payment and a separate approval).
• 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.
• Native LIS connections (REST, FHIR R4, HL7 v2, SFTP, Edge) cannot be activated: they are implemented but disabled, and no vendor interface is certified. See Laboratory connectivity release status.

A launch request can be returned, blocked or rejected by Solia, and those states remain authoritative until the underlying issue is resolved.

• Setup steps 1–6, Control Plane configuration, Sandbox and integration testing are technical and free; completing them is not a subscription charge.
• Production promotion is paused in the app while an operator-led end-to-end verification is completed, even though the underlying platform guard is installed.
• Three future events are designed as the earliest commercial milestone: a deliberately launched live third-party Program, deliberate transactional Production Partner API enablement, or a provider-verified first paid laboratory-owned consumer order under a restricted first-order mode. None of these triggers is live; no milestone is recorded automatically.
• Solia bills laboratories for the platform through its existing billing provider (Mercury). That is separate from consumer payments, which a laboratory receives through its own processor.
• Billing status distinguishes plan selected, payment method authorized, invoice issued, provider-confirmed paid, active, approved waiver, grace, past due, suspended and canceled; anything without provider evidence is shown as unknown, never as paid.
• No click in the Control Plane grants billing, entitlements or Production by itself.

• The owner sees the selected plan and its terms before the first invoice is issued through the billing provider.
• Issuing an invoice is not payment. Billing begins when the provider confirms the first invoice is paid.
• A paid plan does not make the laboratory live; Production activation still requires every server-derived requirement.
• Finish later leaves plan, payment and readiness state unchanged.
• Effective Fulfillment Production readiness takes part in the final launch gate and is stricter than onboarding completion.

1. Register an API client — a client receives no access by default.
2. Grant the client a Production Program.
3. Issue a scoped credential deliberately, with step-up verification.
4. Configure the webhook endpoint separately.

• Laboratory Production activation — makes the workspace live; decided by the gates above.
• Program lifecycle — each Program keeps its own draft, active and paused state; Programs are not part of the core six-step setup.
• Consumer deployment publish — a separate, gated action for the optional storefront; activation does not publish it.
• Solia On Demand publication — the channel is enabled separately, and each ready offering is explicitly published or paused without changing DTC publication.
• Partner API credentials — issued after activation per client and Program grant with step-up verification.

• 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.

Selected source CI, rich draft completeness, technical connection success, listing and payment each establish different facts. No approved live native authority, clinical/vendor sign-off or hardened promotion is implied. G2/G4/G6/G7–G10 remain open and Production remains NO-GO.