{
  "id": "page:docs-v6-spec-and-roadmap-implementation-foundation-layer",
  "_kind": "Page",
  "_file": "wiki/docs/v6-spec-and-roadmap/implementation/foundation-layer.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/v6-spec-and-roadmap/implementation/foundation-layer.md",
    "sourceKind": "repo-docs",
    "title": "Foundation Layer Implementation",
    "displayName": "Foundation Layer Implementation",
    "slug": "docs/v6-spec-and-roadmap/implementation/foundation-layer",
    "articlePath": "wiki/docs/v6-spec-and-roadmap/implementation/foundation-layer.md",
    "article": "\n# Foundation Layer Implementation\n\n→ [Implementation Index](../README.md#implementation) | Next: [Platform Layer](platform-layer.md)\n\n## Phase 1: Foundation Layer\n\nThe foundation layer establishes the minimum V6 base inside the current repository shape. This phase clarifies seams, validation gates, and ownership in `packages/sdk`, `packages/babysitter-agent`, and `plugins/*`. It does not commit V6 to creating deferred top-level packages.\n\n### Current-Package Seam Clarification\n\n**Runtime And Session Boundaries**\n- Clarify which runtime concerns already belong to `packages/babysitter-agent`\n- Isolate Pi wrapper, session handling, and structured event concerns behind internal module seams before considering any package move\n- Reduce filesystem assumptions only where current commands and tests prove the change is safe\n- Record candidate extraction boundaries as ADR-backed slices rather than package commitments\n\n**Hook System**\n- Tighten programmatic hook responsibilities in the current SDK and plugin surfaces\n- Verify hook registration, invocation, and acknowledgment flows against existing runtime behavior\n- Add or update configuration only where the current CLI and plugin model already require it\n\n### Infrastructure Foundation\n\n**Compiler And Packaging Reality Checks**\n- Validate `agent-plugins-mux` and related packaging flows against real plugin manifests and generated outputs\n- Document import and ownership seams that already exist in the repo instead of inventing new package boundaries\n- Add compatibility notes for any rename or extraction candidate that survives Phase 0 decision framing\n\n**Platform Candidate Preparation**\n- Describe plugin-system responsibilities in current-package terms\n- Identify which platform concerns are internal `packages/sdk` or `packages/babysitter-agent` candidates versus actual `plugins/*` responsibilities\n- Treat filesystem abstraction and plugin registration work as candidate slices only when they can be validated independently\n\n## Deliverables\n\n- Updated seam map for runtime, session, and hook responsibilities in current packages\n- ADR-backed first executable slice for the accepted `@a5c-ai/babysitter-agent` seam contract\n- ADR-ready candidate slices for any later extraction or rename still worth considering\n- Hook and packaging flows validated against existing commands and plugin outputs\n- Any reduced-filesystem claim stated with a baseline, command, and rollback note\n\n## Technical Validation\n\n**Documentation Consistency**: Foundation work must remain consistent with [V6 Architecture Specification](../v6-architecture-specification.md) and [Package Specifications](../package-specs.md)\n\n**Current-Behavior Checks**: Use current build, test, and plugin packaging commands as the source of truth for whether a seam is real\n\n**Current Slice Command**: `npm run verify:v6:seams` is the repo-level validation gate for the accepted seam-contract slice\n\n**Packaging Validation**: Compare compiler changes against existing manifest and install surfaces\n\n**Performance Benchmarking**: Any runtime or session target must cite a baseline command before it becomes a success criterion\n\n**Extraction Gate**: No deferred package name becomes part of this phase without a decision record that changes its state in the core V6 docs\n\n## Explicit Non-Deliverables\n\nThis phase does not create `@a5c-ai/agent-runtime` or `@a5c-ai/agent-platform`. Those names remain deferred vocabulary unless later decision records promote a specific slice into scope.\n\n---\n\n**Related Documents**: [Package Specifications](../package-specs.md) | [Testing Framework](../testing-framework.md) | [Platform Layer](platform-layer.md)\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:docs-v6-spec-and-roadmap-implementation",
      "to": "page:docs-v6-spec-and-roadmap-implementation-foundation-layer",
      "kind": "contains_page"
    }
  ]
}