docs/v6-spec-and-roadmap/v6-1
v6.1 Specification — Layer-to-Package Gap Analysis guide
This directory contains the v6.1 specification documents derived from a gap analysis between the Atlas graph (source of truth for the a5c agent stack), the actual monorepo packages, and the v6.0 spec documentation.
Pages in this section
Start with the section hub, then move sideways into adjacent pages when you need more detail.
Agent Layer Capabilities — What agent-core, agent-runtime, and agent-platform Should Actually Do
PageThe renames and restructuring are plumbing. This document defines the capabilities each layer package needs to be a super-capable implementation, grounded in the atlas graph node kind definitions.
wiki/docs/v6-spec-and-roadmap/v6.1/agent-layer-capabilities.md
The atlas graph models two AgentProducts (agent-platform, adapters) each decomposed into Core/Runtime/Platform/UI implementations. This document maps the graph's decomposition to the actual packages and identifies what needs to change.
wiki/docs/v6-spec-and-roadmap/v6.1/agent-stack-decomposition.md
Complete inventory of gaps between the Atlas graph (source of truth) and the current implementation. Each gap is classified by severity and type.
wiki/docs/v6-spec-and-roadmap/v6.1/gap-inventory.md
The Atlas graph is the source of truth. This document lists every task needed to make the repo's package names, structure, and capabilities match the 9 canonical muxes, 14 stack layers, and the agent-stack node kinds defined in the graph.
wiki/docs/v6-spec-and-roadmap/v6.1/graph-alignment-tasks.md
The Atlas graph defines 9 canonical muxes as the bridging abstractions of the a5c agent stack. Each adapter normalizes one concern across all supported agent products. This document maps each graph adapter to its implementing package(s) and identifies concrete gaps.
wiki/docs/v6-spec-and-roadmap/v6.1/mux-architecture-gaps.md
This document identifies naming mismatches between the Atlas graph (source of truth) and the actual monorepo package names. Misalignment creates confusion for contributors and agents navigating the codebase.
wiki/docs/v6-spec-and-roadmap/v6.1/naming-alignment.md
The atlas graph defines 14 stack layers (stack-layers cluster). Each layer represents an architectural concern in the a5c agent stack. This document maps each layer to its implementing packages, primary graph node kinds, and current implementation maturity.
wiki/docs/v6-spec-and-roadmap/v6.1/stack-layer-map.md
Work items derived from the gap inventory, ordered by impact and feasibility.
wiki/docs/v6-spec-and-roadmap/v6.1/v6.1-priorities.md
v6.1 Specification — Layer-to-Package Gap Analysis
This directory contains the v6.1 specification documents derived from a gap analysis between the Atlas graph (source of truth for the a5c agent stack), the actual monorepo packages, and the v6.0 spec documentation.
Reading Order
1. stack-layer-map.md — Canonical mapping of all 14 atlas stack layers to packages, node kinds, and implementation status 2. naming-alignment.md — Naming mismatches between graph concepts and package names, with proposed renames 3. gap-inventory.md — Complete inventory of gaps: missing implementations, deferred capabilities, fragmented ownership 4. v6.1-priorities.md — Prioritized work items for v6.1 based on gap severity and user impact
Source of Truth
The Atlas graph (packages/atlas/graph/) is the canonical source of truth for the agent stack architecture. The 14 stack layers, their node kinds, and their relationships define what the system IS — packages implement what the graph describes.
When a package doesn't match the graph, the package needs to change (or the graph needs a deliberate amendment with a decision record).