# Browser evidence

The deterministic verify-browser tool builds current source and checks planned routes at 375 and 1080 pixels. It records screenshot paths, image failures, overflow, h1 counts, labels, internal navigation targets, and console errors against source and output hashes.

This is mechanical evidence, not a visual-quality verdict or proof that a live backend accepted a lead. Critics must inspect the rendered images and copy. Never invent evidence when the browser is unavailable. Repair failures, rebuild, and rerun before completion.


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.

For new-build icons, read `icons.md` and inspect compiled glyphs at actual desktop/mobile sizes. Verify semantic fit, visible labels, counters, alignment, supported families, duotone contrast and accessible names on controls. Library review is not page-level evidence; locate and repair inappropriate selection, sizing or color.

For sites with typography version 1, load `typography.md`. Establish concrete shared roles before authoring, reuse sizes and weights across routes, retain the 12px rendered floor, and repair browser typography findings before acceptance. Template identity does not waive this policy.

For requested appointment booking, load `scheduling.md`; use the standard component and verify the compatible admin connection. Do not enable it on sites that did not request scheduling.