Workflow Docs
Turn repeated work into a process you can review.
Workflow Docs explain how to structure repeated model work with clear inputs, named steps, model choices, review points, approvals, outputs, and history. The goal is a process people can understand before and after it runs.
Give repeated work a clear shape.
Start with the job, define what goes in and what should come out, then break the work into stages. Add model choices where needed, simulation or dry-run concepts where supported, and approval points before sensitive or state-changing actions.
- Define clear inputs and outputs.
- Break the process into named steps that people can understand.
- Choose flagship, open, or local lanes by step where supported.
- Add review and approval before consequential movement.
- Keep outputs, decisions, and useful evidence connected to workflow history.
Core workflow concepts
These are the building blocks for designing repeatable work without assuming every process should run unattended.
Inputs and named steps
List the files, prompts, connected context, user decisions, stages, and expected outputs that give the workflow its structure.
Model choices
Use flagship, open, or local lanes by step based on reasoning need, volume, sensitivity, and supported configuration.
Simulation and dry runs
Use simulation or dry-run concepts where supported to inspect the workflow before sensitive movement or execution-oriented steps.
Approval points
Place human review before state-changing actions, connected-system actions, or sensitive context movement.
Outputs and history
Keep outputs, evidence, route choices, approval decisions, and review notes connected to workflow history where available.
How to design a workflow
- 01
Define the recurring task
Name the repeated job in plain language and decide whether it deserves a structured workflow.
- 02
Name the inputs and outputs
List the context, files, prompts, decisions, and expected results the workflow needs.
- 03
Break the work into steps
Separate research, drafting, verification, review, approval, and execution-oriented movement.
- 04
Add review gates
Place approvals before sensitive, external, or state-changing steps.
- 05
Keep the record
Attach outputs, evidence, approval decisions, and useful history so the process can be reviewed and improved.
- 06
Scope
Workflow Docs cover workflow design, review points, model choices, approvals, evidence, and history. These concepts connect to Ethen Workflow, Cortex, Approvals, and Evidence. Actual runtime behavior depends on the product surface and supported configuration.
FAQ
- What are Workflow Docs for?
- They help builders design repeatable model workflows with named steps, approvals, evidence, and visible boundaries. They are the docs for turning repeated model work into readable processes with steps, approvals, and evidence.
- Do workflows run fully on their own?
- Workflow docs focus on reviewable workflow support. Sensitive or state-changing steps should move through visible approval paths. Because many teams need stronger process structure before they need more automation.
- What should a workflow include?
- A good workflow includes inputs, steps, model lanes, review points, approval gates, expected outputs, and evidence records. Inputs, stages, lane choice, approvals, evidence, and the boundaries around execution.
- How do workflows use multiple models?
- Different steps can use flagship, open, or local lanes depending on task needs and supported configuration. No. The page explicitly avoids promising unattended autonomy.
- How do Workflow Docs connect to Cortex?
- Cortex covers planner, worker, verifier, and receipt patterns for more complex workflow coordination. Because workflow quality depends on what users can inspect before and after a run.
- Can workflows use local models?
- Yes, where local lanes and runtime configuration support the workflow step. It helps teams build repeatable systems they can still understand later.
Design the workflow before it moves.
Use Workflow Docs to structure repeated model work with clear stages, review points, approvals, and a useful record of what happened.