Front-end delivery standard
66 rules across six dimensions, in two lists: one to build against, one to pass before production.
Both lists below are generated from a single set of rules, so they cannot drift apart. Every rule has a stable id, a build instruction, and an acceptance test that says how it is proved. A rule that fails at the gate points straight back at the instruction that would have prevented it.
Build checklist
Follow while building. Ordered the way the work happens, not by category.
Production gate
Verify before go-live. Ordered by how each item is checked.
How this runs
What a review needs, turnaround, the three verdicts, and waivers.
What is in it
66 rules - 21 blocker, 40 required, 5 recommended.
Severity
- blocker
- Stops a release. No negotiation at review time.
- required
- Stops a release unless it is waived in writing, with a reason.
- recommended
- Reported, never blocks.
This page follows its own rules
The filters on the two checklists write their state into the address bar and restore it on load, because that is what this standard asks of every listing. So any filtered view is a link. Filter down to what you want to talk about and send the URL back, or use the comment link on an individual rule and it will arrive already carrying its id.
It is deliberately not indexed, and it is the one place where the rule about indexability is inverted on purpose.