Proposals¶
Status: Design workspace
Audience: Maintainers, deployment operators, and builders
Last updated: 2026-08-03
Proposals describe shaped architectural directions as they move from design to implementation. They are release-independent until accepted through the roadmap and architecture decision process.
Active proposals¶
| Proposal | Status | Purpose |
|---|---|---|
| v0.14.0 C4 Model: Agent Capabilities and Durable Storage | Implementing | Define the breaking Deep Agents 0.7, skill bundle, Agent-owned MCP, and durable storage architecture |
| v0.14.0 MCP Runtime and Authentication Contract | Implementing | Specify Agent-owned MCP config, direct MCP OAuth, workload token exchange, per-server discovery, readiness, and executable security criteria |
| Sandboxed skill package registry | Superseded | Rejected name-based registry design retained as architectural history |
| Curated OpenTelemetry Agent tracing | Implemented on v0.13 branch | Replace noisy, duplicative traces and estimated usage with a bounded Agent-run trace and provider-authoritative Usage Events |
Status meanings¶
| Status | Meaning |
|---|---|
| Draft | Open for design review; no implementation commitment |
| Accepted | Approved through governance and ready for roadmap scheduling |
| Implementing | Backed by an active roadmap item and implementation work |
| Implemented | Delivered and reflected in the code-derived architecture |
| Superseded | Replaced by another proposal or architecture decision |
A draft proposal must not be presented as current architecture. Once implementation starts, follow the architecture change workflow and create an Architecture Decision Record (ADR) when the change affects a public protocol, persistence authority, execution boundary, or extension model.