II.
Page JSON
Structured · livepage:docs-harness-features-backlog-gaps-agent-delegation-gap-agent-008
GAP-AGENT-008: Harness Selection Policies json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "page:docs-harness-features-backlog-gaps-agent-delegation-gap-agent-008",
"_kind": "Page",
"_file": "wiki/docs/harness-features-backlog/gaps/agent-delegation/gap-agent-008.md",
"_cluster": "wiki",
"attributes": {
"nodeKind": "Page",
"sourcePath": "docs/harness-features-backlog/gaps/agent-delegation/GAP-AGENT-008.md",
"sourceKind": "repo-docs",
"title": "GAP-AGENT-008: Harness Selection Policies",
"displayName": "GAP-AGENT-008: Harness Selection Policies",
"slug": "docs/harness-features-backlog/gaps/agent-delegation/gap-agent-008",
"articlePath": "wiki/docs/harness-features-backlog/gaps/agent-delegation/GAP-AGENT-008.md",
"article": "\n# GAP-AGENT-008: Harness Selection Policies\n\n| Field | Value |\n|-------|-------|\n| Category | agent-delegation |\n| Priority | High |\n| Effort | M |\n| Status | Missing |\n\n## Description\nDefine policies for selecting which harness handles a given task based on capability requirements, cost constraints, and quality targets. Reframed from CC named capability profiles to babysitter harness selection policies.\n\n## Current State\nTasks routed to single harness specified at run creation. Task execution hints (execution.harness, execution.model) exist but are not used for routing decisions.\n\n## Target State\nHarness selection policies that consider: task kind and capability requirements, model preference, cost constraints, harness availability and health. At least 4 profiles: full, read-only, plan-only, verify-only.\n\n## Dependencies\n- [GAP-HADAPT-001](../harness-adaptation/GAP-HADAPT-001.md) -- capability-based routing foundation\n\n## Key Files\n| Component | Path |\n|-----------|------|\n| Task definitions | `packages/sdk/src/tasks/` |\n| Task registry | `packages/sdk/src/tasks/registry.ts` |\n| Harness adapters | `packages/sdk/src/harness/` |\n\n## Recommendation\nPhase 2 implementation. Define harness selection policies in task registry. Match task requirements to harness capabilities. Select optimal harness per task.\n",
"documents": []
},
"outgoingEdges": [],
"incomingEdges": [
{
"from": "page:docs-harness-features-backlog",
"to": "page:docs-harness-features-backlog-gaps-agent-delegation-gap-agent-008",
"kind": "contains_page"
}
]
}