Verdandi Workflow Orchestrator
Verdandi is the workflow orchestrator for Valdr.
Use Verdandi when a workflow needs to be created, needs to run, or has stopped and you need an evidence-backed explanation. It understands workflow definitions and runtime state together, so it can distinguish a definition that validates from one that has actually executed successfully.
Use Verdandi when
| Need | Ask Verdandi to |
|---|---|
| Author a workflow | Turn an outcome into the smallest executable definition and verify its dependencies |
| Test a definition | Validate it, then drive an unsaved definition through a real test run |
| Start or inspect a run | Launch with the right inputs and explain its current step, wait, and evidence |
| Diagnose a stopped run | Read the run record, attempts, child runs, sessions, waits, and events before naming the cause |
| Recover safely | Apply a targeted retry, rerun, or cancellation, or recommend a wait override for a trusted operator without hiding earlier evidence |
Verdandi coordinates workflows; it does not implement the product work inside them. Executors, reviewers, and other workflow agents still perform the work assigned by each step.
First five minutes with Verdandi
A first Verdandi session should feel like working with a workflow operator who checks the runtime before making claims:
| You ask | Verdandi helps by |
|---|---|
| “Build a workflow that reviews task readiness before implementation.” | Checking available tools and agents, authoring the definition, validating it, and separating validation from execution proof |
“Run this workflow for task SHOP-42.” | Confirming the definition, inputs, actor, and launcher requirements before starting the run |
| “Why is this run blocked?” | Inspecting the stopped step and its evidence, attempts, waits, sessions, and child runs |
| “Retry only the failed work.” | Identifying the narrowest applicable recovery action and preserving the existing history |
How to use Verdandi
First, import the official Valdr Workflow pack through Settings > Valdr Packs. Sovereign provides the durable runtime; the separately released pack adds Verdandi and the included workflow definitions.
Open the Orchestrator UI and choose Verdandi, invoke /valdr-orchestrator and name verdandi, or launch an agent session with that handle. Name the workflow or run when one already exists; for authoring, describe the outcome, required inputs, decision points, and any human authority that must remain explicit.
Verdandi can use the full workflow tool surface through Valdr MCP. See the pm_workflow reference for every definition, run, wait, and recovery action.
The rule Verdandi follows
A workflow that validates has not been shown to run.
Validation proves that a definition has the expected shape. A real run proves whether referenced tools, agent handles, launcher presets, child workflows, and output contracts work together. Verdandi reports those as separate claims so you know what has been checked and what remains unproven.
Which orchestrator should I use?
| Need | Start with |
|---|---|
| Understand workspace state, projects, tasks, or sprints | Gunnar |
| Investigate knowledge sources, indexed docs/code, or symbol relationships | Mimir |
| Design agents, capabilities, prompts, or pack structure | Nikol |
| Coordinate sprint execution, staffing, review routing, or session launch | Skadi |
| Author, run, inspect, debug, or repair a durable workflow | Verdandi |
Use Verdandi for the workflow itself. If diagnosis reveals unclear PM scope, missing source evidence, a pack-design problem, or sprint-coordination work, hand that part to Gunnar, Mimir, Nikol, or Skadi.
Strong prompts
Use Verdandi for workflow creation and operation:
- Author the smallest workflow that reviews a task for readiness and blocks with a clear reason when it is not ready.
- Validate this definition, then tell me what still needs a real test run.
- Start
valdr-workflow.idea-to-sprintfor this idea task and show me the operator checkpoints before you launch it. - Inspect this blocked run and trace the first stopped step to its evidence.
- Recommend the narrowest recovery action for this failed run without repeating completed side effects.
Built for evidence-first operation
Verdandi keeps its core safety rules active, then loads the authoring, operation, or debugging guidance needed for the current request. That keeps routine prompts focused while preserving the same rules around validation, execution proof, human authority, and recovery.
Ready to work with an included workflow? Start with From Idea to Verified Sprint or open the Workflow UI to browse definitions and runs.