Why does a policy change require more than replacing a document?

A policy change creates an operational boundary. Work already in progress may have started under one rule but reach its next decision under another. The relevant question is not simply which document is newest, but which version governs the action being taken.

In utilities, a revised connection policy can introduce an additional site assessment before a booking is confirmed. A request received before the change may still need that assessment if confirmation happens after the effective date. Another request may retain its earlier treatment because an explicit transition clause protects confirmed bookings.

For environment builders, this creates a useful distinction between reading a rule and changing operational state. An agent must identify the governing event, compare it with the effective boundary, and determine whether existing progress can stand.

MirrorFirm could generate policy versions, pending requests and action permissions that expose this distinction. The training or evaluation value lies in decisions across time: applying new requirements where required, retaining valid earlier decisions, and explaining the boundary without treating every open item identically.