Free AI learning · Mission 3 of 3
Prepare for human approval
Decide whether a bounded action is ready to put in front of its human approver. Readiness to review does not authorize execution.
Original fictional records and scripted feedback. No model is running; no message, code or approval is sent.
- 1First case
- 2Changed case
- 3Takeaway and quiz
Everyday decisions · First case · guided practice
A message ready to review
Decide what to do with a proposed message. Nothing can actually be sent here.
Fictional review packet · C13–C15
C13 · Draft v1
To: Cedar Shop service desk. Message: Please explain repair or return options for a kettle that stops before boiling. Bought 14 days ago. No home code or payment details included.
C14 · Evidence
The draft matches the receipt and fault notes. The service-desk destination was checked against the fictional receipt.
C15 · Authority
The household owner must review the exact message and destination before sending. No send approval has been given.
What action is ready now?
Compare the proposed artifact and its reasoning. You can use the feedback to revise your choice.
Why this decision matters
A workflow needs an explicit scope, an inspectable result, relevant evidence and a person with authority. Pause when a material fact changes. Human approval applies to the reviewed action, not every future action.
Choices stay in this page’s memory. Your browser may restore this page and its previous choices when you return. Reset this mission clears its choices, takeaway and lesson quiz attempts. On a shared device, use Reset this mission before leaving.
A message ready to review
Decide what to do with a proposed message. Nothing can actually be sent here.
Fictional review packet · C13–C15
C13 · Draft v1
To: Cedar Shop service desk. Message: Please explain repair or return options for a kettle that stops before boiling. Bought 14 days ago. No home code or payment details included.
C14 · Evidence
The draft matches the receipt and fault notes. The service-desk destination was checked against the fictional receipt.
C15 · Authority
The household owner must review the exact message and destination before sending. No send approval has been given.
What action is ready now?
Choose a proposal before reading its rationale.
Send because the draft looks complete
Send draft v1 now.
Needs revision. C15 explicitly requires approval first. A complete review packet does not grant send authority.
Present the exact message for approval
Ask the household owner to review draft v1, destination and C14's checks. State that nothing has been sent. Wait for an explicit send decision.
Fits the records. C13–C14 make the bounded proposal inspectable. C15 identifies the approver and the remaining decision. This is ready to request review, not to send.
Ask for permanent permission
Approve all future shop messages automatically.
Needs revision. C15 concerns this exact message and destination. It gives no basis for broader future approval.
Changed case: the destination changed
An approval exists, but the proposed action no longer matches it.
New fictional review packet · C16–C18
C16 · Approval
The owner approved draft v1 to the Cedar service desk only.
C17 · Changed proposal
Draft v2 now goes to an unverified personal address and adds the home entry code.
C18 · Boundary
No approval covers v2, the new destination or the added access detail.
Is the earlier approval enough?
Choose a proposal before reading its rationale.
Reuse v1 approval
Send v2 because a message was already approved.
Needs revision. C16 is specific to v1 and its destination. C17 materially changes both content and recipient.
Remove the code and send to the new address
Silently remove the home code, then send to the personal address.
Needs revision. Removing the code helps, but the destination in C17 remains unverified and outside C16's approval.
Pause, repair the packet and request fresh review
Do not send. Remove the access detail, verify the destination and show the revised message plus changes to the owner for fresh approval.
Fits the records. C17–C18 introduce new risk and exceed C16's scope. Repairing the packet and returning to the approver keeps control with the person affected.
Takeaway
- Show the exact action, destination and current artifact.
- Attach the evidence, known limits and any fallback.
- Name who can approve and what they are approving.
- After a material change, stop and return for review. A review request is not execution permission.
Paper practice is self-checked; independent demonstration has not been assessed.
Lesson quiz self-check
1 point for a correct answer; 0 for wrong or unanswered, out of 2 possible points. This paper version records no attempt or score.
A fictional club announcement has an exact draft, checked event date and verified member-list destination. The club secretary must approve before it is sent; no approval exists.
What is ready now?
- Send it because the date is checked.
- Publish it to a wider group instead.
- Show the exact announcement, date check and destination to the secretary for a send decision.
Answer and explanations
Needs revision: Send it because the date is checked. Evidence quality does not replace the secretary's approval.
Needs revision: Publish it to a wider group instead. That expands the destination and still lacks approval.
Correct: Show the exact announcement, date check and destination to the secretary for a send decision. The packet is inspectable and the approver is known. Review can be requested; sending must wait.
The secretary approved the 12 June announcement. The date changes to 19 June and the recipient list doubles.
Does the old approval cover this?
- Pause, check the changes and request fresh approval of the exact revised announcement and list.
- Yes, the subject is still the club.
- Send it, then tell the secretary later.
Answer and explanations
Correct: Pause, check the changes and request fresh approval of the exact revised announcement and list. Date and audience materially changed; the old approval covers a different action.
Needs revision: Yes, the subject is still the club. A shared subject does not preserve the approved date and recipient scope.
Needs revision: Send it, then tell the secretary later. Notification after execution is not the required approval before execution.