Skip to content

Route dispatch to agent and template based on issue metadata #435

@sergeyklay

Description

@sergeyklay

Sortie dispatches all issues using a single agent and a single workflow template regardless of issue characteristics. When multiple agent adapters and workflow templates are available, the orchestrator should select the appropriate agent and template based on issue metadata such as labels, issue type, or priority.

The orchestrator is the only component with simultaneous visibility into tracker metadata, available agent adapters, and workflow templates. This makes dispatch routing a core orchestrator responsibility that cannot be delegated to agents or trackers.

The expected behavior: a user defines a set of rules that map issue attributes to a specific agent adapter and workflow template. When Sortie picks up an issue, it evaluates the rules and dispatches accordingly. If no rule matches, a default agent and template are used as fallback.

Depends on #434 (dispatch rule format research and ADR).

Verify: Sortie dispatches an issue with label bug using a different agent and/or workflow template than an issue with label docs, based on user-defined dispatch rules. Default fallback works when no rule matches.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:configWORKFLOW.md parsing, typed config, env resolution, validationarea:orchestratorDispatch, retry, reconciliation, state machine, poll loop

    Projects

    Status

    Todo

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions