Case Room first.
The builder confirms the product truth, governing records, scope boundary, and implementation direction before payment.
The package inherits authority from the confirmed case.
The files do not invent a plan from scratch. They carry forward the product and system decisions you already reviewed and confirmed.
The hierarchy matters
The package is not five disconnected documents. Every file inherits from the confirmed case direction.
Package 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 product 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 failure 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 on Intent-Fidelity Development.
IFD is the methodology. Driftbreak makes it operational. Your coding agent executes the resulting direction.
Intent-Fidelity Development resolves product intent into explicit authority, architecture, technical direction, and implementation work.
Driftbreak operationalizes that method through the Case Room and a connected implementation package.
Your coding agent or development team still writes the software from the direction Driftbreak helped establish.