II.
Page JSON
Structured · livepage:docs-v6-spec-and-roadmap-v6-1-stack-layer-map
Stack Layer Map — Atlas Graph to Package Mapping json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "page:docs-v6-spec-and-roadmap-v6-1-stack-layer-map",
"_kind": "Page",
"_file": "wiki/docs/v6-spec-and-roadmap/v6-1/stack-layer-map.md",
"_cluster": "wiki",
"attributes": {
"nodeKind": "Page",
"sourcePath": "docs/v6-spec-and-roadmap/v6.1/stack-layer-map.md",
"sourceKind": "repo-docs",
"title": "Stack Layer Map — Atlas Graph to Package Mapping",
"displayName": "Stack Layer Map — Atlas Graph to Package Mapping",
"slug": "docs/v6-spec-and-roadmap/v6-1/stack-layer-map",
"articlePath": "wiki/docs/v6-spec-and-roadmap/v6.1/stack-layer-map.md",
"article": "\n# Stack Layer Map — Atlas Graph to Package Mapping\n\n## The 14 Layers\n\nThe 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.\n\n## Layer Mapping\n\n### L1: Model\n**Scope:** Trained artifact and declared capability surface\n\n| Aspect | Value |\n|--------|-------|\n| Packages | `@a5c-ai/agent-catalog` (metadata only) |\n| Node Kinds | ModelVersion, ModelFamily, Modality (capabilities-and-models cluster) |\n| Graph Cluster | capabilities-and-models |\n| Maturity | Metadata only — no execution package |\n| Spec Coverage | Implicit in agent-catalog contract |\n\n**Gap:** Model capabilities are cataloged but not executable. No package owns model selection, routing, or capability negotiation at this layer.\n\n---\n\n### L2: Provider\n**Scope:** Hosted or self-hosted serving boundary\n\n| Aspect | Value |\n|--------|-------|\n| Packages | `@a5c-ai/transport-adapter` (proxy), `@a5c-ai/adapters-cli` (provider config) |\n| Node Kinds | Provider, ModelProviderProduct, ModelProviderVersion (compute + capabilities-and-models) |\n| Graph Cluster | compute |\n| Maturity | Partial — provider routing implemented in transport-adapter proxy |\n| Spec Coverage | v6.0 package-specs.md mentions transport-adapter |\n\n**Gap:** Provider concepts are split between transport-adapter (proxy) and adapters-cli (provider translation). No unified provider abstraction package.\n\n---\n\n### L3: Transport\n**Scope:** Wire and client path between agent core and provider\n\n| Aspect | Value |\n|--------|-------|\n| Packages | `@a5c-ai/transport-adapter` |\n| Node Kinds | TransportProxy, TransportClient, ModelTransportProtocol, TransportProtocol (compute + capabilities-and-models) |\n| Graph Cluster | compute |\n| Maturity | Implemented — HTTP proxy with codec translation |\n| Spec Coverage | transport-adapter README (marked deferred for full codec refactor) |\n\n**Gap:** Codec capabilities (tool schema translation, cost normalization) are planned but not fully implemented. The v6.0 plan had a codec architecture refactor that was started but not completed.\n\n---\n\n### L4: Agent-Core\n**Scope:** Inner loop and graph/turn semantics for one agent brain\n\n| Aspect | Value |\n|--------|-------|\n| Packages | `@a5c-ai/genty-core`, `@a5c-ai/comm-adapter` |\n| Node Kinds | AgentCoreImpl (agent-stack) |\n| Graph Cluster | agent-stack |\n| Maturity | **Mature** — Dual implementation path (unified + harness-neutral) |\n| Spec Coverage | v6.0 unified-stack-architecture.md, v6-architecture-specification.md |\n\n**Note:** Two packages implement this layer for different concerns: `genty-core` (unified babysitter loop) and `agent-comm-adapter` (harness-neutral dispatch). This is intentional per v6.0 spec.\n\n---\n\n### L5: Agent-Runtime\n**Scope:** Host process and operational runtime for an agent core\n\n| Aspect | Value |\n|--------|-------|\n| Packages | `@a5c-ai/genty-platform`, `@a5c-ai/comm-adapter` |\n| Node Kinds | AgentRuntimeImpl (agent-stack) |\n| Graph Cluster | agent-stack |\n| Maturity | **Mature** — agent-platform hosts the unified runtime; agent-comm-adapter hosts harness dispatch |\n| Spec Coverage | v6.0 unified-stack-architecture.md |\n\n---\n\n### L6: Agent-Platform\n**Scope:** Extension, distribution, launch, and ecosystem surface\n\n| Aspect | Value |\n|--------|-------|\n| Packages | `@a5c-ai/extensions-adapter`, `@a5c-ai/agent-catalog`, `@a5c-ai/genty-platform` |\n| Node Kinds | AgentPlatformImpl, Plugin, PluginTarget, PluginMarketplace, PluginArtifact (agent-stack + extensions) |\n| Graph Cluster | agent-stack, extensions |\n| Maturity | Partial — plugin compiler mature; deeper platform (team agents, marketplace identity) deferred |\n| Spec Coverage | v6.0 plugin-ecosystem.md |\n\n**Gap:** AgentPlatformImpl is defined in graph but has no standalone implementation package. Platform concerns are scattered across agent-platform, extensions-adapter, and agent-catalog.\n\n---\n\n### L7: Workspace\n**Scope:** Materialized working context the agent reads/writes/indexes\n\n| Aspect | Value |\n|--------|-------|\n| Packages | `@a5c-ai/babysitter-sdk` (run dirs), `@a5c-ai/genty-platform` (workspace management) |\n| Node Kinds | Workspace, Worktree, WorktreeSession (lifecycle) |\n| Graph Cluster | lifecycle |\n| Maturity | Partial — SDK owns `.a5c/runs/` layout; workspace materialization policy not formalized |\n| Spec Coverage | Implicit in SDK storage docs |\n\n**Gap:** No dedicated workspace abstraction. The concept of \"what the agent can see/modify\" is implicit in the SDK's run directory layout rather than an explicit workspace contract.\n\n---\n\n### L8: Execution\n**Scope:** Invocation environment for agent-driven tools and commands\n\n| Aspect | Value |\n|--------|-------|\n| Packages | `@a5c-ai/babysitter-sdk` (effects, tasks), `@a5c-ai/genty-platform` (tool dispatch) |\n| Node Kinds | Execution, Effect, Invocation (lifecycle) |\n| Graph Cluster | lifecycle |\n| Maturity | **Mature** — Effect model, task dispatch, shell/agent/orchestrator task kinds |\n| Spec Coverage | v6.0 v6-architecture-specification.md (effect lifecycle) |\n\n---\n\n### L9: Sandbox\n**Scope:** Policy-enforcement perimeter around execution and side effects\n\n| Aspect | Value |\n|--------|-------|\n| Packages | `@a5c-ai/tasks-adapter` (approval gates) |\n| Node Kinds | Sandbox, PermissionMode (lifecycle + security) |\n| Graph Cluster | lifecycle, security |\n| Maturity | Partial — tasks-adapter handles human approval; filesystem/network policy enforcement deferred |\n| Spec Coverage | v6.0 security-architecture.md |\n\n**Gap:** Sandbox as a policy enforcement layer (filesystem restrictions, network controls, resource limits) is aspirational. Only human approval gates are implemented.\n\n---\n\n### L10: Interaction\n**Scope:** User-facing action primitives (commands, keybindings, controls)\n\n| Aspect | Value |\n|--------|-------|\n| Packages | `@a5c-ai/adapters-cli`, `@a5c-ai/genty-tui`, `@a5c-ai/babysitter-sdk` (interaction module) |\n| Node Kinds | InteractionPrimitive, InteractionPattern, InteractionPrimitiveCategory (agent-stack + extensions) |\n| Graph Cluster | agent-stack, extensions |\n| Maturity | **Mature** — Rich interaction model across CLI, TUI, web surfaces |\n| Spec Coverage | Implicit across multiple docs |\n\n---\n\n### L11: Presentation\n**Scope:** Outermost rendering surface (TUI, CLI, web, IDE, API)\n\n| Aspect | Value |\n|--------|-------|\n| Packages | `@a5c-ai/genty-ui`, `@a5c-ai/genty-tui`, `@a5c-ai/genty-web-app`, `@a5c-ai/babysitter-observer-dashboard`, `@a5c-ai/genty-tui-plugins` |\n| Node Kinds | Presentation, AgentUIImpl, Dashboard (agent-stack + extensions) |\n| Graph Cluster | agent-stack, extensions |\n| Maturity | **Mature** — Multi-surface: TUI, CLI, web, mobile (Android/iOS), TV (Android TV/Apple TV), watch (watchOS/Wear OS) |\n| Spec Coverage | v6.0 unified-stack-architecture.md |\n\n---\n\n### L12: Knowledge Fabric\n**Scope:** Durable organizational knowledge, memory, retrieval, indexing\n\n| Aspect | Value |\n|--------|-------|\n| Packages | `@a5c-ai/agent-catalog`, `@a5c-ai/atlas` |\n| Node Kinds | KnowledgeFabricImpl, MemorySystem, RetrievalPipeline, KnowledgeSource, KnowledgeDomain (agent-stack + domain) |\n| Graph Cluster | agent-stack, domain |\n| Maturity | Partial — Atlas provides ontology/catalog; durable memory, RAG, and semantic retrieval are deferred |\n| Spec Coverage | v6.0 mentions knowledge fabric as deferred (§8.2) |\n\n**Gap:** The graph defines rich knowledge concepts (MemorySystem, RetrievalPipeline, VectorStore) but no package implements durable agent memory or semantic retrieval. agent-catalog is metadata-only.\n\n---\n\n### L13: Orchestration\n**Scope:** Control-plane primitives for agent work coordination\n\n| Aspect | Value |\n|--------|-------|\n| Packages | `@a5c-ai/babysitter-sdk`, `@a5c-ai/genty-platform` |\n| Node Kinds | OrchestrationPrimitive, Run, Phase, PhaseMachine, PhaseTransition, OrchestratorState (lifecycle) |\n| Graph Cluster | lifecycle |\n| Maturity | **Mature** — SDK owns effect model, replay engine, deterministic execution, event sourcing |\n| Spec Coverage | v6.0 v6-architecture-specification.md, unified-stack-architecture.md |\n\n**Note:** babysitter-sdk is intentionally the monolithic center of orchestration per v6.0 decision. Splitting into smaller packages was evaluated and rejected for pragmatic reasons.\n\n---\n\n### L14: Governance\n**Scope:** Policy, risk, compliance, audit, approval controls\n\n| Aspect | Value |\n|--------|-------|\n| Packages | `@a5c-ai/genty-platform` (governance module), `@a5c-ai/tasks-adapter` (approval routing), `@a5c-ai/atlas` (evidence/claims) |\n| Node Kinds | AgentGovernanceImpl, EvidencePolicy, Claim, TrustLevel (agent-stack + catalog-meta + trust) |\n| Graph Cluster | agent-stack, catalog-meta, trust |\n| Maturity | Partial — approval gates, evidence claims, trust levels defined; broader policy framework (NIST AI RMF, OWASP) aspirational |\n| Spec Coverage | v6.0 security-architecture.md |\n\n**Gap:** AgentGovernanceImpl is defined but implementation examples are sparse. The governance module in agent-platform exists but covers a narrow surface (plugin governance, hook validation).\n\n## Maturity Summary\n\n| Maturity | Layers | Count |\n|----------|--------|-------|\n| **Mature** | L4, L5, L8, L10, L11, L13 | 6 |\n| **Partial** | L2, L3, L6, L7, L9, L12, L14 | 7 |\n| **Metadata Only** | L1 | 1 |\n",
"documents": []
},
"outgoingEdges": [],
"incomingEdges": [
{
"from": "page:docs-v6-spec-and-roadmap-v6-1",
"to": "page:docs-v6-spec-and-roadmap-v6-1-stack-layer-map",
"kind": "contains_page"
}
]
}