CASE STUDY
LOCAL PROOFVoza — 256-Screen Verification System
Verification system for a 256-screen consumer language-learning app — a machine-computed, 4-tier proof report (repo: Voza-e2e-stabilization).
Topology: a 256-screen registry drives npm run verify, which fans out to Tier-1 static, Tier-2 logic, and Tier-3 engine-contract gates that all write into a machine-computed PROOF_REPORT. The same registry generates 257 Maestro flows feeding a Tier-4 device certification that honestly reads 0 of 256 until re-run.
PROBLEM
A 256-screen native app had no honest answer to "which screens actually work" — hand-edited status docs do not scale.
BUILT
A registry-driven 4-tier verifier machine-computes a PROOF_REPORT no human can edit and auto-generates 257 Maestro device flows against the live backend.
- screens green on Tier 1–3
- 256/256
- generated Maestro flows
- 257
- live service contracts wired
- 36/36
- production API routes behind them
- 176
- Hand-edited scorecard drift
- One redbox cascading 139 failures
- Stale device-cert claims
- Transient device flakes
INTERACTIVE — HOVER THE PYRAMID
E2E BROWSERProtects the highest-value user flows: auth, checkout, forms. Failures capture traces and screenshots so bugs arrive pre-reproduced.
Playwright · Chromium · trace files