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.
5 rules match. Clear filters
- STR-018 Separate reusable topics IF a unit has one subject, independent value, and repeated reuse, THEN make it a standalone topic with links ELSE keep it in context. Heuristic
- TEC-001 Choose an information type IF a technical topic is being created, THEN classify it as concept, task, reference, troubleshooting, glossary, or mixed with explicit boundaries ELSE do not draft a generic blob. Hard constraint
- TEC-004 Reference supports lookup IF the reader needs facts about an entity or interface, THEN use stable repeated fields, valid values, defaults, constraints, examples, and links ELSE select another type. Context default
- TEC-014 API reference exposes contract IF an endpoint, function, event, or schema is documented, THEN specify inputs, types, requiredness, constraints, outputs, errors, examples, and version ELSE mark incomplete. Hard constraint
- TEC-019 Reuse single-source facts IF the same volatile fact appears in multiple documents, THEN centralize it or generate references from one source ELSE retain independent stable statements. Heuristic