A build isn't done when the code is written — it's done when it survives all six.
Every file builds cleanly. Syntax errors and broken imports never reach you — they're caught and repaired before the run continues.
The app starts in a clean sandbox and stays up — no crash on launch, no silent white screen.
Each screen in the plan is visited and answers. Dead routes, broken links, and error pages fail the run.
The promises from your plan — "booking a spot decreases availability" — are each driven end-to-end and checked individually. Your proof list uses your words.
Four named security checks ride on the same receipt: no secrets in the code that ships, no secret behind a public prefix, private pages behind sign-in, and the database's own security advisor. Each reads proven, found wanting, or skipped — with the reason.
Every screen re-checked at phone width in a browser — nothing cut off, nothing unreachable. It checks the web app at phone size, not on a real phone.
The agent that writes your code and the agent that checks it are separate — different roles, different context, different incentives. The verifier only sees the plan's promises and the running app, so it tests what you asked for, not what the builder thinks it built.
When a check fails, the failure goes back to the builder with the specific broken promise — and the run repeats until every gate is green or we stop and tell you honestly.
Any build's receipt can become a public, read-only page at australis.io/r/… — what was checked, what passed, each behaviour by name. Press Share receipt on the verdict card or in the preview toolbar, then send the link to a client or a teammate.
The security pass runs again each time a build lands, and its findings show as a shield on the receipt. A check that couldn't run — no database, nothing to sign in to — says so instead of pretending to pass.
Request the beta, describe an app, and watch the verifier drive it. The proof does the convincing.