Skip to content

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

  1. Task and delegation contract

    Can you trace every worker's authority to a current grant and show which resources and limits remain shared across the task?

  2. Workspace and effect rules

    Have you distinguished reviewing a proposed patch from applying it, and bound any approval to the intended immutable effect? What happens while an outcome is unknown?

  3. Memory and recovery decisions

    Have you checked both support for a stored claim and permission for its audience? Does resumed work preserve current authority and already committed or reserved resources?

  4. Workflow evaluation and release memo

    Does each capability have evidence, observation gaps and a useful-work check? Can you defend a reduced operating scope without implying the full workflow is ready?

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?

A fictional engineering team wants to reuse one agent's patch proposal in a second project. Change the task contract, source and recipient permissions, evidence requirements and effect identity. State what must be reviewed again and what evidence can reasonably be reused.

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. Test your reasoning about delegated authority, unknown effects, persistence and recovery.

NEXT COURSE

Build an AI security evaluation →

Audit the observations, sampling and comparisons behind an assessment recommendation.

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.