II.
Page JSON
Structured · livepage:docs-harness-features-backlog-gaps-effect-routing-gap-route-001
GAP-ROUTE-001: Smart Effect Routing Engine json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "page:docs-harness-features-backlog-gaps-effect-routing-gap-route-001",
"_kind": "Page",
"_file": "wiki/docs/harness-features-backlog/gaps/effect-routing/gap-route-001.md",
"_cluster": "wiki",
"attributes": {
"nodeKind": "Page",
"sourcePath": "docs/harness-features-backlog/gaps/effect-routing/GAP-ROUTE-001.md",
"sourceKind": "repo-docs",
"title": "GAP-ROUTE-001: Smart Effect Routing Engine",
"displayName": "GAP-ROUTE-001: Smart Effect Routing Engine",
"slug": "docs/harness-features-backlog/gaps/effect-routing/gap-route-001",
"articlePath": "wiki/docs/harness-features-backlog/gaps/effect-routing/GAP-ROUTE-001.md",
"article": "\n# GAP-ROUTE-001: Smart Effect Routing Engine\n\n| Field | Value |\n|-------|-------|\n| Category | effect-routing |\n| Priority | High |\n| Effort | XL |\n| Status | Missing |\n\n## Description\nCentralized routing engine that considers task kind, capabilities needed, model preference, cost, and harness health to select optimal execution target.\n\n## Current State\nAll effects routed to single configured harness. No routing logic.\n\n## Target State\nRouting engine evaluates: task required capabilities, model preference, cost constraints, harness availability and health, historical performance. Selects optimal harness/model combination per effect.\n\n## Dependencies\n- [GAP-HADAPT-001](../harness-adaptation/GAP-HADAPT-001.md) -- capability declarations\n- [GAP-HADAPT-003](../harness-adaptation/GAP-HADAPT-003.md) -- cost-based routing (optional enhancement, M6)\n- [GAP-HADAPT-005](../harness-adaptation/GAP-HADAPT-005.md) -- health monitoring (optional enhancement, M6)\n\n## Key Files\n| Component | Path |\n|-----------|------|\n| Harness adapters | `packages/sdk/src/harness/` |\n| Task definitions | `packages/sdk/src/tasks/` |\n| Adapter registry | `packages/sdk/src/harness/registry.ts` |\n\n## Recommendation\nPhase 3 implementation. Build routing engine as central coordinator. Integrate capability matching, cost optimization, and health awareness.\n",
"documents": []
},
"outgoingEdges": [],
"incomingEdges": [
{
"from": "page:docs-harness-features-backlog",
"to": "page:docs-harness-features-backlog-gaps-effect-routing-gap-route-001",
"kind": "contains_page"
}
]
}