Current release status

Current release snapshot

This preview provides versioned lifecycle and architecture documentation, an available static/synthetic lumber guided tour, frozen declaration-backed TypeScript examples validated by the portal, current package and adapter identities, conformance evidence, and disclosed limitations. It also provides enrollment or interest submission where the current production implementation supports it, plus status documentation for planned integrations.

Review the synthetic examples; do not treat them as an instruction to install or execute unavailable packages.

What is available in the portal

The portal offers the static documentation and its current enrollment surface. It does not provide hosted execution, a live provider credential flow, or a public Core control plane. The portal provides no public registry distribution and makes no production-readiness claim. See Versioning and migrations for the contract identities and access boundary.

Current package chain and access

The private-preview package chain is documented in Versioning and migrations. Package access is inactive: enrollment does not create entitlement, and there is no public registry or download. The portal does not provide hosted execution or a live provider credential flow.

Surface and integration status

Planned means no current API, credential flow, availability promise, or release date. Retell is a private-preview Actions-only boundary, not hosted provider execution. These statuses come from the shared portal authority.

Documentation availability and interactive-surface availability are separate. The static/synthetic lumber guided tour at /builder/lumber is available now; the future interactive Playground, Trace, and Evaluator surfaces remain P3 and are not live. Guide remains P4 and is not implemented. P4A Knowledge Guide is planned for versioned, cited documentation and bounded guidance; P4B Support Guide is planned for authenticated, explicitly authorized, tenant/account-scoped read-only diagnostics with redacted schema-closed results and auditable handoff. Guide has no mutation or business-action tools and no arbitrary database, shell, HTTP, credential, provider-dispatch, reconciliation, entitlement-change, or business-mutation authority. A retrieved backend observation is not effect truth. The Trace, Evaluator, and reconciliation documentation is available to read now.

Known evidence gaps

Abrupt process-loss cleanup remains unproven. The current Actions projection mismatch also remains open unless the shared authority proves it corrected: the current PROJECTION_FAILED mapping is not the frozen target. Process-local reconciliation cannot survive restart. No exactly-once or automatic-retry claim follows. Read the Conformance checklist and Provider and verifier responsibilities for the bounded evidence and reconciliation detail.

What a developer can do now

1. Understand the lifecycle and map an existing application, provider, and independent verifier.
2. Identify trusted context, policy, and authoritative-state owners.
3. Review package-root interfaces and declaration-backed examples.
4. Inspect current conformance evidence and its limitations.
5. Submit interest or enrollment without treating confirmation as entitlement.
6. Prepare questions or an integration design for a future access decision.

These status boundaries show which architecture can be evaluated now, which evidence remains incomplete, and which capabilities must not yet be built into a production plan.

Where to read next

Start with Core lifecycle, then review Security and privacy, Conformance, and Versioning and migrations.