We had an AI build two storefronts. Its self-review passed. Its browser QA caught 4 bugs.

We had an AI agent build two fictional storefronts one afternoon: a Warsaw watch manufacture and a tiny type foundry. It wrote the pages, ran them in a browser, declared its own work clean. Then we did what most AI-generated work never gets — we graded it.

We call it an acceptance gate: a fixed pass/fail checklist executed against the live page at three breakpoints. Not "make it look premium" — a rubric the model can't charm.

It caught four things the same model had already signed off on:

None of this is "AI can't design." All of it is "nobody ran QA on what AI shipped" — and an AI's own review is a rubber stamp, because it grades intentions, not artifacts.

The exercise pushed us to write down what repeats in AI-built UI. Poker logic — tells are the things you do when nobody's watching:

Here is the part that actually matters: the expensive tells are structural, not visual. Indigo is cheap — one line of prompt kills it before code exists, which is also why classifiers trained on visual tells chase a moving target. "Shipping a hero on a screen that needs a table" survives every color change. That is the class worth putting on a checklist.

We publish as KURSYWA PRESS. Disclosure, since this is a shop: the full doctrine is a $29 PDF; the 2-page extract is free → https://aiclub1.gumroad.com/l/tmamtm

Curious what the gate flagged on your AI-built page? Drop a screenshot description in the comments — worst structural tell wins a review.