Quality gate
No app should be released just because the AI finished typing
Quality Agent release gates
Blueprint and requirements
Roles, pages, data model, monetization, integrations, and edge cases are documented.
UI matches requested app
The generated frontend must visually match the user request instead of drifting to the wrong industry.
Clickable preview
Navbar, CTAs, cards, forms, chat, cart/booking buttons, and status panels respond in preview.
Mobile responsiveness
Phone, tablet, and desktop layouts use stable constraints with no overlap or clipped controls.
Primary workflow
The main customer journey works end-to-end with validation, state changes, and confirmation.
Backend contract
Database plan, generated routes, auth roles, and UI screens agree with each other.
Security scan
Secrets, auth rules, database policies, upload safety, payment/webhook logic, and user-only actions are reviewed.
Deployment smoke test
Production build, env variables, API health, and generated app preview are checked before export or publish.
Release rule
90%
Minimum release score. Apps below the threshold stay blocked and go back to the builder, UI reviewer, backend reviewer, or setup concierge.