The rules
Every rule, and how hard it binds
228 base rules across 14 domains and 9 structural layers. Filter them, then open one to see its condition tree, both branches, its exceptions and its sources.
34 rules match. Showing 26–34. Clear filters
- VOI-012 Avoid institutional self-centering IF WE/OUR language displaces the reader’s need or action, THEN rewrite around the reader or subject ELSE retain clear author responsibility. Heuristic
- TEC-006 Imperative starts the step IF the reader performs a procedural action, THEN start with a specific imperative verb and name the object ELSE name the actual actor. Context default
- TEC-011 UI verb works across input methods IF an instruction refers to a generic interface action, THEN prefer input-neutral verbs such as SELECT, OPEN, ENTER, or CHOOSE; use CLICK only for mouse-specific action ELSE retain. Context default
- TEC-012 Interface labels match exactly IF documentation names a visible label, command, field, endpoint, or code identifier, THEN match its current spelling and capitalization exactly ELSE flag version mismatch. Hard constraint
- TEC-017 Terms and examples globalize safely IF content will be translated or read globally, THEN avoid culture-bound idioms, ambiguous dates, concatenated fragments, and unstable synonyms ELSE retain. Context default
- ACC-004 Separate each instruction IF multiple actions appear in one block and can be completed separately, THEN make each a separate step ELSE retain a single compound action. Context default
- ACC-010 Error message states problem and recovery IF an error message appears, THEN state what happened, what remains safe or changed, and the next corrective action in non-blaming language ELSE retain. Hard constraint
- ACC-011 Respect user dignity IF language stereotypes, infantilizes, blames, or defines people solely by a condition without contextual reason, THEN replace it with accurate respectful language ELSE retain self-identified terms. Hard constraint
- ETH-011 No discriminatory default IF examples, labels, or rules assign capability, risk, role, or worth by protected or irrelevant identity, THEN remove the inference and audit downstream rules ELSE retain identity only when relevant and responsibly handled. Hard constraint