# Designesy — /contracts/monitor Canonical page: https://www.designesy.org/contracts/monitor --- ## Monitor Monitor is the continuous-governance layer: re-score a URL on a cadence, store snapshots, compute drift deltas against the baseline, and surface regressions before they compound. Every prior designesy surface is a snapshot — monitor turns them into a watched series. Version 0.1.0 · provisional · [machine export](/contracts/monitor.json) ## Source authority Designesy design intelligence research 2026-08-01 Into Design Systems 2026 — "weekly audits at cents per report, drift detection without dedicated headcount" Design Systems Collective 2026 (Enara) — "the system surfaces the shape of how drift happens, the only way to stop it before it compounds" Lollylop 2026 — "visual bugs are invisible to code reviews, every sprint adds a little more, drift catches it before it compounds" Designesy 2026 scan — no competitor combines URL-scoped production fetch + design-token-aware checks + scheduled cadence + trend-over-time ## Monitoring model Register a URL + cadence (daily/weekly/monthly). On each run, re-execute the 12 drift checks (d01-d12) and store a snapshot. Compute deltas against the first-run baseline: score delta, new violations, resolved violations, token-set mutations, and trend slope across the last 3 runs. Alert when score degrades beyond a threshold or when new violations appear. **Snapshot structure** ## Cadence options ## Alert triggers ## Verification 10 checks — 10 checks. PASS=1, WARN=0.5, FAIL=0. Score = (points/10) × 100. A≥90, B≥80, C≥70, D≥60, F<60. Note: the monitor score reflects governance health (is the watch working, is the site stable), not design quality — design quality is the /score surface. Validation: Designesy monitor engine — scheduled re-scan + snapshot storage + delta computation. Method: Re-run the 12 drift checks on cadence, store snapshots, compute deltas vs baseline and previous run, fire alerts on threshold breach. Browser-only checks: None — all checks are static CSS analysis + snapshot diffing, no browser needed. ## Open questions - Snapshot storage is client-side (localStorage) in v0.1.0 — production monitoring needs server-side persistence (database or KV store) - Email alerting (m10) requires RESEND_API_KEY env var + verified sending domain (monitor@designesy.org) — without the key, alerts surface in-UI only - Scheduled cadence (daily/weekly/monthly) requires a cron runner (Vercel Cron Jobs) — v0.1.0 monitors on manual trigger only - Cross-page drift (drift mode 2) requires crawling multiple pages — the monitor currently watches the single registered URL - The 3-run trend slope (m04) needs 3 snapshots — the first 2 runs will show insufficient data - Contract version drift (m09) probes for agent.json version field — not all sites expose one ## Run it Monitor any URL for drift over time: