follow-up-orchestrator

To decide if a multi-step workflow turn is complete or requires a follow-up, evaluate the ongoing turn against runtime data to return a structured verdict like done, needs_followup, or needs_replan. This prevents silent abandonment of meaningful work.

End-of-turn evaluation in durable workflow orchestration is the process of assessing an active turn to produce a stable outcome contract, ensuring durable runtime state, tickets, and plans are updated to enable explicit handoffs and traceability across turns.

Generate structured follow-up tickets when a task is blocked on external dependencies by returning a blocked_on_external verdict and proposing durable follow-up data for persistence. This ensures traceability and explicit handoffs for the blocked workflow state.

Use an explicit needs_replan verdict instead of marking workflow planning as done when the current plan is no longer viable and requires replanning. This enforces a stable output contract and preserves durable knowledge in the runtime store.

You can persist durable state and knowledge across multiple turns during ticketing orchestration by integrating the evaluation with the runtime store, tickets, plans, and verification data. This keeps knowledge current and enables explicit handoffs.