Validation rules

Every rule below carries one sentence saying what fires it. The table is generated directly from VALIDATION_RULES, sentence included, so a rule cannot enter the validator without an explanation. Counts are never typed into this page.

How to read a row

error means the file is not a valid model and validate() returns ok: false. warning never blocks — it identifies a fallback or unsupported authoring combination without calling the building impossible. The class says why the project is entitled to check it at all:

Errors in the first three classes block. The retained warnings do not. That split is the design: the validator is willing to be certain about geometry and about the model's own declarations, and never treats a code figure from one jurisdiction as a verdict everywhere.

What is not here is as deliberate as what is. How many views a model authors, which accent colour it nominates, whether a bathroom looks too big for its fixtures — those had rules once, and they are gone. A rule with no hard architectural constraint behind it is taste wearing a diagnostic's clothes.

Next