How it works · Step 4 of 4
Confirm: did the fix hold?
After the fix runs, the Worker re-checks the target the fix was meant to repair. If the check fails, the reverse steps its author wrote run in reverse order.
After the restart, the Worker re-checks nginx on web-01.
After the restart, the Worker re-checks that /healthz answers on web-03.
After the cleanup, the Worker re-checks disk use on web-06.
The step
Confirm re-checks the fix's own target.
AI drafts the check when the ActionBook is written. Your engineer corrects it. Your team decides what recovered means.
A run that only says “executed” has not told you whether the service is back.
The fix held
The run closes, and the record says so.
The fix didn’t hold
The reverse steps its author wrote run in reverse order. The event stays open, and the record names what could not be undone.
What it checks today
Confirm runs the check written into the fix.
Here is the line.
The run ends with a record. The record shows the event, the facts the Worker gathered and how the run ended. If a fix ran, it also shows the fix and its re-check.
