docs/v6-spec-and-roadmap
a5c.ai V6 Spec And Roadmap guide
This 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.
Pages in this section
Start with the section hub, then move sideways into adjacent pages when you need more detail.
→ Documentation Index(README.md) | Related: Unified Stack Architecture(unified-stack-architecture.md) | Package Specifications(package-specs.md)
wiki/docs/v6-spec-and-roadmap/agent-mux-integration.md
This document provides an architectural comparison between the current a5c.ai agent stack and the V6 architecture, highlighting the key differences in design philosophy, component organization, and system capabilities.
wiki/docs/v6-spec-and-roadmap/architecture-comparison.md
→ Documentation Index(README.md) | Previous: System Overview(system-overview.md) | Next: V6 Architecture Vision(v6-vision.md)
wiki/docs/v6-spec-and-roadmap/current-state.md
Decision Records
PageUse this section when you need the current accepted decision rather than the surrounding exploration.
wiki/docs/v6-spec-and-roadmap/decisions/index.md
→ Documentation Index(README.md) | Related: Implementation Roadmap(v6-implementation-roadmap.md) | Agent-Mux Integration(agent-mux-integration.md)
wiki/docs/v6-spec-and-roadmap/dependencies-resources.md
Glossary
Page→ Documentation Index(README.md) | Related: Unified Stack Architecture(unified-stack-architecture.md) | Stack Guide(stack-guide.md)
wiki/docs/v6-spec-and-roadmap/glossary.md
This section groups the executable V6 rollout documents by delivery phase.
wiki/docs/v6-spec-and-roadmap/implementation/index.md
→ Documentation Index(README.md) | Previous: V6 Vision(v6-vision.md)
wiki/docs/v6-spec-and-roadmap/package-specs.md
→ Documentation Index(README.md) | Previous: Testing Framework(testing-framework.md)
wiki/docs/v6-spec-and-roadmap/performance-docs.md
→ Documentation Index(README.md) | Previous: Package Specifications(package-specs.md) | Next: Security Architecture(security-architecture.md)
wiki/docs/v6-spec-and-roadmap/plugin-ecosystem.md
→ Documentation Index(README.md) | Previous: Plugin Ecosystem(plugin-ecosystem.md) | Next: Testing Framework(testing-framework.md)
wiki/docs/v6-spec-and-roadmap/security-architecture.md
Stack Guide
Page→ Documentation Index(README.md) | Related: Glossary(glossary.md) | Unified Stack Architecture(unified-stack-architecture.md)
wiki/docs/v6-spec-and-roadmap/stack-guide.md
System Overview
Page→ Documentation Index(README.md) | Next: Current State Analysis(current-state.md)
wiki/docs/v6-spec-and-roadmap/system-overview.md
→ Documentation Index(./README.md) | Previous: Security Architecture(./security-architecture.md) | Next: Performance Considerations(./performance-docs.md)
wiki/docs/v6-spec-and-roadmap/testing-framework.md
→ Documentation Index(README.md) | Related: Glossary(glossary.md) | Stack Guide(stack-guide.md)
wiki/docs/v6-spec-and-roadmap/unified-stack-architecture.md
V6 is a controlled architecture evolution of the existing Babysitter stack. It does not assume that the repository should be decomposed into a large family of new packages immediately. Instead, V6 defines a bounded target state:
wiki/docs/v6-spec-and-roadmap/v6-architecture-specification.md
This roadmap is not a wish list. Each phase exists to answer a concrete question about viability. A phase only starts when its entry criteria are met and only continues while its validation signals remain positive.
wiki/docs/v6-spec-and-roadmap/v6-implementation-roadmap.md
→ Documentation Index(README.md) | Previous: Current State(current-state.md) | Next: Package Specifications(package-specs.md)
wiki/docs/v6-spec-and-roadmap/v6-vision.md
a5c.ai V6 Spec And Roadmap
This 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.
Current Position
The repository already contains the important building blocks:
packages/sdkis the stable center of gravity.packages/babysitterandpackages/babysitter-agentprovide the CLI and agent runtime.plugins/contains the real harness integrations and their packaging constraints.- The adversarial reviews show that a broad "split everything into many packages" plan is not yet justified.
V6 therefore treats adversarial analysis as a design input, not an appendix.
What V6 Is
V6 is a staged architecture program with three goals:
1. Reduce accidental coupling in the current stack where there is already a proven seam. 2. Improve naming, documentation, and validation so future extractions are deliberate instead of aspirational. 3. Ship changes in slices that can be rolled back without destabilizing the existing toolchain.
What V6 Is Not
V6 does not currently commit to:
- a full package explosion across runtime, platform, governance, memory, cost, and observability,
- a distributed or remotely coordinated plugin architecture as a first move,
- speculative security or isolation guarantees that are not backed by implementation and validation artifacts,
- performance claims without a measurement method and fallback plan.
Reading Order
Start here:
1. System Overview 2. Glossary 3. Unified Stack Architecture 4. Stack Guide 5. V6 Vision 6. V6 Architecture Specification 7. V6 Implementation Roadmap 8. Package Specifications
Use these as constraints:
Document Map
Core planning documents:
- System Overview - current system boundaries and ecosystem position
- Glossary - canonical terminology for the unified Babysitter, agent-mux, and mux-support stack
- Unified Stack Architecture - how the current monorepo stack fits together end to end
- Stack Guide - where to start reading and which package/docs own which concerns
- Current State Analysis - repository reality and pain points
- V6 Vision - principles, non-goals, and decision filters
- V6 Architecture Specification - normative architecture for the next executable stage
- V6 Implementation Roadmap - gated rollout plan with entry, exit, and kill criteria
- Package Specifications - bounded package responsibilities and extraction triggers
Supporting modules:
- Agent-Mux Integration
- Performance & Documentation
- Testing Framework
- Security Architecture
- Plugin Ecosystem
First Executable Slice
The 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.
- Decision record: ADR-001: Babysitter-Agent Seam Contract As The First Executable V6 Slice
- Repo-level validation command:
npm run verify:v6:seams
Implementation
Implementation-phase docs live under implementation/ and describe what each roadmap phase is allowed to ship without promoting deferred package vocabulary into scope.
Decision Records
Decision 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.
Maturity Standard
Each major V6 document should answer five questions clearly:
1. What is normative now? 2. What is deferred? 3. What has been invalidated by adversarial review? 4. How will the claim be measured or validated? 5. What is the rollback path if the change fails?
If a section cannot answer those questions, it is design exploration rather than specification.
Status
- Status: In revision
- Version: 6.0.0 draft
- Last updated: April 2026