Sentinel is the QA layer that runs after every Platform build. It scores Lighthouse, accessibility, completeness, and copy quality, then publishes a composite 0-100 score with a receipt. If anything regresses on a re-deploy, you'll see it before users do.
Performance, Best Practices, SEO. Run from Google's official Lighthouse CLI. p50 / p95 of the 4 subscores → composite.
WCAG 2.2 AA compliance: contrast ratios, semantic HTML, alt text, keyboard nav, ARIA roles, color-independence.
Does it have the sections it should? FAQ, contact, pricing, footer, sitemap, OG image, favicons, robots.txt — checked.
Claude-Haiku rates copy on clarity + tone + grammar + brand-fit. Cheap, fast, surprisingly opinionated.
Each axis returns 0-100. The composite weights performance + copy slightly higher than the others (those are what users actually feel). Weights are tunable per project.
Production-ready. Ship it. Re-scored on every redeploy to catch regressions.
Ship with caveats. Sentinel surfaces the lowest-axis issues + suggested fixes in your dashboard.
Auto-blocks deploy unless overridden. Common failure: bad contrast on dynamic-color hero, missing FAQ on a service page.
Every Sentinel score writes a receipt with the test inputs + outputs + the binary hashes of the Lighthouse/aXe/Haiku runs. Anyone can re-run the same tests against the same site and compare.
# Re-verify any Sentinel score: $ npx @dcsplatform/sentinel-verify bafy…9f3c → Re-running Lighthouse on https://bella-cucina-v2.dcsai.app... → Re-running aXe contrast check... → Re-running completeness audit... → Calling Haiku for copy re-score... ✓ Composite re-verified: 87/100 (delta < 1.5) ✓ All axis scores within ±3 of recorded ✓ Receipt chain intact
Every build scored. Every score signed. Free with Platform.