Why should a customer update change more than one record?

A customer change often enters through one channel but affects several operational processes. A utilities customer changes their correspondence address. That may alter where bills and notices go, while leaving the service address, meter location and supply agreement unchanged. Treating every address field as equivalent creates a plausible but incorrect result.

For environment builders, the useful unit is the dependency graph around the request. Some records inherit a customer detail. Others hold a separately agreed value. Historical documents may preserve the detail that applied when they were issued. An agent needs to distinguish these relationships before taking action.

MirrorFirm could generate an environment in which these dependencies are expressed through records, operating rules and available actions. A request can then require inspection, selective updates and a clear account of what remains unchanged.

This matters because a successful write operation says little about business correctness. Training or evaluation can instead examine whether the agent follows the meaning of the change through the organisation, including the boundaries where propagation must stop.