Sortie currently dispatches all issues using a single agent and a single workflow template. To support issue-aware routing (selecting agent + template based on issue metadata), the orchestrator needs a dispatch rule format. Several design questions must be resolved before implementation.
Options to evaluate:
- Rules as a dedicated section in WORKFLOW.md YAML front matter. Keeps all dispatch config in one file, but may overload the workflow file's purpose.
- Rules in a separate config file (e.g.,
dispatch.yaml or a rules section in a top-level Sortie config). Cleaner separation of concerns, but introduces a new file for users to manage.
- Rules as CLI flags or environment variables. Simplest for single-rule setups, but does not scale to complex routing.
Each option must address: matching syntax (label, issue type, priority, glob patterns, regex, exact match), first-match-wins vs weighted priority semantics, per-rule agent and template override, fallback behavior when no rule matches, and interaction with existing WORKFLOW.md front matter fields (ADR-0004, ADR-0005).
Priority: medium. This unblocks intelligent multi-agent dispatch but is not a launch blocker.
Verify: ADR documenting the chosen format, matching semantics, and fallback behavior, with at least two concrete configuration examples.
Sortie currently dispatches all issues using a single agent and a single workflow template. To support issue-aware routing (selecting agent + template based on issue metadata), the orchestrator needs a dispatch rule format. Several design questions must be resolved before implementation.
Options to evaluate:
dispatch.yamlor arulessection in a top-level Sortie config). Cleaner separation of concerns, but introduces a new file for users to manage.Each option must address: matching syntax (label, issue type, priority, glob patterns, regex, exact match), first-match-wins vs weighted priority semantics, per-rule agent and template override, fallback behavior when no rule matches, and interaction with existing WORKFLOW.md front matter fields (ADR-0004, ADR-0005).
Priority: medium. This unblocks intelligent multi-agent dispatch but is not a launch blocker.
Verify: ADR documenting the chosen format, matching semantics, and fallback behavior, with at least two concrete configuration examples.