Standard DTC Runtime

• Control Plane — owns Experience configuration, consumer deployment state, revisions, publish gating and domain intent, plus the Catalog, Fulfillment, clinical and Results authority the storefront reads.
• Consumer runtime — a separately deployed application that renders the Standard DTC Storefront and Patient Portal. It stores no catalog, pricing, clinical or result data of its own.

The published runtime resolves the laboratory from the requested domain and serves only a published revision of a live deployment. An unknown domain, unpublished deployment or missing authority renders nothing for that laboratory rather than a substitute. The reference storefront is isolated to its own demonstration address and is never served for a laboratory domain.

• Private preview — opened from Experience with a short-lived signed grant the platform verifies; it shows the exact current draft revision for one Sandbox workspace and is read-only.
• Published runtime — serves the published revision publicly after the publish gate passes.

The storefront lists only storefront-eligible tests: active, visible and available tests with a storefront address. Biomarkers come from the canonical test-to-biomarker relationship. Featured tests are the configured featured set intersected with the current storefront Catalog.

• Ordering eligibility — self-order, provider review required or not available — is resolved by the platform per test and region; the runtime never infers it.
• One cart represents one patient, and each test appears at most once.
• Transactions are submitted only through supported platform interfaces.

• A Production payment-provider contract is not configured, so live consumer payment is not available.
• A canonical multi-item order transaction is not available.
• Managed DNS and TLS for laboratory domains are provisioned externally and may be pending for a given laboratory.
• Collection-site listing and provider-fee contracts are not available to the consumer runtime.