Before
The approved baseline screenshot.
LOCAL VISUAL RELEASE GATE
Before/After Visual Change Proof Studio
Mark what was supposed to change before the run. Then expose every connected pixel cluster that escaped the plan—and preserve the exact proof bytes.
No upload. No visual guess.
Exact dimensions, locked zones, deterministic artifacts and SHA-256 receipt.
PNG · JPEG · WebP ≤16 MiB · ≤25 MP
STEP 1 · EXACT INPUTS
Choose the before and after screenshots
V1 intentionally refuses alignment and rescaling. Both decoded images must have identical dimensions.
After
The candidate screenshot to review.
STEP 2 · PREREGISTER INTENT
Draw only the areas meant to change
Drag on the image or add exact coordinates. Locking freezes the plan before analysis.
Load an exact image pair to draw intended-change zones.
Maximum RGBA channel delta below this value is ignored.
Explicitly bounded to 0.1% of pixels or 5,000, whichever is lower.
CONTAINMENT VERDICT
DECISION · EVIDENCE · NEXT ACTION
Changed pixels
Inside zones
Outside zones
Connected clusters
PROOF VIEWS
Inspect the change, not a score
Swipe and onion expose alignment; blink exposes drift; heatmap locates connected changes.
BeforeAfter
EVIDENCE PACK
Exact bytes for review and handoff
Every download is hashed before it is shown. The receipt covers the six evidence artifacts.
Connected cluster ledger
| ID | X/Y | Size | Pixels | Outside zones | Contained |
|---|
Method, assumptions and limits
PUBLIC METHOD
A visual diff that refuses to pretend
1. Exact coordinate space
Magic bytes and browser decode must agree. A dimension mismatch stops the run; V1 never aligns or rescales.
2. Intent before evidence
Lock normalizes the zones and SHA-256-binds their exact geometry, dimensions and profile before analysis. Any zone edit invalidates that registration and every prior export.
3. Recheckable packet
Deterministic PNG/SVG/CSV/JSON/HTML/Markdown bytes and the zone-registration hash are covered by Receipt v1 and can be independently mutated and verified.
Method sources
Reviewed 11 August 2026. These sources define supported file structure, browser pixel extraction and exact hashing—not visual quality.