Quick: gate a write with approval

Short recipe — one approval, correctly placed. Approvals live on nodes, not in a separate app.

Steps

1. Open the workflow containing the external write (destination or ontology write node).
2. Select the writing node and open its policy block.
3. Require approval at node level — the gate sits as close to the effect as possible. Workflow-level approval covers launches; node-level covers consequences.
4. Check the aggregated permissions view: the gate shows on the node and rolls up to the graph summary.
5. Dry-run to confirm the gate triggers: the preview should state that approval is required before the write executes.
6. Commit the policy change as a version, then approve the first gated run deliberately — reading the evidence the approval presents. The approval record (who, what, why) stays with the run: future audits start there, not in chat logs.

Image: permissions view with the node-level gate highlighted and the pending approval state.

Done means no external write in this workflow executes without a named human decision. Policy fields in Workflow nodes; write rules in Write policies.