Methodology guide
Designing domain workflows
Turn a business process into a reviewable task by preserving its documents, decisions, revisions, and handoffs.
When to use it
Start with a clear purpose.
Use this approach when success depends on several connected actions rather than a single answer. A finance close, contract review, or engineering change can become a bounded scenario with a clear starting state and completion condition.
Step 01
Map the decisions
Identify where new information changes the work. Connect each decision to its evidence, tool action, and responsible reviewer; include correction and approval loops.
Step 02
Build a bounded workspace
Package a fixed starting state and explicit task instructions. Keep dependencies between files visible, and distinguish actions the agent may take from decisions requiring review.
Step 03
Pilot the complete path
Run the scenario from input to final artifact. Inspect intermediate versions and failed attempts, then revise missing context or ambiguous completion rules.
Acceptance
Make the result reviewable.
Accept the package when another reviewer can follow the evidence, reproduce required checks, and explain each material revision. Separate an illustrative workflow from claims about production results.