Module 07 Activity

Scenario

The workflow is about to be trusted with something that cannot be undone. This module is what makes that defensible.

What you build

A human gate placed by reversibility, with editable state, explicit approval, a guarded effect and an audit record.

Steps

1. Sort every step by reversibility and choose the gates. Justify keeping the count low.
2. Compile with interrupt_before on the node after each gate, and confirm the pause holds no connection open.
3. Decide which state fields a reviewer may edit and enforce it. Guard flags and counters are not editable.
4. Make approval a state field the acting node checks, separate from the resume itself.
5. Test a duplicate resume explicitly - resume twice and confirm the effect happened once.
6. Record who approved what, when, and which fields they changed.

Evidence to hand in

• The reversibility table and the chosen gates.
• The editable-field policy and how it is enforced.
• Evidence that a duplicate resume produced one effect.
• One audit record naming reviewer, timestamp and edited fields.
• The seven-piece checklist from Unit 04 with each item's status.

Review checklist

• Gates are placed immediately before irreversible steps, not at the end.
• The gate count is low and the reason is stated.
• Guard flags and counters are not reviewer-editable.
• Approval is a state field, not an implication of resuming.
• The duplicate resume was tested, and all seven pieces are present.

Mark complete