design-review

Findings are tagged P0-P3 (Blocking / Major / Minor / Polish) and reported individually — there is NO aggregate score, health score, or letter grade, ever; an aggregated number invites self-grading theater.

The visual review is a bounded loop, maximum 2 fix cycles: the loop exits PASS only once the register-applicable positive floors are actually met, and a plateau (cycle 2 repeating cycle 1's finding) stops immediately even at cycle 1 of 2.

Before any "done" claim, a mandatory in-loop challenger gate judges the deliverable blind — fresh-context, off a rendered PNG only, never fed this procedure's own reasoning. A Block from the challenger must be resolved or owner-accepted before "done" is reported.

Design Review — Final Quality Gate

When

After design-motion (web/webapp) or directly after the mockup (design-ios/ design-android). The last step before reporting any design deliverable done — never skipped, never reported as passed if it wasn't actually run (references/review-procedure.md Failure Handling).

Input

• The complete rendered artifact: components/mockup with animations (if any) and interactive states.
• design-system.md as the audit baseline (tokens, forbidden fonts, contrast floors).
• The Je reproduis line written by design-web/design-webapp — three declared elements, two tagged [corpus: {reference}/{tokens section}] (measured procedure, the craft) and one tagged [sector: {url} — register] (register signal only; [sector: none — register from brief] is valid, an empty slot is not). A missing or untagged line is a blocking Part 1 finding — the binary verdict has no input without it.
• The corpus pages opened (Gate 0 artefact 3): at least two {reference}-recode/index.html, named. The [corpus: …] tags prove the corpus was read, never that it was seen — and a page sourced from markdown alone clears every mechanical check and reads dead. Absent ⇒ blocking Part 1 finding.
• The on-screen inventory (Gate 0 artefact 4): what each section physically carries, plus the screen-holding-floor verdict. Blocking when VISUAL_DENSITY ≤ 3 or DESIGN_VARIANCE ≥ 6; reported otherwise.
• Any declared premium pattern(s); the signature element (design-method Step 2) instead gets a Signature Dominance verdict.
• The plan's two structural picks — hero treatment (design-method/references/macrostructure-bank.md) and body sequence (design-method/references/body-sequence-bank.md). A plan naming neither is itself a detector signal (anti-slop entry 15). brand register; a product deliverable carries neither.
• The register (brand/product, from design-method Gate 0) — an input, never inferred mid-review: check 14's floors, Part 2 item 8's floors and the Lookalike Test (item 8b) all branch on it.