The short answer
Terminology varies by product. Think of a workbench and procedures rather than another model.
Try it in three steps
- List what a filing task needs besides a model.
- Add input folder, output path, error log and stop rules.
- Identify omissions that would prevent review.
A practice prompt
Before you start
Map execution support to one observable task.
Practice material (fictional)
Task: read two notes and create an inventory. Needs: access scope, reader, output path, check record and stopping condition.Replace placeholders in the prompt with this material, or append the material if there are no placeholders. Reading time excludes doing the exercise.
List inputs, tools, permissions, state and checks for a read-only file inventory. Do not select paid services or execute it.What to look for (not a recorded test result)
Separate model generation from permitted actions, execution and checks. Explain the effect of missing pieces rather than memorizing a term.
If it goes wrong
The harness label does not establish reliability; inspect working controls and checks.
Check your result
You can explain the model's role separately from execution and verification.
References and scope
The links below support the concepts or product navigation. The steps and exercises are our teaching suggestions, not official certification or measured customer outcomes. Product interfaces and availability may change. References checked on 2026-10-17.