The In-Haus method

House
Rules.

Ten rules every In-Haus build runs under.

Appetite, not estimate
Time and budget are fixed; scope flexes inside them.
Serves: Cost
Decisions are the critical path
Every open question is tracked, aged and shown. People decide and approve; agents never do.
Serves: Control
Verify before build
Every story has acceptance criteria and its own test, written first. It is done only when its test passes in the Build Inspector's hands.
Serves: Coherence
Daily loop, phase gate
Build and demo daily; sign off at the end of each build phase on the build schedule.
Serves: Community
Documents are views
Charter, roadmap, status, test plan and reports render from the record. Nothing is typed twice.
Serves: Coherence
Change is logged, never argued
A change order shows cost, time and what it displaces. Approved changes move the baseline and keep the history.
Serves: Control
Owned from day one
The Owner's data, decisions and Haus Rules are theirs from the start. Payments, the email domain and DNS are in their name. The build transfers at Deliver.
Serves: Control
Feedback becomes rules
Every correction becomes a rule, in two layers: ours under every agent, and the Owner's Haus Rules on top. A Haus Rule never weakens one of ours.
Serves: Community
Capacity is spent, never wasted
An agent with an open question logs it, with a due date and what it blocks, then takes the next Ready task.
Serves: Cost
Decided at approval
Each table's security and indexes are decided in the approved build set and enforced as tables are built.
Serves: Control

The five risks

What goes wrong with AI-built work.

Every House Rule, control and metric names the one it serves.

Cost: You approved a budget. Nobody can tell you where it went.
Here the budget and the window are fixed, and you see spend and forecast on one screen.
Control: Your vendor holds the code, the accounts and the decisions.
Your accounts are yours from day one. The code and data are yours at handover.
Coherence: What ships isn't what the business signed off.
Every feature is agreed, with its test, before anyone builds it.
Compliance: No one can show it's safe to put customers on it.
It's tested, checked for security and restored from backup before launch.
Community: Your people are left out of the build, then left holding it.
They test it, sign it off and run it after.

Start with Vet

The framework is free to read. A build runs in the App. A scoping call is where Vet begins.