{
  "id": "page:docs-harness-features-backlog-gaps-harness-adaptation-gap-hadapt-001",
  "_kind": "Page",
  "_file": "wiki/docs/harness-features-backlog/gaps/harness-adaptation/gap-hadapt-001.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/harness-features-backlog/gaps/harness-adaptation/GAP-HADAPT-001.md",
    "sourceKind": "repo-docs",
    "title": "GAP-HADAPT-001: Capability-Based Task Routing",
    "displayName": "GAP-HADAPT-001: Capability-Based Task Routing",
    "slug": "docs/harness-features-backlog/gaps/harness-adaptation/gap-hadapt-001",
    "articlePath": "wiki/docs/harness-features-backlog/gaps/harness-adaptation/GAP-HADAPT-001.md",
    "article": "\n# GAP-HADAPT-001: Capability-Based Task Routing\n\n| Field | Value |\n|-------|-------|\n| Category | harness-adaptation |\n| Priority | Critical |\n| Effort | L |\n| Status | Partial |\n\n## Description\nRoute tasks to harnesses based on declared capabilities (code generation, web search, file editing, etc.). Match task requirements to harness strengths.\n\n## Current State\nHarnesses declare capabilities via `HarnessCapability` enum (Programmatic, SessionBinding, StopHook, Mcp, HeadlessPrompt) and `getCapabilities()` on all adapters. Discovery reports capabilities per harness. However, task definitions do not declare required capabilities, and there is no routing engine that matches task requirements to harness capabilities. Tasks are routed to a single harness specified at run creation.\n\n## Target State\nHarnesses declare capabilities. Tasks declare required capabilities. Routing engine matches task requirements to available harnesses. Fallback to default harness when no match found.\n\n## Dependencies\n- None (foundation gap for harness adaptation)\n\n## Key Files\n| Component | Path |\n|-----------|------|\n| Harness adapters | `packages/sdk/src/harness/` |\n| Harness discovery | `packages/sdk/src/harness/discovery.ts` |\n| Task definitions | `packages/sdk/src/tasks/` |\n\n## Recommendation\nPhase 1 implementation. Define HarnessCapability declarations per adapter. Add required capabilities to task definitions. Implement matching in routing engine.\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:docs-harness-features-backlog",
      "to": "page:docs-harness-features-backlog-gaps-harness-adaptation-gap-hadapt-001",
      "kind": "contains_page"
    }
  ]
}