What exception records should accompany a generated customer change?

Ask for these generated artefacts when the training objective includes repairing incomplete propagation.

- A failed downstream update receipt. - A queue item with an assigned owner. - A reason code tied to the failure. - A retry rule with stopping conditions. - A manual correction record. - A reconciliation result showing remaining gaps. - A closure note supported by repair evidence.

In healthcare administration, a contact number change can reach the patient administration record while an appointment reminder service rejects the update because its reference is missing. The failure should produce visible work rather than silently disappearing from the scenario.

The exception records can distinguish a temporary service failure from a broken record link. Those conditions require different responses: retrying may resolve the former, while the latter needs a reference repair before another attempt is useful.

MirrorFirm could generate both the failed operation and the evidence needed to repair it, including unresolved outcomes when the responsible team has not responded. This gives labs material for teaching persistence with boundaries. A model should continue useful repair work, avoid uncontrolled retries and retain an honest account of what remains incomplete.