A sealed brief

A build with an unusual set of rules. The agent gets one file. It may not ask a question. It may not say what it is building. Its only progress report is a percentage.

Where the brief is silent, it picks the most defensible option and moves on. If it cannot finish something, it finishes the rest and lists the gap in the handover. It may not ship a fake.

This removes the person from the middle of the work, which means the checks have to do the job a person would have done. So the gates enforced no internet permission, a note on how each test could pass wrongly, contrast, and backups that actually restore.

It produced a working app. It also made one thing plain. There is no human gate during a sealed build, so the gates are the only reviewer, and the handover is the only moment anyone finds out.