{
  "id": "page:docs-v6-spec-and-roadmap-stack-guide",
  "_kind": "Page",
  "_file": "wiki/docs/v6-spec-and-roadmap/stack-guide.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/v6-spec-and-roadmap/stack-guide.md",
    "sourceKind": "repo-docs",
    "title": "Stack Guide",
    "displayName": "Stack Guide",
    "slug": "docs/v6-spec-and-roadmap/stack-guide",
    "articlePath": "wiki/docs/v6-spec-and-roadmap/stack-guide.md",
    "article": "\n# Stack Guide\n\n→ [Documentation Index](README.md) | Related: [Glossary](glossary.md) | [Unified Stack Architecture](unified-stack-architecture.md)\n\n## Purpose\n\nThis 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.\n\n## Start Here\n\nIf you are new to the stack, read these in order:\n\n1. [System Overview](system-overview.md)\n2. [Glossary](glossary.md)\n3. [Unified Stack Architecture](unified-stack-architecture.md)\n4. [V6 Architecture Specification](v6-architecture-specification.md)\n5. [Package Specifications](package-specs.md)\n\nThen branch into the area you are actually changing.\n\nBefore proposing a new seam, run the active validation cue for the first executable V6 slice:\n\n- `npm run verify:v6:seams`\n\n## If You Need To Change Orchestration\n\nRead:\n\n- [V6 Architecture Specification](v6-architecture-specification.md)\n- [Package Specifications](package-specs.md)\n- [Testing Framework](testing-framework.md)\n\nWork mainly in:\n\n- `packages/sdk`\n- `packages/babysitter`\n- `packages/babysitter-agent`\n- `library/`\n- project-local `.a5c/processes/`\n\n## If You Need To Change Harness Dispatch\n\nRead:\n\n- [docs/agent-mux/README](https://github.com/a5c-ai/babysitter/blob/main/docs/agent-mux/README.md)\n- [Agent-Mux Integration](agent-mux-integration.md)\n- [Unified Stack Architecture](unified-stack-architecture.md)\n\nWork mainly in:\n\n- `packages/agent-mux/core`\n- `packages/agent-mux/adapters`\n- `packages/agent-mux/cli`\n- `packages/agent-mux/sdk`\n- `packages/agent-mux/gateway`\n\n## If You Need To Change Hook Behavior\n\nRead:\n\n- `packages/hooks-mux/README.md`\n- `packages/hooks-mux/ARCHITECTURE.md`\n- [Agent-Mux Integration](agent-mux-integration.md)\n\nWork mainly in:\n\n- `packages/hooks-mux/core`\n- `packages/hooks-mux/cli`\n- `packages/hooks-mux/adapter-*`\n- `plugins/babysitter-unified/hooks/`\n\n## If You Need To Change Plugin Packaging\n\nRead:\n\n- `packages/agent-plugins-mux/unified_plugin_system_spec.md`\n- `plugins/babysitter-unified/README.template.md`\n- per-harness plugin README files under `plugins/babysitter-unified/per-harness/`\n\nWork mainly in:\n\n- `packages/agent-plugins-mux`\n- `plugins/babysitter-unified`\n- concrete bundles under `plugins/babysitter-*`\n\n## If You Need To Change Human Approval Or Breakpoint Routing\n\nRead:\n\n- `packages/breakpoints-mux/specs/architecture.md`\n- [Testing Framework](testing-framework.md)\n\nWork mainly in:\n\n- `packages/breakpoints-mux`\n- `packages/sdk` breakpoint integration\n- related hook and plugin surfaces if the transport changes\n\n## If You Need To Change UI Surfaces\n\nRead:\n\n- `packages/agent-mux/README.md`\n- package README files under `packages/agent-mux/*`\n\nWork mainly in:\n\n- `packages/agent-mux/ui`\n- `packages/agent-mux/webui`\n- `packages/agent-mux/tui`\n- `packages/agent-mux/mobile-*`\n- `packages/agent-mux/tv-*`\n- `packages/agent-mux/watch-*`\n- `docs-site/` or `packages/atlas/webui` where relevant\n\n## Source-Of-Truth Map\n\nUse this rule of thumb:\n\n| Concern | Primary source of truth | Supporting references |\n|---|---|---|\n| V6 architecture scope | `docs/v6-spec-and-roadmap/` | package READMEs, adversarial analyses |\n| Orchestration runtime behavior | `packages/sdk`, `packages/babysitter`, `packages/babysitter-agent` | V6 docs, CLI docs |\n| Harness dispatch behavior | `packages/agent-mux/*` and `docs/agent-mux/` | V6 integration docs |\n| Hook normalization | `packages/hooks-mux/*` | per-harness plugin docs |\n| Unified plugin packaging | `packages/agent-plugins-mux`, `plugins/babysitter-unified/` | install READMEs for concrete bundles |\n| Breakpoint routing | `packages/breakpoints-mux` | SDK integration docs |\n\n## Practical Rules\n\n- Start from the package that already owns the behavior before proposing a new layer.\n- If a document describes a future package or layer, check whether V6 marks it as deferred.\n- Treat installable plugin bundles as real compatibility surfaces even when the unified plugin source exists.\n- Use package names and paths when discussing ownership; use architecture terms only when they map to a real current seam.\n- 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.\n\n---\n\n**Related Documents**: [Current State](current-state.md) | [Glossary](glossary.md) | [Unified Stack Architecture](unified-stack-architecture.md)\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:docs-v6-spec-and-roadmap",
      "to": "page:docs-v6-spec-and-roadmap-stack-guide",
      "kind": "contains_page"
    }
  ]
}