page:docs-v6-spec-and-roadmap-stack-guide
Stack Guide reference
→ Documentation Index(README.md) | Related: Glossary(glossary.md) | Unified Stack Architecture(unified-stack-architecture.md)
Stack Guide
→ Documentation Index | Related: Glossary | Unified Stack Architecture
Purpose
This guide is the fast path for navigating the unified stack. Use it when you need to know where to start reading, which package owns a concern, and which docs are normative versus supporting context.
Start Here
If you are new to the stack, read these in order:
1. System Overview 2. Glossary 3. Unified Stack Architecture 4. V6 Architecture Specification 5. Package Specifications
Then branch into the area you are actually changing.
Before proposing a new seam, run the active validation cue for the first executable V6 slice:
npm run verify:v6:seams
If You Need To Change Orchestration
Read:
Work mainly in:
packages/babysitter-sdkpackages/babysitterpackages/genty/platformlibrary/- project-local
.a5c/processes/
If You Need To Change Harness Dispatch
Read:
Work mainly in:
packages/adapters/corepackages/adapters/adapterspackages/adapters/clipackages/adapters/sdkpackages/adapters/gateway
If You Need To Change Hook Behavior
Read:
packages/adapters/hooks/README.mdpackages/adapters/hooks/ARCHITECTURE.md- Agent-Adapter Integration
Work mainly in:
packages/adapters/hooks/corepackages/adapters/hooks/clipackages/adapters/hooks/adapter-*plugins/babysitter-unified/hooks/
If You Need To Change Plugin Packaging
Read:
packages/extensions-adapter/unified_plugin_system_spec.mdplugins/babysitter-unified/README.template.md- per-harness plugin README files under
plugins/babysitter-unified/per-harness/
Work mainly in:
packages/extensions-adapterplugins/babysitter-unified- concrete bundles under
plugins/babysitter-*
If You Need To Change Human Approval Or Breakpoint Routing
Read:
packages/tasks-adapter/specs/architecture.md- Testing Framework
Work mainly in:
packages/tasks-adapterpackages/babysitter-sdkbreakpoint integration- related hook and plugin surfaces if the transport changes
If You Need To Change UI Surfaces
Read:
packages/adapters/README.md- package README files under
packages/adapters/*
Work mainly in:
packages/adapters/uipackages/adapters/webuipackages/adapters/tuipackages/adapters/mobile-*packages/adapters/tv-*packages/adapters/watch-*docs-site/orpackages/atlas/webuiwhere relevant
Source-Of-Truth Map
Use this rule of thumb:
| Concern | Primary source of truth | Supporting references |
|---|---|---|
| V6 architecture scope | docs/v6-spec-and-roadmap/ | package READMEs, adversarial analyses |
| Orchestration runtime behavior | packages/babysitter-sdk, packages/babysitter, packages/genty/platform | V6 docs, CLI docs |
| Harness dispatch behavior | packages/adapters/* and docs/adapters/ | V6 integration docs |
| Hook normalization | packages/adapters/hooks/* | per-harness plugin docs |
| Unified plugin packaging | packages/extensions-adapter, plugins/babysitter-unified/ | install READMEs for concrete bundles |
| Breakpoint routing | packages/tasks-adapter | SDK integration docs |
Practical Rules
- Start from the package that already owns the behavior before proposing a new layer.
- If a document describes a future package or layer, check whether V6 marks it as deferred.
- Treat installable plugin bundles as real compatibility surfaces even when the unified plugin source exists.
- Use package names and paths when discussing ownership; use architecture terms only when they map to a real current seam.
- Treat validation commands as part of the architecture surface. If a seam has no repo path and no active validation cue, it is still design exploration.
---
**Related Documents**: Current State | Glossary | Unified Stack Architecture