Capstone: Approve a Safe Automation Plan

Review four prepared control examples, run twelve checks against the saved plan, and approve only its current version.

See the situation

Bring together the decisions you have saved. Prepared examples and current-plan approval are separate checks.

Samir · Workflow operator

The case

Capstone: approve a bounded control plan

Inspect what the examples can show, validate the current saved plan, and approve only that version.

Review four prepared control examples, run twelve checks against the saved plan, and approve only its current version.

Your task

Test your saved safety plan against the final cases. Repair missing controls before approving it.

Need a little guidance?

You’re done when: The approved version has bounded actions, independent gates, recovery, and tested failure cases.

Approval should represent a current, inspectable control plan.

Need a reminder? Reopen the worked example

Watch one example first

A report of zero refusals may mean all requests were safe—or the gate never ran. A controlled prohibited request plus a gate-execution event distinguishes those possibilities.

Why this follows from the evidence

Validate the saved control plan separately from prepared examples. Approval is not a substitute for observing a real implementation’s controls.

GTM Lab

Saved locally

Workflow Control Plan

sample-workflow-control-plan · v1 · draft

Review the prepared control examples

These requests and expected control responses were prepared by the guide to demonstrate independent controls. They were not sent through an executing workflow.

Correct by every rule, and unacceptableCorrect and unacceptable
The forbidden-state rule should hold a request that otherwise passes ordinary checks. Confirm that the reason names the renewal state.
A segment far larger than the capAt volume
The daily limit should defer overflow with record IDs and a next-cycle path, rather than silently dropping work.
The provider fails halfway throughPartial success
The state display should distinguish successful and failed records and keep the prior successful result visible.
A cleanup routine with a defectThe repair is the hazard
The preview should make the proposed repair visible by category before a write can repeat an earlier defect.

Run all 12 validation checks

The checks test relationships between sections that can be easy to miss when a plan is assembled piece by piece. Each runs by its stable ID and reports pass or fail with a reason.

Approve the current saved version

All twelve checks are green. What does this plan actually buy you?

The workflow is now safe to run.A person now checks the risky actions before they happen.Each control is now attached to a specific thing that would go wrong, so you can argue about the control rather than about whether the team is being careful enough.

Your place saves as you go.

Chapter 8 of 80 complete