Release channels

AgentPlat 1.1.0 is published under npm latest across all 66 coordinated packages. See the verified distribution record and adoption guide. Governed autonomy is opt-in; existing instruction-driven definitions keep their behavior. Jev remains optional.

Stable 1.x releases follow the stability contract. Prereleases use next and must never promote latest. Stable promotion requires successful public checks, exact artifact verification, reference integration validation, and clean registry consumers for the entire coordinated release.

Install matching stable versions:

pnpm add @agentplat/framework@1.1.0 @agentplat/sessions@1.1.0

See the production and migration guide (opens in a new tab). Historical observations below describe previews; they do not override the stable 1.x policy.

0.3.0-alpha.4 was the coordinated Evidence and Trust preview. This paragraph describes that historical release, not the current npm tag. Consult the component maturity matrix for dated distribution observations and verify tags before installing. That release added scoped Evidence lifecycle, deterministic multidimensional Trust Profiles, policy-exact eligibility, contradiction, quarantine and recovery, while retaining Alpha 1/2 Mesh and Alpha 3 Inference Control defaults and contracts. Source examples use local package links and can be ahead of the registry. Outside the repository, verify availability and select the coordinated next channel explicitly.

pnpm add @agentplat/trust@next

Trust exposes a browser-safe root and pure mesh-records normalizers. Explicit server-only adapters live at @agentplat/mesh/trust and @agentplat/inference-control/trust. Only calls routed through those opt-in adapters receive Trust filtering or restriction; direct Mesh, provider, handler and dispatcher calls keep their existing behavior.

Historically, session/browser APIs remained on next until the reference Next.js controls, public contract tests, package smoke test, downstream validation and a stable API review are all green for a promotion candidate. latest is intentionally not advanced merely because a preview release is published.

New scoped packages can receive latest from npm on their first publication even when published with next; npm does not permit removing the only version's latest tag. This caveat applies to the first publication of @agentplat/trust, as it did when the four Agent Mesh packages were introduced in Alpha 1. Consumers should still install the coordinated channel explicitly while the framework is in preview.

The owner-authorized release-level OIDC profile (opens in a new tab) prepares one verified cohort for one protected deployment approval. Its setup is in progress; enablement follows verification of every npm publisher relationship. The existing staged workflow remains available for historical cohorts.