hf-workflow-router

Workflow routing uses a finite state machine to evaluate disk-stored artifact evidence, current profiles, and escalation signals to determine runtime routing choices and output the target skill. It drives transitions based on approved specs, progress, reviews, and completion artifacts rather than chat memory.

Evidence-driven decision making for workflow recovery evaluates the latest disk-stored artifacts, such as reviews and verification gates, to seamlessly route the workflow. It determines runtime routing choices including current stage, workflow profile, execution mode, and workspace isolation to restore operations.

To determine execution mode and workspace isolation, the routing skill evaluates the latest artifact evidence and current profile. It outputs the target skill alongside runtime routing choices, including current stage, workflow profile, execution mode, and workspace isolation.

Yes, you can upgrade workflow profiles and dispatch reviewers automatically using an escalation pattern. The routing skill progressively upgrades profiles and dispatches reviewers as needed, relying on the latest artifact evidence and escalation signals to drive the transition.

You should not use chat memory for workflow routing when you need reliable recovery and escalation. The routing skill relies on disk-stored artifact state, such as approved specs, progress, and verification, rather than chat memory to drive transitions and determine the target skill.