EE VIZN

Status: FUTURE (Phase 3 capture, Phase 6 agent lenses). Not a running service.

Job

EE VIZN is visual intelligence for EE Holdings. It is not a replacement for Compacter generation. It inspects what a human would see.

Inspection targets: websites, dashboards, mobile layouts, screenshots, generated images, branding, UI consistency, spacing, typography, accessibility, broken layouts, forms, buttons, charts, navigation, application states, visual regressions.

Lenses

A lens is a named observation policy: viewport, auth persona, URL list, wait strategy, screenshot set, rubric weights, compare-to baseline.

Examples: backout.checkout.mobile, compacter.pricing.desktop, eefinance.symbol.chart.

Agents attach lenses the way they attach API keys. The output of a lens run is assets + evaluations in Pastes, not a chatty caption dumped into Slack.

Website-wide optimization

Website -> Playwright (or equivalent) -> screenshot -> VIZN analysis -> Pastes experiment -> score -> generate alternatives -> screenshot -> score -> winner -> human or auto promote -> deploy -> recheck -> record.

Reusable winners: navigation, cards, dashboards, forms, pricing, onboarding, checkout, buttons, type, tables, charts, landing sections, mobile layouts.

Card example: v1 71, v2 76, v3 88. v3 becomes the recommended template in the EE component memory. Compacter and other builders should pull that template. They do not today.

Providers

Pluggable: hosted vision APIs, self-hosted VLM, deterministic CV (layout boxes). The Pastes evaluation row records evaluator_type=vision and provider id so routing can prefer the judge that matched humans.

What VIZN is not

Not a design tool.
Not a CDN.
Not a substitute for unit tests on money movement.