Lesson 5 of 6 · 0%Hold at the human decision boundaryNext
Course map

Channels, Messaging and Real-World Integrations

0 of 6 complete0 of 6

Lesson 5.1 · 45 minutes

Hold at the human decision boundary

Separate drafting from external delivery, log approval, and escalate uncertainty without leaking context.

Skip course map
Current lessonHold at the human decision boundary0% complete · 0/6 lessons

Channels, Messaging and Real-World Integrations

0% complete · Current: Hold at the human decision boundary

Draft lesson: awaiting independent technical and publication review; do not use it as production configuration guidance.

Editorial review pendingon version support under review

Action boundary

Before you act

Expected result
A synthetic draft cannot leave the test boundary without a named, logged approval decision.
Failure mode
A generated draft is treated as consent to send or a timeout becomes automatic delivery.
Rollback
Hold the route, revoke pending delivery authority, and ask the designated owner to resolve the decision.

Orient

Generation is not permission. The human gate belongs immediately before the irreversible external action.

Perform

Define the approval record: decision ID, approver identity, scope, destination, expiry, decision, and reason. Make expiry resolve to hold, never send.

Lab

For a synthetic support request, classify the request, draft a response, send the draft to a named approver, record approval or rejection, then allow or block delivery. Keep the original test message out of the escalation summary unless necessary.

Check

Your escalation handoff names the uncertain decision, accountable owner, deadline, and safe interim state. It does not contain a copied customer conversation or credentials.

Continue

Lesson 6.1 shuts the path down and proves it stays down.

Lesson checkpoint

Ready to move on?

Mark this lesson complete when you can apply its outcome without relying on the examples above.