LESSON03.255 minutes
Automate a repeated workflow
Separate rules from judgment
Keep deterministic steps deterministic and reserve model use for bounded ambiguity.
Use ordinary software for stable rules, calculations, validation, and routing. Consider AI only where inputs vary and the result can be reviewed against evidence.
Learning outcomes
What you should be able to show.
- 01Classify workflow steps by behavior
- 02Avoid using a model for deterministic logic
- 03Place approval before irreversible action
Studio practice
Make the lesson visible.
- 01
Label every step
Mark each step as capture, validation, rule, retrieval, transformation, judgment, approval, or action.
- 02
Choose the mechanism
Assign forms, code, automation, search, AI assistance, or human judgment based on the behavior, not novelty.
- 03
Protect the action
Insert review, idempotency, confirmation, or a reversible queue before emails, payments, publication, or record changes.
Evidence to keep
Your lesson record.
- Classified workflow
- Mechanism decision
- Protected action boundary
REFLECTWhich current ‘judgment’ step is actually an undocumented rule?