Thesis/Bet 01ProductOperating

The Design Scan.

The visual analog of Lovable's Security Scan. Point it at any Lovable project. It captures a full-page screenshot, sends the actual pixels to Claude alongside the project's DESIGN.md contract, and returns findings drawn from what the model can actually see. Slop. Drift. Voice. Unjustified novelty. Hierarchy, type, and contrast as they actually render.

The bet: every Lovable project should ship with a DESIGN.md, and the platform that reads it on every generation is the platform that sets the taste bar at scale. Three flavors. A general contract any Lovable app inherits by default (layout, type, consistency, the floor). An internal contract Lovable holds itself to, so quality stays high while velocity stays high. And the one a team writes for their own product, so every generation lands on-brand. This site is audited against its own. External URLs get the general one.

   DESIGN.md ──────┐
                   │  contract
                   ▼
   any /url ──▶ ┌──────────┐ ──▶  ┌─ slop      ── 3   findings
                │   scan   │      ├─ drift     ── 1   finding
                └──────────┘      ├─ voice     ── ok
                                  └─ novelty   ── flag, justify or revert

Fig. 01 · Every generation is read against the contract. Findings, not memos.

Design scanIDLE

Contract: project

Awaiting first scan

◢ Audited against this site's DESIGN.md-

§ Audit write-ups

Scans, written out.

The five-part memo treatment of selected live audits. For when the findings deserve narrative context.

Loading memos…

←Back to the thesis The Filter→