orchestrate

Workflow orchestration routes repository tasks through installed capabilities while preserving dispatch-spec, task-session, and observability boundaries for traceable artifact generation across sigils and spells.

Multi-capability coordination applies governance to complex repository workflows by guiding classification, execution, validation, and handoff stages to ensure safe collaboration and modular extension.

Task routing processes repository work from initiation through validated artifact by applying a defined frontmatter, objective section, and process block that govern classification and execution.

Yes, workflow orchestration requires a defined frontmatter including name, description, runtime, and surface_kind, plus an objective section and process block to guide execution accurately.

Yes, workflow orchestration supports complex repository workflows requiring governance, multi-capability coordination, and traceable artifacts across sigils and spells for end-to-end observability.

Workflow orchestration should be avoided for simple repository tasks that do not require multi-capability coordination, governance boundaries, or traceable artifacts across sigils and spells.