Case Room first.
The builder confirms the product truth, source-of-truth records, survival boundary, and first-version scope before payment.
The package inherits authority from the confirmed case.
The files do not invent a plan from scratch. They carry forward the decisions you already reviewed and confirmed.
The hierarchy matters
The package is not five disconnected documents. Every file inherits from the confirmed recovery boundary.
Recovery run second.
The backend run materializes the confirmed case into architecture, technical blueprint, workflow, and AI implementation sessions.
Implementation handoff third.
The package gives the next coding session a stable boundary so it stops reinterpreting the app from scratch.
Five files with five jobs
A five-file recovery and implementation package built for decision, execution, and handoff.
Read first, understand the handoff, or jump straight into the leader/executor flow.
The governing product structure, objects, workflows, authority boundaries, and scope horizon.
Modules, records, write paths, interfaces, jobs, validation, security, and recovery behavior.
Campaign 0 sets up the selected operating environment; later campaigns pursue case-specific outcomes with proof gates and replan triggers.
Leader, executor, and single-agent prompts that bind the campaign to repository reality and builder decisions.
Built first for existing apps that have drifted.
Existing AI-built app recovery: restore product truth before the next build session.
New builds are supported when a trustworthy product direction needs to be formed before code begins.
Driftbreak is not a generic spec generator or a prettier planning chat.