Module 02 Summary
What this module established
A goal must name the artefact or decision that means it is finished, or the agent elaborates until a ceiling stops it. Every instruction should name an output it makes impossible - if you cannot name one, the line is costing tokens and diluting the ones that work.
Carry forward
- Bound steps, time and actions independently, and check success before the ceilings. Actions need their own bound because they are the expensive failure.
- Build three outcomes. A system with two reports a missing input as its own failure, and pushes ambiguous cases into confident answers.
- Write the task as structured fields. A paragraph hides its own gaps.
Before moving on
Move on when your task has four stopping conditions, a third outcome, and a colleague can say from the definition alone when it would be finished.
