Which existing behavior is authoritative and worth preserving
Understand what exists, then decide what the product should become next.
Driftbreak joins current product reality with the builder's intent so the next implementation phase does not begin by reinterpreting the whole application.
The situation
The product already exists and may work, but its next version requires more than another isolated feature request or generic planning document.
What Driftbreak must resolve
Which current assumptions, records, and workflows need evidence before they govern new work
What the next product boundary is and what should remain unchanged
How the architecture and technical plan should evolve without creating parallel authority
What leaves the case
A package that connects current reality to the next confirmed product and implementation direction without pretending Driftbreak inspected evidence it was not given.