Vibe coding vs production: one project, two speeds
A project is a set of features, each on its own clock. Vibe some, certify others — and never rebuild to switch.
The mental model people struggle with is that 'fast' and 'production-grade' usually live in different codebases. In Dual7 they live in the same one. The unit that moves between modes isn't the project — it's the feature.
Every feature carries its own state
Think of a project as a board of features. Authentication is certified and in production. Billing is certified. The new reporting view is still a draft in Vibe Mode. The AI assistant is an experiment nobody's ready to ship. They coexist, each on its own clock — and they don't block each other.
- Vibe the features that are still moving — iterate at full speed, no gates.
- Certify the ones that are ready — they run through the seven agents and go live.
- Only certified features reach production. Drafts stay in Vibe until you say so.
No rebuild to switch
Moving a feature from Vibe to Governed doesn't mean re-implementing it. It's the same code, certified. And you can move it back to iterate, then re-certify. The codebase is continuous from the first prompt to the production deploy — which is exactly why you never have to throw the prototype away.
Vibe what's moving. Certify what's ready. Same project, no rebuild.