Lesson 1.4Lesson 4 of 30

Enforced workflows and handoffs

Implement multi-step workflows with enforcement and handoff patterns

Key points

1If an order of steps must always hold, enforce it in code: a prerequisite gate blocks process_refund until get_customer has verified the customer.
2Prompt instructions are guidance. Even a good prompt has a non-zero failure rate, which is unacceptable for money or identity rules.
3A multi-issue request: split it into concerns, investigate them in parallel with shared context, answer with one combined resolution.
4When escalating mid-process, hand the human a structured summary: customer, root cause, what was tried, recommended action. They do not see the transcript.

What the exam guide checks here

Objective wording from the exam guide (English).

1.4.K1Programmatic enforcement (hooks, prerequisite gates) vs prompt-based guidance for ordering
1.4.K2When deterministic compliance is required, prompt instructions alone have a non-zero failure rate
1.4.K3Structured handoff for mid-process escalation: customer details, root cause, recommended actions
1.4.S1Programmatic prerequisites block downstream tools until prerequisites complete (e.g. process_refund until verified get_customer)
1.4.S2Decompose multi-concern requests, investigate each in parallel with shared context, synthesise one resolution
1.4.S3Compile structured handoff summaries for humans who lack the transcript

Answer scenario questions on this topic. Every option comes with an explanation.