{
  "id": "page:docs-genty-features-backlog-updated-phase4-critical-path",
  "_kind": "Page",
  "_file": "wiki/docs/genty-features-backlog-updated/phase4-critical-path.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/genty-features-backlog-updated/phase4-critical-path.md",
    "sourceKind": "repo-docs",
    "title": "Phase 4: Critical Path Analysis",
    "displayName": "Phase 4: Critical Path Analysis",
    "slug": "docs/genty-features-backlog-updated/phase4-critical-path",
    "articlePath": "wiki/docs/genty-features-backlog-updated/phase4-critical-path.md",
    "article": "\n# Phase 4: Critical Path Analysis\n\n## Critical Path (Longest Chain of Unsatisfied Dependencies)\n\nThe critical path is 6 nodes deep, running through the parallelization and agent-delegation domains. This is the chain that, if any node is delayed, delays the maximum number of downstream gaps.\n\n```\nGAP-SUBOBS-001 (Critical, IN_PROGRESS, M)\n  Streaming Output Capture from Invoked Harnesses\n    |\n    v\nGAP-SUBOBS-002 (High, IN_PROGRESS, M)\n  Subagent Progress Tracking\n    |\n    v\nGAP-PAR-003 (High, IN_PROGRESS, L)              [also needs GAP-PAR-001]\n  Multi-Harness Parallel Dispatch\n    |\n    v\nGAP-AGENT-003 (High, IN_PROGRESS, L)            [also needs GAP-AGENT-001]\n  Process Orchestration with Effect Routing\n    |\n    v\nGAP-AGENT-004 (Medium, IN_PROGRESS, M)          [also needs GAP-PROC-001]\n  Built-in Process Templates\n    |\n    v\nGAP-SESSION-003 (Medium, OPEN, M)\n  Session Templates and Presets\n```\n\n### Why this is the critical path\n\n**Node 1 -- GAP-SUBOBS-001: Streaming Output Capture** (Critical priority, M effort)\n- The foundation of all subagent observability. Without streaming output from harness processes, progress tracking, health monitoring, and the entire dashboard drill-down chain are blocked.\n- Currently IN_PROGRESS: Pi adapter streams via subscribe(), but CLI harnesses capture output only after process exit.\n- Remaining work: Pipe stdout/stderr from child processes in real-time across all harness types.\n- Unblocks: GAP-SUBOBS-002, GAP-SUBOBS-004, GAP-SUBOBS-005, GAP-PERF-004, GAP-UX-001f\n\n**Node 2 -- GAP-SUBOBS-002: Subagent Progress Tracking** (High priority, M effort)\n- Extracts progress signals (percentage, step, ETA) from streaming output. Required by the coordinator pattern to know worker status.\n- Currently IN_PROGRESS: BackgroundEffectStatus tracks lifecycle but not granular progress.\n- Remaining work: Progress percentage extraction, ETA estimation, progress bar support.\n- Unblocks: GAP-PAR-003, GAP-SUBOBS-005, GAP-UX-001e (via implicit dependency)\n\n**Node 3 -- GAP-PAR-003: Multi-Harness Parallel Dispatch** (High priority, L effort)\n- Named effect groups with persistent identity across iterations. Multiple harnesses working concurrently on related tasks.\n- Currently IN_PROGRESS: Execution waves and named groups exist, but cross-iteration team coordination is absent.\n- Remaining work: Coordinator process pattern, team management across iterations, inter-effect communication during execution.\n- Unblocks: GAP-PAR-010, GAP-AGENT-003\n\n**Node 4 -- GAP-AGENT-003: Process Orchestration with Effect Routing** (High priority, L effort)\n- The coordinator process template: dynamically routes work to different harnesses, aggregates progress from workers.\n- Currently IN_PROGRESS: capabilityRouter.ts exists but is not consumed in orchestrateIteration.\n- Remaining work: Wire capability routing into orchestration loop, build coordinator process template.\n- Unblocks: GAP-AGENT-004\n\n**Node 5 -- GAP-AGENT-004: Built-in Process Templates** (Medium priority, M effort)\n- Pre-configured templates (explorer, planner, verifier, reviewer) with harness/model/capability profiles.\n- Currently IN_PROGRESS: Methodology definitions are rich but not packaged as ready-to-use templates.\n- Remaining work: Package methodologies with specific harness+capability configurations.\n- Unblocks: GAP-SESSION-003\n\n**Node 6 -- GAP-SESSION-003: Session Templates and Presets** (Medium priority, M effort)\n- Session templates stored in `.a5c/session-templates/` specifying default harness, model, breakpoints, process bindings, budgets.\n- Currently OPEN: No session template system exists.\n\n### Total effort on critical path: M + M + L + L + M + M = approximately XL-XXL\n\n---\n\n## Alternative Near-Critical Paths\n\n### Path B: Streaming to UI (5 deep)\n\n```\nGAP-SUBOBS-001 -> GAP-PERF-004 -> GAP-PAR-006 (terminal)\nGAP-SUBOBS-001 -> GAP-UX-001f -> (needs GAP-UX-001 respec first)\n```\n\nThis path is blocked on GAP-UX-001 (NEEDS_RESPEC), making it stalled rather than critical.\n\n### Path C: Memory Pipeline (5 deep)\n\n```\nGAP-AGENT-001 -> GAP-AGENT-006 -> GAP-STATE-001 -> GAP-STATE-002 (terminal)\n```\n\nShorter but feeds into important long-term memory capabilities.\n\n### Path D: Run Lifecycle (4 deep)\n\n```\nGAP-PROC-003 -> GAP-STATE-006 -> GAP-RUN-003 (terminal)\n```\n\nBlocked by process versioning which has no upstream dependencies -- can start immediately.\n\n---\n\n## Foundation Gaps (Most Downstream Dependents)\n\nThese gaps unblock the most downstream work and should be prioritized:\n\n| Gap | Status | Priority | Direct Dependents | Total Downstream |\n|-----|--------|----------|-------------------|------------------|\n| GAP-SUBOBS-001 | IN_PROGRESS | Critical | 7 | 22 |\n| GAP-PAR-001 | IN_PROGRESS | High | 6 | 16 |\n| GAP-ECO-002 | OPEN | High | 5 | 12 |\n| GAP-REMOTE-007 | IN_PROGRESS | High | 3 | 5 |\n| GAP-UX-001 | NEEDS_RESPEC | High | 5 | 9 |\n| GAP-AGENT-001 | IN_PROGRESS | High | 5 | 15 |\n| GAP-SUBOBS-002 | IN_PROGRESS | High | 3 | 10 |\n| GAP-PROC-001 | IN_PROGRESS | High | 4 | 8 |\n\n### What \"Total Downstream\" means\nDirect dependents are gaps that directly list this gap as a dependency. Total downstream is the transitive closure -- all gaps that are blocked (directly or indirectly) when this gap is incomplete.\n\n### Key insight\n**GAP-SUBOBS-001** (Streaming Output Capture) is the single most impactful foundation gap, with 22 total downstream dependents spanning subagent-observability, parallelization, performance, and user-experience domains. It should be the top priority for unblocking maximum downstream work.\n\n**GAP-ECO-002** (CC Marketplace Protocol Support) is the highest-impact OPEN gap (not yet started), unblocking the entire ecosystem track including plugin trust, auto-update, validation, analytics, and plugin management integration.\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:docs-genty-features-backlog-updated",
      "to": "page:docs-genty-features-backlog-updated-phase4-critical-path",
      "kind": "contains_page"
    }
  ]
}