using-agents-stack

Orchestrator routing dispatches a fresh worker to the correct harness phase by using the strongest, most relevant durable artifact as authority. This ensures decisions are governed by durable evidence and prevents chat-memory drift.

Artifact precedence defines the authority hierarchy for durable evidence when routing work. You need it during orchestrator dispatch to validate routing decisions and prevent chat-memory drift across pending backlog and sprint states.

Prevent chat-memory drift by dispatching a fresh worker context for each route and using durable artifacts as authority. The router validates decisions against the durability rules defined in the repository references.

Yes, the dispatcher handles both pending backlog routing and parked or running sprints. It honors dormant state correctness by referencing docs/live and repository references to ensure parked and runnable states are handled correctly.

Yes, orchestrator routing requires the durability rules and artifact precedence defined in the repository references. These references validate routing decisions and ensure the dispatcher uses the correct durable artifact as authority.

The best way to declare no family fit is through orchestrator routing, which evaluates artifact precedence to route to exactly one child skill or declares no fit. This ensures durable evidence governs the decision and prevents chat-memory drift.