The In-Haus method
The
people.
AI builds. Stewards govern. Owners own.
AI builds. Stewards govern. Owners own.
- Owner
- Signs for the whole project: Contract, Access, Blueprint, Full sign-off and Delivered. Never each build phase.
- Stakeholder
- Signs a build phase when the Master Blueprint or their Build Inspector calls for it.
- Build Inspector
- Runs each build phase's tests and approves.
- Chief Architect
- Owns the Master Blueprint, signs Readiness, approves the merge list and signs the single merge to main for each build phase.
- Build Architect
- Per build phase, writes and signs the build spec and its acceptance criteria, and updates the spec when an answer changes it.
- Build Foreman
- Runs the build as it happens: clears bottlenecks, leads human and AI coders, and runs the inspection after each build phase.
- Customer Crew
- Code beside the In-Haus Crew and check the code against the Building Code.
- Building Code Owner
- Answer questions about their area of the Building Code by signed link, with a named backup.
- Stewards
- Design, Build and Delivery Stewards govern and sign their gates. No AI holds a Steward title.
- Chief of Staff
- The single channel for people: reads back what it heard, routes the work and keeps the record. It never decides or signs.
- In-Haus Crew
- Build, test and draft. An AI manager approves each agent's work before people see it. The crew never decides or signs.
Start with Vet
Run it on your next system.
The framework is free to read. A build runs in the App. A scoping call is where Vet begins.