{
  "id": "page:docs-v6-spec-and-roadmap-current-state",
  "_kind": "Page",
  "_file": "wiki/docs/v6-spec-and-roadmap/current-state.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/v6-spec-and-roadmap/current-state.md",
    "sourceKind": "repo-docs",
    "title": "Current State Analysis",
    "displayName": "Current State Analysis",
    "slug": "docs/v6-spec-and-roadmap/current-state",
    "articlePath": "wiki/docs/v6-spec-and-roadmap/current-state.md",
    "article": "\n# Current State Analysis\n\n→ [Documentation Index](README.md) | Previous: [System Overview](system-overview.md) | Next: [V6 Architecture Vision](v6-vision.md)\n\n## Existing Architecture\n\nThe current a5c.ai agent stack consists of:\n\n- **`@a5c-ai/adapters`** - Agent dispatch/multiplexing layer\n- **`@a5c-ai/hooks-adapter-cli`** - Hook normalization across harnesses  \n- **`@a5c-ai/extensions-adapter`** - Cross-harness plugin compiler\n- **`@a5c-ai/genty-platform`** - Monolithic orchestration runtime\n- **`@a5c-ai/babysitter-sdk`** - Core SDK for orchestration\n\nThe plugin side of the stack already exposes the pieces needed for metaplugins, but those pieces are not the metaplugin abstraction itself. `extensions-adapter` is the compiler that emits concrete plugin bundles for legacy non-Babysitter agents. The metaplugin layer is the capability being packaged across those bundles, such as memory systems, governance or policy engines, and discipline-enforcement concerns. First-party unified plugin sources such as `plugins/babysitter-unified` can carry parts of those concerns, but they are concrete plugin surfaces rather than the definition of metaplugins.\n\n## Current Pain Points\n\n**Monolithic Complexity**: `agent-platform` contains:\n- Governance system (policies, authorities, sandbox rules) → [Security Architecture](security-architecture.md)\n- Session management (state, context, history, memory)\n- MCP integration (channels, transport, client tools)\n- Harness adapters and agentic tools\n- Cost tracking and observability\n- Daemon infrastructure\n- Agent-core integration for model communication\n\n**Issues**:\n1. **Bundle Size** - Cannot selectively import functionality\n2. **Deployment Complexity** - All-or-nothing deployment model  \n3. **Development Friction** - Large blast radius for changes\n4. **Testing Challenges** - Difficulty isolating components → [Testing Framework](testing-framework.md)\n5. **Domain Boundaries** - Hard to establish clear separation between functional domains\n\n## Naming Harmonization\n\nCurrent confusing terminology will be updated:\n- runtime binary: `agent-platform`\n- `hooks-adapter` → `hooks-adapter`\n- `extensions-adapter` → `extensions-adapter`\n\nThis harmonization provides clearer naming that reflects the actual purpose of each package → [Package Specifications](package-specs.md)\n\n## Impact Assessment\n\nThe monolithic structure creates significant challenges:\n\n**Development Impact**:\n- Changes require building and testing entire monolith\n- Difficult to establish clear module ownership\n- Cross-cutting concerns blur domain boundaries\n\n**Deployment Impact**:\n- Cannot deploy individual capabilities independently\n- All-or-nothing upgrade model increases deployment risk\n- Bundle size impacts application startup time\n\n**Maintenance Impact**:\n- Testing requires full integration environment\n- Bug isolation is complex across domain boundaries\n- Performance optimization requires whole-system analysis\n\n## Executable Seam Clarification Gate\n\nV6 does not treat this monolith as ready for broad extraction yet. The first required slice is an internal seam contract inside `@a5c-ai/genty-platform`, not an immediate package split.\n\nThat seam contract lives at `packages/genty/platform/src/seams/contract.ts` and assigns each current top-level runtime domain to an owned slice:\n\n- `runtime-foundation`: runtime, session, storage, tasks, prompts, compression\n- `governance-control`: governance, breakpoints\n- `integration-bridges`: harness, mcp, api, anycli\n- `operator-surfaces`: cli, daemon, interaction, observability, cost\n\nThe contract is only useful if it stays executable. Changes to `packages/genty/platform/src` should therefore keep the seam manifest, package subpath exports, and seam validation tests aligned before any broader extraction is proposed.\n\nThis slice is formally accepted in [ADR-001: Agent-Platform Seam Contract As The First Executable V6 Slice](decisions/ADR-001-agent-platform-seam-contract.md). The repo-level validation entrypoint for that slice is `npm run verify:v6:seams`.\n\n---\n\n**Related Documents**: [System Overview](system-overview.md) | [V6 Vision](v6-vision.md) | [Package Specifications](package-specs.md)\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:docs-v6-spec-and-roadmap",
      "to": "page:docs-v6-spec-and-roadmap-current-state",
      "kind": "contains_page"
    }
  ]
}