# Symposium-2026 Design Loop — Verifier Rules These 9 rules are enforced by `mcp__codex-cli__review` (GPT-5.5) on every surface before wave completion. A surface may not advance past the verifier loop until all applicable rules return PASS. Opus may not self-review as the verifier. --- ## 1. No feature overclaim Do not claim a feature that is not shipped and verified in the Laravel repo. A claim is anything that a prospect, advisor, or evaluator would reasonably interpret as a live product capability — a CTA, a status label, a confirmed output, or a workflow step stated without a caveat. The Laravel verifier (`php artisan verify`) and the test suite are the authoritative record of what is shipped. If a feature is partially shipped, the surface must reflect that honestly (for example, by showing a "verification pending" badge or a scoped description of what is actually live). - **FAIL:** A surface for `p5-proposal-generation` shows a "Generate in 30 seconds" call-out even though the proposal generation job has no verifier pass for that SLA. - **PASS:** The same surface shows "Proposal draft queued" with a link to the builder, matching the verified `POST /proposals/{id}/generate` behavior recorded in the verifier output. --- ## 2. Brand token purity All color and font values in the surface's HTML and CSS must come exclusively from `_brand.css` custom properties (e.g. `var(--color-accent)`, `var(--font-family-primary)`). No raw hex codes, RGB values, named CSS colors, or font-name strings may appear in inline styles, `