Safety and approval gates

Inhalt

Approval gates are checkpoints where the system pauses for a human to review a decision or output before taking a consequential action. They are critical whenever the cost of a mistake is non-trivial — sending messages to patients, writing to a real database, modifying a dataset. The design rule: gate on the *action*, not the generation. Drafting is cheap and private; sending is expensive and public. Every consequential side-effect gets a gate.

Beispiel: A participant communication draft (reschedule, reminder, eligibility decision) is generated automatically but must be reviewed by the coordinator before sending.

Hast du das verstanden?

• [ ] The workflow pauses on a real approval action, not auto-proceeds
• [ ] Reject has its own logged path
• [ ] Timeout behaviour is defined (what happens if no one clicks in 24h?)
• [ ] Every decision row names the approver and the timestamp
• [ ] You can explain in one sentence what you learned that you would tell a labmate tomorrow

Direkt ausprobieren

Diese Links öffnen die laufenden Demos auf n8n.32dots.de + dify.32dots.de.