Design an approval pattern for an AI assistant that can draft and send emails.
Instruction: Keep draft creation separate from sending. Bind approval to the exact message and account that will be used.
Updated
Official answer available
Read the opening below, then unlock the full answer and practical guidance.
I would make drafting reversible and sending a separate capability. A draft record holds the sender account, To/Cc/Bcc recipients, subject, body, and attachment references. The assistant presents those fields clearly before asking for a send decision.
Approval would identify that draft version and its content hash...
Your preparation path
Work through these questions in order. Read the answer aloud, then explain it in your own words.
1. Start with the foundations
Build the vocabulary and explain the core decisions.
2. Apply it to a real workflow
Practice diagnosis, validation, and everyday tradeoffs.
3. Prepare for senior discussions
Explain failure boundaries, recovery, and production choices.
- Design a fallback strategy when tools are unavailable, degraded, or unauthorized. Member answer
- How do you implement MCP step-up authorization without losing scopes or retrying forever? Member answer
- An MCP request resumes after user confirmation. How would you validate its requestState? Member answer
Related Questions
-
easy
-
easy
-
easy
-
easy
-
easy
-
easy