-
Notifications
You must be signed in to change notification settings - Fork 4
Add dispatch rules how-to guide to docs site #469
Copy link
Copy link
Open
Labels
area:configWORKFLOW.md parsing, typed config, env resolution, validationWORKFLOW.md parsing, typed config, env resolution, validationarea:docs-sitedocs.sortie-ai.com content and infrastructuredocs.sortie-ai.com content and infrastructurearea:orchestratorDispatch, retry, reconciliation, state machine, poll loopDispatch, retry, reconciliation, state machine, poll loop
Metadata
Metadata
Assignees
Labels
area:configWORKFLOW.md parsing, typed config, env resolution, validationWORKFLOW.md parsing, typed config, env resolution, validationarea:docs-sitedocs.sortie-ai.com content and infrastructuredocs.sortie-ai.com content and infrastructurearea:orchestratorDispatch, retry, reconciliation, state machine, poll loopDispatch, retry, reconciliation, state machine, poll loop
Type
Projects
Status
Todo
Sortie gains rule-based dispatch in this milestone (#435): operators can map issue metadata (labels, issue type, priority) to a specific agent adapter and workflow template. The user-facing docs site needs a how-to page that walks a reader through configuring these rules from zero.
Scope of the new page: a concrete end-to-end example (e.g., route
buglabels to one agent/template anddocslabels to another), the full config field reference for the chosen rule format (follows the ADR from #434), matching semantics (first-match-wins vs weighted priority, glob vs exact), fallback behavior when no rule matches, and a troubleshooting section covering common misconfigurations. Cross-link to the architecture reference page (#437) and to the existing WORKFLOW.md documentation.Depends on #434 (format ADR) and tracks #435 (implementation).
Verify: a new page under
how-to/ondocs.sortie-ai.comcovers the scenario above, builds cleanly, and is linked from the how-to index and the WORKFLOW.md reference page.