The job is a shippable site, not a surprise domain
An AI site factory is useful when it shortens research, contracts, generation, and checks. It becomes dangerous when it also decides that the result is good enough to be public. Shipsite splits those jobs. Automation may finish reversible work. Production is a named version plus a human yes.
Three decision domains, not a chatbot vote
The current protected domains are the PRD, design direction when the workflow asks for it, and production. Dijiang can explain the artifact and the blocker. It cannot approve the transition. That is not friction for its own sake. It is how a later agent, and a later human, can see why a live URL exists.
- Approve the PRD to start a build, not a domain.
- Approve production only after the same version has QA evidence.
- A rejection with a reason is a successful use of the factory.
Receipts over fluency
A fluent assistant answer is easy to fake. A deploy receipt is not: it names the version, the endpoint check, and the rollback pointer. Search submission, merchant checkout, and paid campaigns follow the same rule. If the evidence is partial, the UI must say partial.