conductor-creator

To set up deterministic task routing, scan existing skills, agents, and workflows to generate a project-specific routing brain. This produces codified routing rules and integration artifacts that ensure consistent task mapping across your evolving project ecosystem.

Task routing drift occurs when mapping decisions between tasks, skills, and agents are not codified. Applying a deterministic routing engine generates persistent rule files that enforce consistent task mapping across sessions and prevents inconsistency during project setup.

You need a deterministic routing brain when your project requires consistent task routing across sessions and an evolving ecosystem. It maps tasks to workflows, skills, and agents to avoid drift and maintain alignment across all operational surfaces.

Run the routing brain generator after your agent and workflow definitions exist. It inspects these definitions to map tasks to workflows and skills, producing project-level outputs like conductor-rules.json and conductor.py that feed the routing engine.

Yes, the generated routing rules integrate with other creators like agent-creator and workflow-creator. This integration maintains alignment across surfaces, ensuring that task routing decisions remain synchronized with evolving agent and workflow definitions.

Deterministic routing requires existing agent and workflow definitions before generating rules. If your project ecosystem evolves without updating these definitions, the generated routing artifacts may not reflect current task mappings, leading to potential routing misalignment.