Founder & IT onboarding, Step 5 and Step 6 authority

A laboratory founder can start the guided workflow alone. The same six steps are used by everyone; there is no separate IT wizard. Laboratory IT joins inside Step 5 through a technical handoff.

• Lab Admin — saves owner-facing onboarding and connection changes. Independent clinical mapping review requires separate authorized reviewer access; no role activates Production by itself.
• Operations — may view and contribute technical information, but cannot perform configuration-writing technical tasks, approve mappings or request Production.
• No onboarding role can grant billing, entitlements or Production by itself.

• Identifying the laboratory system records "Laboratory system identified". It does not mean the connection is configured or approved.
• A named LIS product is matched to a candidate starting package only. Candidate packages are descriptive; none is vendor certified.
• The executable path today is the HTTPS/JSON Solia Lab Contract, tested against the Sandbox test laboratory.
• If the laboratory needs a native interface, a managed integration request carries the IT handoff (product, version, interface type, network path) so Solia and laboratory IT can plan the connection.
• Step 5 completion requires canonical Sandbox evidence: an order, its acknowledgement and a result. Request progress is shown truthfully but never counts as readiness.

• Technical readiness is derived from fresh, environment-scoped reads. A failed, missing or still-refreshing read is shown as not ready, never as a remembered pass.
• Business activation (plan, payment, agreement) is separate. Paying never activates Production.
• The Partner API handoff appears only after a current, authoritative read shows the workspace is active.
• Production promotion is currently paused platform-wide pending Solia's release authorization.