Tasks

A task is a process written as a sentence. You describe what should happen, Workbench turns it into a plan, and each run follows that plan: flows do the work, zv1 writes what needs writing, and people take the decisions that are theirs to take.

Open Tasks in the top navigation and choose Create a task with zv1. You write the task by describing it to zv1, which is also how you change it later.

Writing the sentence

Type the process the way you would explain it to a colleague: "When a support ticket comes in, summarize it, have Priya decide whether it's a bug, and if it is, file it and tell the team." Press Compile and Workbench proposes a plan.

The plan comes back as the same sentence, annotated. Each clause carries a small mark for what kind of step it is:

• Workbench flow runs one of your flows and hands its output to the next step.
• zv1 writes asks zv1 to produce something from what the run has so far. A step can be given tools, and you choose who approves what it does: whoever started the run, the task's author, or nobody, if you pre-authorize it when you save.
• A person decides stops the run until a named teammate picks one of the options you wrote. If it sits too long the run escalates.
• Handed to people and notification deliver what the run produced to teammates, with or without waiting.
• Branch, for each, retry until, and wait shape the flow of the run.
• Runs another task starts a second task, either waiting for it or moving on.
• Ledger record writes the outcome into Ledger as a decision with evidence attached.

Click any clause to see how it is configured. If something didn't bind the way you meant, edit the sentence and compile again. Nothing is saved until you press Save v1 & activate.

Versions

Saving the plan gives it a numbered version. Runs pin the version they started on, so editing the sentence later never changes a run that is already underway.

The most-edited parts of a step can be changed without recompiling: open the clause and choose Edit step to change a zv1 instruction, a gate's prompt or escalation time, a wait's duration, a pinned flow version, or a message. Saving cuts the next version.

Starting runs

A task starts by hand from its page, on a schedule you set on the trigger, or from your own code. A task that takes a starting document asks for it when you start a run.

Each run is a receipt: what ran, in what order, what it cost, who decided what, and where it is waiting now. A run that is waiting on a person shows up for that person in their inbox and on the task page.

Sharing the work with zv1

Ask zv1 to run a task with you, or to talk through a process that could become one. zv1 can start runs, take gates that are assigned to it, and report where a run stands.