Design a safe write-action pipeline for tools that can modify customer data.

Instruction: Preview an exact mutation, bind any required approval, recheck authorization, and detect concurrent changes.

Context: Design customer-data writes so the assistant cannot silently apply a stale, broader, or differently approved change.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

I would make the tool accept a narrow patch, not unrestricted database commands. The service validates editable fields and business rules, then produces a preview showing the target record and before-and-after values. Any required approval refers to that patch, target, and record version.

At execution, the backend rechecks...

Your preparation path

Work through these questions in order. Read the answer aloud, then explain it in your own words.

Related Questions