What the change is intended to accomplish and which existing promises must survive
Make the consequential change without letting it silently redefine the system.
Driftbreak frames the requested change against the product's governing decisions, architecture, affected workflows, and protected behavior before implementation begins.
The situation
The request sounds local, but it may change ownership, state, permissions, source-of-truth records, user promises, or several connected screens and services.
What Driftbreak must resolve
Which product objects, workflows, actors, and authority boundaries are affected
Whether the current architecture can absorb the change or must be deliberately revised
How implementation will prove the change without treating collateral regressions as acceptable
What leaves the case
An updated system direction and bounded implementation campaign that tells the coding agent what changes, what remains protected, and what evidence closes the work.