Mirror starts with visual truth
Mirror begins with measurable rendered output rather than pretending it can infer everything about source code.
Start with the rendered result
It is tempting to build a design-comparison tool that reads your source and explains what to change. That is the interesting version of the problem, and it is also the version that quietly guesses.
Mirror starts somewhere less glamorous and far more defensible: the rendered output. A reference image, an implementation, a chosen viewport, a deterministic capture, and a measured comparison between the two.
Measurement before inference
A difference view, a threshold and a set of mismatch regions are facts about two images. They can be reproduced, reviewed and argued with. Advice about which CSS rule caused the difference is an inference, and inferences deserve to be labelled as such.
Mirror keeps those two categories visually and structurally separate. Anything measured is presented with the evidence that produced it.
Local first, and honestly so
Planned Local V1 is designed to work without a Paddy Systems Account, with references, captures and reports staying local by default. Chromium is the authoritative first rendering engine, so results are consistent rather than negotiable.
Cloud projects, history, collaboration, GitHub workflows, CI and Figma are upcoming, and are described as upcoming everywhere they appear.
What Mirror is not
Being specific about the boundary is part of the product.
- Mirror is not a generic DOM or CSS debugger.
- Mirror does not claim it can automatically fix source code.
- Mirror is in development and is not presented as launched.