{
  "id": "page:docs-v6-spec-and-roadmap-implementation-platform-layer",
  "_kind": "Page",
  "_file": "wiki/docs/v6-spec-and-roadmap/implementation/platform-layer.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/v6-spec-and-roadmap/implementation/platform-layer.md",
    "sourceKind": "repo-docs",
    "title": "Platform Layer Implementation",
    "displayName": "Platform Layer Implementation",
    "slug": "docs/v6-spec-and-roadmap/implementation/platform-layer",
    "articlePath": "wiki/docs/v6-spec-and-roadmap/implementation/platform-layer.md",
    "article": "\n# Platform Layer Implementation\n\n→ [Implementation Index](../README.md#implementation) | Previous: [Foundation Layer](foundation-layer.md) | Next: [Application Layer](application-layer.md)\n\n## Phase 2: Platform Layer\n\nThe platform layer builds on the foundation by hardening plugin, session, and extensibility behavior in the current stack. It does not assume that deferred `agent-platform*` package names have already been approved as V6 deliverables.\n\n### Core Platform Implementation\n\n**Plugin Framework**\n- Improve plugin lifecycle behavior through existing SDK, compiler, and `plugins/*` surfaces → [Plugin Ecosystem](../plugin-ecosystem.md)\n- Validate plugin dependency and manifest handling against current install and packaging flows\n- Treat marketplace, governance, and isolation work as measured slices, not abstract platform promises\n- Describe metaplugins as capability composition above concrete plugin and hook bundles, without requiring a new package boundary\n\n**Session Management Evolution**\n- Clarify session ownership across `packages/babysitter-agent`, `packages/sdk`, and plugin integration points\n- Improve persistence, context propagation, and recovery only where the current runtime already exposes those seams\n- Keep session changes rollbackable and testable without introducing broad cross-package churn\n\n### Candidate Slice Areas\n\n**Metaplugin Composition**\n- Document composition rules for higher-order capability bundles on top of current plugin and hook surfaces\n- Validate whether hook-type extension or pipeline processing can remain internal to current packages\n- Promote a standalone package only if a later ADR proves that the seam reduces coupling more than it adds API surface\n\n**Orchestration Integration**\n- Keep Babysitter orchestration integration expressed through current packages and plugin bundles\n- Treat orchestration-plugin vocabulary as exploratory only unless a decision record changes its classification\n- Preserve process-library and SDK integration as present-day implementation surfaces\n\nIf a future standalone package is ever pursued here, it should host proved composition logic rather than replace concrete plugin packaging. The current repository evidence still treats unified plugins and per-harness bundles as the install surfaces, with `agent-plugins-mux` compiling those outputs.\n\n## Deliverables\n\n- Improved plugin/session documentation and implementation slices within current packages\n- Manifest, install, and recovery validation for the plugin and session flows actually shipped today\n- Evidence for or against deeper platform extraction recorded as ADR inputs\n- Tooling and plugin integration still working through the current architecture surfaces\n\n## Technical Validation\n\n**Plugin Compatibility Testing**: Manifest correctness, install flows, and generated bundle behavior → [Testing Framework](../testing-framework.md)\n\n**Session Persistence Validation**: Recovery and consistency verification in the packages that currently own session state\n\n**Dependency Resolution Checks**: Correctness verification only for logic that already exists or is being added as a bounded slice\n\n**Cross-Platform Compatibility**: Windows, macOS, Linux validation for current commands and plugins\n\n**Deferred Vocabulary Guardrail**: `@a5c-ai/agent-platform`, `@a5c-ai/agent-platform-meta-plugins`, and `@a5c-ai/agent-platform-orchestration-plugin` remain non-deliverables in this phase\n\n## Explicit Non-Deliverables\n\nThis phase does not create new `agent-platform*` top-level packages. It only earns the right to propose them later by proving real seams in current-package work.\n\n---\n\n**Related Documents**: [Foundation Layer](foundation-layer.md) | [Plugin Ecosystem](../plugin-ecosystem.md) | [Security Architecture](../security-architecture.md)\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:docs-v6-spec-and-roadmap-implementation",
      "to": "page:docs-v6-spec-and-roadmap-implementation-platform-layer",
      "kind": "contains_page"
    }
  ]
}