Keep a record of the result

A decision pack explains what should happen. An outcome record explains what actually happened. Link the two.

Record the requested result, task, caller, acting identity, approval, source evidence, attempted action, destination, idempotency key and read-back result. Give remaining work an owner and next check.

Use distinct states: prepared, awaiting approval, applied, verified, failed or cancelled. Never mark a proposal as applied because its description sounds convincing.

Review a sample against the source system, including interrupted and rejected runs. A record without evidence is a pointer, not proof. Keep company-specific outcomes private.