A documented catalogue: for each rule id, a group, a title as a noun phrase, a one-line reason a builder cares, and the level it raises. Deliberately no numbers in the prose — thresholds live in the engine, and the finding's own message carries the live figure.
Also called: rules reference · what does it check · why does this warning exist
- 1The panel lists all rules grouped by area, marking which are currently tripped.
- 2assertRuleCatalogueComplete() is a guard: a rule id the engine pushes but the catalogue does not document throws, and so does a documented level that disagrees with the raised level.
- 3The standing test runs it against a spec built to trip as many rules as possible.
A builder about to send a drawing to a customer wants to know what was checked, not only what came back broken, and a screen showing current findings answers half of that. The catalogue lists every rule the design is tested against, what each one is asking, and where it stands right now. The thresholds are read from the checks themselves rather than written out again in prose, because a second copy of a number is a copy that drifts.
- A checker that only speaks when something is wrong.
- Rule text drifting from the thresholds it describes.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →