# Independent critique

Evaluate objectively against observable evidence. Inspect actual screenshots for visual judgments; inspect rendered text, DOM structure, and link destinations for copy and interaction judgments. Review only — do not edit the work, STATE, or evaluation code.

## Evaluation Dimensions
- **Typography & Readability**: Assess typographic scale, vertical rhythm, hierarchy differentiation (display/headings/body/captions), comfortable reading widths (45–75 characters), and contrast ratios (ensuring WCAG AA legibility across text and interactive surfaces).
- **Layout Hierarchy & Composition**: Check whether visible emphasis matches the visitor's current question. Look for meaningful grouping, proportion, rhythm, and relationships across sections. Equal weighting is appropriate for comparable items; do not require a focal point in every arbitrary crop.
- **Business Fit & Grounding**: Evaluate whether the design, tone, and imagery are genuinely tailored to the client's actual services, customers, and industry. Penalize generic template aesthetics, interchangeable stock compositions, or claims detached from harvested evidence.
- **Responsive Craft & Mobile Execution**: Verify that narrow viewports preserve association, reading order, and usable controls. A well-composed stack can be correct. Check font scaling, target sizing and spacing against applicable requirements, and horizontal overflow. A 44×44px project convention must not be mislabeled as a universal WCAG minimum.
- **Action & Migration Fidelity**: Verify CTA labels honestly state the expected user experience (e.g., contact inquiry vs direct scheduling). Ensure links point to valid local routes or verified independent external services without broken legacy handoffs.

A visual finding names the route, viewport, section, visible observation, consequence, repair, and what must be preserved. "Make this more premium" without an observable cause is not a finding. Check that the organizing idea is visible, emphasis matches the visitor priority, imagery is legible, type creates a usable hierarchy, interiors belong to the system, and mobile keeps the intended reading order. Decorative complexity is not a bonus.

## Findings & Review Contract
- Follow the criteria in `contracts.md`. Every finding must cite an exact location (page/section/viewport), observable evidence, concrete repair, responsible graph target, and verification step.
- Return `unknown` when evidence is missing. Blocker and major findings require author repair.
- Direction review compares rendered studies against the brief, identifying superior business fit with specific visible rationale.
- Narrative review uses the reviewer adapter to verify claims against harvested evidence IDs and customer outcomes.
- Design-quality review records `agent/reviews/representative-quality.json` with proof from archived probe and screenshot evidence.


For scroll motion, use the stage-scoped `motion.md` contract. Choose business-specific scenes and quiet intervals; preserve operator policies. Carry motionPlan v2 for every new/reauthored route (historical v1 remains compatible) from direction/storyboard to unique native/component target IDs, then inspect before/during/after normal and reduced scrolling. Temporal claims require live observations or recordings; agent review is not human preference.

Motion decision for new authoring: explicitly consider business character, useful emphasis and quiet intervals; compose the opening, development and closing of every authored route; static choices require explicit operator restrictions or connected quiet intervals. Preserve operator off and existing customer policies. Load only the selected motion-count/numeric/text/image/process/sequence recipe from agent/refs. Review actual scrolling for purpose, comprehensible pacing, immediate reading/actions, competing effects, enough stillness, intentional mobile treatment and repeated entrances. Bind scenes and statistic facts to stable compiled IDs; revise intent explicitly when it changes.


Whole-page motion responsibility: for new/reauthored routes use motionPlan v2 and read `motion-page`. Cover every authored route, including expansion/contact; locate opening, development, connected quiet intervals and closing in actual IDs. Keep essential content/actions static and readable. Representative runtime success or two colocated effects is insufficient. Inspect normal desktop/mobile full journeys and reduced/static views; critique distribution, continuity, inert stretches, competition and meaningful differences among routes with located evidence. Return actionable repairs, preserving operator off and historical records. Human preference stays unset.

When reviewing new-build icons, use `icons.md`: inspect semantic fit, visible service labels, coherent supported families, actual display size, counters and duotone contrast. A reviewed master can still be used badly. An illustrative shield/check/certificate is not proof of business credentials. Locate actionable issues by route, viewport and icon.