Put your review packet to the test
Close the worked answers and examine what you produced. A useful review lets another engineer follow your decision, challenge an assumption and test the proposed control. Use the prompts below to find the part that still needs work.
Sign in to save your reading progress. You can use these review prompts without an account. Lesson access follows the course syllabus.
Check the artifacts
Boundary map and permission table
Have you separated the person requesting help, the service acting for them, the source owner and the eventual recipient?
Output and tool contracts
Does the design cover saved and streamed output, changed permissions, queued actions and an external operation whose result is still unknown?
Evaluation report
Can a reader identify each denominator, what counted as success, what was unobserved and whether valid work remained useful?
Release and response packet
Is the permitted operating scope enforceable, with evidence for the decision, unresolved blockers, owner roles and criteria for restarting after containment?
For each prompt, point to a decision in your own work. If you can only repeat the lesson's wording, revisit its exercise and explain what would change your answer.
TRY A CHANGED REQUIREMENT
Can the reasoning travel?
Give a fictional support assistant two new requirements: send a draft later and include an attachment. Work out which permissions can change between drafting and delivery. Update your output contract and one allowed and one denied evaluation case before proposing a release decision.
Write the revision before checking the course examples. Name the changed boundary, a justified decision, a remaining uncertainty and a test that could disprove your conclusion. Use fictional data or work you are authorized to review.
Choose your next step
If the decision still feels uncertain, return to the project and compare your revised memo with its worked feedback. Defend retrieval, output and tool decisions under different constraints.
NEXT COURSEReview an engineering agent →
Extend the method to delegated work, repository changes, memory and interrupted tasks.
Share the course syllabus and its free lessons with a colleague if they are working through similar questions. Keep private review material out of anything you share.