T-Z56F-orchestrate-routing-table
Status: closed/superseded · Impact: medium · Complexity: medium
Dispatch treats every task identically regardless of size or autonomy;
DarkFactory proved that two small enums on the work item can drive an
automatic model/timeout policy. Add a config-plane routing table keyed off the
existing complexity / autonomy axes
(D-3PDM-cross-project-data-model-adoption P8).
Proposed
Section titled “Proposed”sdlc.yaml gains a routing table mapping complexity (and optionally
autonomy) to model, effort level, and timeout budget;
orchestrate / task-work dispatch reads it when launching implementations.
Absent config means behavior unchanged. Axes stay in data, mapping stays in
config (P-0008 harness-agnosticism).
Acceptance criteria
Section titled “Acceptance criteria”- AC-1: the sdlc.yaml schema accepts a routing table; invalid entries fail config validation.
- AC-2: orchestrate / task-work dispatch applies the routed model, effort, and timeout when the table is present.
- AC-3: with no routing table configured, behavior is unchanged.
- AC-4: doctor/config output surfaces the resolved routing.
Out of scope
Section titled “Out of scope”- A separate difficulty axis on task — only if routing off
complexityproves miscalibrated (D-3PDM-cross-project-data-model-adoptionopen question). - Per-run manual overrides beyond existing CLI flags.
Dependencies
Section titled “Dependencies”- none
Discovery context
Section titled “Discovery context”D-3PDM-cross-project-data-model-adoptionP8: DarkFactory’scapability → modelmap (haiku…opus) andeffort × capability → timeoutbudgets were used corpus-wide and config-overridable.