Developer docs · Published boundary
Build with explicit boundaries.
Use these guides to understand the public health contract, private synthetic workflow model, and the controls expected of future operational integrations.
Read availability first. Documentation explains current source and product direction; it does not grant production access. Never place credentials, customer data, or provider payloads in browser code or support messages.
Choose your path
Public contract
Quickstart
Understand liveness, readiness, and the intentionally narrow public schema.
Read the guide →Private previewAuthentication & scope
Keep identity, workspace, capability, and environment authority server-derived.
Review access →Private synthetic previewCorrection lifecycle
Follow a held order through correction, evidence, approval, and local release.
Follow the lifecycle →Design guidanceReliability
Handle retries, idempotency, stale revisions, and unknown outcomes safely.
Design for failure →GeneratedAPI reference
Read the allowlisted operations and response schemas generated from OpenAPI.
Browse reference →Design previewCLI & MCP
Understand the intended operator-tooling model without mistaking it for a released distribution.
Review MCP →Availability model
| Label | What you may rely on |
|---|---|
| Public contract | The allowlisted schema is published, but no unauthenticated production API host is advertised. |
| Private preview | Access requires explicit provisioning and remains bounded to authorised synthetic evaluation. |
| In source | Code and tests exist; deployment, composition, provider acceptance, and customer use are separate proof. |
| Design guidance or roadmap | Use it for planning, not as an executable or available product contract. |
Integration principles
- Derive identity and workspace scope on the server.
- Bind decisions and retries to stable operation identities and exact record revisions.
- Treat timeouts as unknown outcomes until reconciled.
- Keep local release separate from carrier execution and source-system writeback.
- Preserve enough evidence for an operator to explain what happened without exposing sensitive payloads.