II.
Page JSON
Structured · livepage:docs-v6-spec-and-roadmap
a5c.ai V6 Spec And Roadmap json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "page:docs-v6-spec-and-roadmap",
"_kind": "Page",
"_file": "wiki/docs/v6-spec-and-roadmap.md",
"_cluster": "wiki",
"attributes": {
"nodeKind": "Page",
"sourcePath": "docs/v6-spec-and-roadmap/README.md",
"sourceKind": "repo-docs",
"title": "a5c.ai V6 Spec And Roadmap",
"displayName": "a5c.ai V6 Spec And Roadmap",
"slug": "docs/v6-spec-and-roadmap",
"articlePath": "wiki/docs/v6-spec-and-roadmap/README.md",
"article": "\n# a5c.ai V6 Spec And Roadmap\n\nThis directory documents a pragmatic V6 evolution for the Babysitter stack. The intent is not to describe the biggest possible modular future. The intent is to define the smallest architecture change that is worth shipping, can be validated against the current repository, and leaves room for later extraction if the seams prove real.\n\n## Current Position\n\nThe repository already contains the important building blocks:\n\n- `packages/sdk` is the stable center of gravity.\n- `packages/babysitter` and `packages/babysitter-agent` provide the CLI and agent runtime.\n- `plugins/` contains the real harness integrations and their packaging constraints.\n- The adversarial reviews show that a broad \"split everything into many packages\" plan is not yet justified.\n\nV6 therefore treats adversarial analysis as a design input, not an appendix.\n\n## What V6 Is\n\nV6 is a staged architecture program with three goals:\n\n1. Reduce accidental coupling in the current stack where there is already a proven seam.\n2. Improve naming, documentation, and validation so future extractions are deliberate instead of aspirational.\n3. Ship changes in slices that can be rolled back without destabilizing the existing toolchain.\n\n## What V6 Is Not\n\nV6 does not currently commit to:\n\n- a full package explosion across runtime, platform, governance, memory, cost, and observability,\n- a distributed or remotely coordinated plugin architecture as a first move,\n- speculative security or isolation guarantees that are not backed by implementation and validation artifacts,\n- performance claims without a measurement method and fallback plan.\n\n## Reading Order\n\nStart here:\n\n1. [System Overview](system-overview.md)\n2. [Glossary](glossary.md)\n3. [Unified Stack Architecture](unified-stack-architecture.md)\n4. [Stack Guide](stack-guide.md)\n5. [V6 Vision](v6-vision.md)\n6. [V6 Architecture Specification](v6-architecture-specification.md)\n7. [V6 Implementation Roadmap](v6-implementation-roadmap.md)\n8. [Package Specifications](package-specs.md)\n\nUse these as constraints:\n\n- [Current State Analysis](current-state.md)\n- [Architecture Comparison](architecture-comparison.md)\n- [V6 Architecture Specification](v6-architecture-specification.md)\n\n## Document Map\n\nCore planning documents:\n\n- [System Overview](system-overview.md) - current system boundaries and ecosystem position\n- [Glossary](glossary.md) - canonical terminology for the unified Babysitter, agent-mux, and mux-support stack\n- [Unified Stack Architecture](unified-stack-architecture.md) - how the current monorepo stack fits together end to end\n- [Stack Guide](stack-guide.md) - where to start reading and which package/docs own which concerns\n- [Current State Analysis](current-state.md) - repository reality and pain points\n- [V6 Vision](v6-vision.md) - principles, non-goals, and decision filters\n- [V6 Architecture Specification](v6-architecture-specification.md) - normative architecture for the next executable stage\n- [V6 Implementation Roadmap](v6-implementation-roadmap.md) - gated rollout plan with entry, exit, and kill criteria\n- [Package Specifications](package-specs.md) - bounded package responsibilities and extraction triggers\n\nSupporting modules:\n\n- [Agent-Mux Integration](agent-mux-integration.md)\n- [Performance & Documentation](performance-docs.md)\n- [Testing Framework](testing-framework.md)\n- [Security Architecture](security-architecture.md)\n- [Plugin Ecosystem](plugin-ecosystem.md)\n\n## First Executable Slice\n\nThe currently selected first executable V6 slice is the `@a5c-ai/babysitter-agent` seam contract. It keeps the existing package boundary intact while making runtime-domain ownership, subpath exports, and validation gates explicit.\n\n- Decision record: [ADR-001: Babysitter-Agent Seam Contract As The First Executable V6 Slice](./decisions/ADR-001-babysitter-agent-seam-contract.md)\n- Repo-level validation command: `npm run verify:v6:seams`\n\n## Implementation\n\nImplementation-phase docs live under `implementation/` and describe what each roadmap phase is allowed to ship without promoting deferred package vocabulary into scope.\n\n## Decision Records\n\nDecision records for concrete V6 structural moves live under `decisions/`. If a proposed rename, extraction, or seam change does not have a decision record, it is still design exploration rather than an accepted V6 slice.\n\n## Maturity Standard\n\nEach major V6 document should answer five questions clearly:\n\n1. What is normative now?\n2. What is deferred?\n3. What has been invalidated by adversarial review?\n4. How will the claim be measured or validated?\n5. What is the rollback path if the change fails?\n\nIf a section cannot answer those questions, it is design exploration rather than specification.\n\n## Status\n\n- Status: In revision\n- Version: 6.0.0 draft\n- Last updated: April 2026\n",
"documents": []
},
"outgoingEdges": [
{
"from": "page:docs-v6-spec-and-roadmap",
"to": "page:docs-v6-spec-and-roadmap-agent-mux-integration",
"kind": "contains_page"
},
{
"from": "page:docs-v6-spec-and-roadmap",
"to": "page:docs-v6-spec-and-roadmap-architecture-comparison",
"kind": "contains_page"
},
{
"from": "page:docs-v6-spec-and-roadmap",
"to": "page:docs-v6-spec-and-roadmap-current-state",
"kind": "contains_page"
},
{
"from": "page:docs-v6-spec-and-roadmap",
"to": "page:docs-v6-spec-and-roadmap-decisions",
"kind": "contains_page"
},
{
"from": "page:docs-v6-spec-and-roadmap",
"to": "page:docs-v6-spec-and-roadmap-dependencies-resources",
"kind": "contains_page"
},
{
"from": "page:docs-v6-spec-and-roadmap",
"to": "page:docs-v6-spec-and-roadmap-glossary",
"kind": "contains_page"
},
{
"from": "page:docs-v6-spec-and-roadmap",
"to": "page:docs-v6-spec-and-roadmap-implementation",
"kind": "contains_page"
},
{
"from": "page:docs-v6-spec-and-roadmap",
"to": "page:docs-v6-spec-and-roadmap-package-specs",
"kind": "contains_page"
},
{
"from": "page:docs-v6-spec-and-roadmap",
"to": "page:docs-v6-spec-and-roadmap-performance-docs",
"kind": "contains_page"
},
{
"from": "page:docs-v6-spec-and-roadmap",
"to": "page:docs-v6-spec-and-roadmap-plugin-ecosystem",
"kind": "contains_page"
},
{
"from": "page:docs-v6-spec-and-roadmap",
"to": "page:docs-v6-spec-and-roadmap-security-architecture",
"kind": "contains_page"
},
{
"from": "page:docs-v6-spec-and-roadmap",
"to": "page:docs-v6-spec-and-roadmap-stack-guide",
"kind": "contains_page"
},
{
"from": "page:docs-v6-spec-and-roadmap",
"to": "page:docs-v6-spec-and-roadmap-system-overview",
"kind": "contains_page"
},
{
"from": "page:docs-v6-spec-and-roadmap",
"to": "page:docs-v6-spec-and-roadmap-testing-framework",
"kind": "contains_page"
},
{
"from": "page:docs-v6-spec-and-roadmap",
"to": "page:docs-v6-spec-and-roadmap-unified-stack-architecture",
"kind": "contains_page"
},
{
"from": "page:docs-v6-spec-and-roadmap",
"to": "page:docs-v6-spec-and-roadmap-v6-architecture-specification",
"kind": "contains_page"
},
{
"from": "page:docs-v6-spec-and-roadmap",
"to": "page:docs-v6-spec-and-roadmap-v6-implementation-roadmap",
"kind": "contains_page"
},
{
"from": "page:docs-v6-spec-and-roadmap",
"to": "page:docs-v6-spec-and-roadmap-v6-vision",
"kind": "contains_page"
}
],
"incomingEdges": [
{
"from": "page:docs",
"to": "page:docs-v6-spec-and-roadmap",
"kind": "contains_page"
}
]
}