Component maturity
This is the editorial entry point for adoption status. Source availability,
registry distribution, executable checks and operational evidence answer
different questions. None implies another. AgentPlat 1.4.0 is published under npm latest across 70 coordinated packages. See the verified distribution record. The stability contract governs API compatibility independently from operational evidence.
Source and integration map
| Component | Source / available integration | Reproducible checks | Operational evidence / adopter obligations |
|---|---|---|---|
| Component | Published capability | Adoption boundary | |
| --- | --- | --- | |
| Framework, models and sessions | Runtime, framework, model adapters, tools, sessions and Redis adapter | Host supplies provider credentials, identity and durable session policy | |
| Agent Rooms and Planner | Rooms, API, PostgreSQL, Mesh/Temporal bridges, Planner engine and workflow bridge | Planner is opt-in; apply Rooms 019 and workflows 001 explicitly; configure authorization, prices, budgets and recovery | |
| Persistent memory and definitions | Stable-agent memory revisions and reviewed-definition coordinates | Separate opt-in memory ledger; host owns identity mapping, audience authorization, retention and UI | |
| Artifacts | Optional immutable artifacts, PostgreSQL CAS and event outbox | Register agent tools explicitly; apply adapter migrations; host owns authorization, delivery and retention | |
| Collective Runtime and workflows | Runtime, planning, workflow runners and PostgreSQL/Temporal adapters | Durable guarantees require configured persistent stores, timers and effect reconciliation | |
| Agent Mesh | Mesh, crypto, protocol, HTTP and PostgreSQL adapters | Bounded integration evidence; deployment owns key custody, membership and transport | |
| Inference Control, Trust and audit | Opt-in controls, eligibility and audit adapters | Only calls routed through configured integration points receive these controls | |
| Agent Morphogenesis | Experimental governed organizational evolution | Remains experimental in operational maturity; publication is not production qualification | |
| A2A, MCP, registry and work adapters | Optional protocol, registry, documentation and Asana integrations | Host supplies identity, network policy and authoritative execution/effect owners | |
| Simulation and conformance | Testing, simulation and adapter conformance packages | Scenarios are bounded and do not imply validation at production scale |
See the package allowlist (opens in a new tab) for the complete component inventory and the capability catalog (opens in a new tab) for advanced surfaces. This table groups packages; it does not certify every export or every combination of adapters.
Distribution
The protected 1.4.0 workflow published 70/70 packages at 1.4.0 under latest. It published 68 packages by OIDC and verified the two interactive bootstrap packages. The run checked package bytes, signatures, provenance and clean registry consumers, including PostgreSQL Planner and artifacts integrations, portable/durable consumers and npm on Node 22. See the workflow run (opens in a new tab) and release record. These consumer checks show bounded integration, not production-scale validation.
Evidence sources and maintenance
- Current frozen baseline (opens in a new tab) and V1 capability evidence catalog (opens in a new tab).
- Morphogenesis hardening evidence (opens in a new tab).
- Signed local/staging readiness profile (opens in a new tab): 22 scenarios over a bounded 30-minute profile at its recorded source commit.
- Research evidence classes (opens in a new tab): implementation, deterministic conformance, local operational profiles and empirical study results stay separate.
Update this matrix when an integration's documented status changes and link
its exact evidence. Do not silently expand the baseline or relabel historical
evidence as validation of the current checkout. Run verify:adoption-docs to
check adoption links, referenced exports and executable commands. Passing that
structural check does not establish usability, security or production readiness.