The ups and downs of automated code checking software

A sliding door needing to be operable &quot;without special knowledge&quot; is interesting. Imagine if that code were expanded with &quot;or uses latches and handles certified according to XYZ 123.&quot; Then someone can certify latches and handles (with installation instructions of course, like don&#x27;t install them sideways). The building model would simply specify the make and model of latches and handles to be used, or if it&#x27;s a simpler building maybe the model would only say &quot;XYZ 123 compliant latches and handles.&quot;<p>This would decouple the complex English language from the need to know whether a door is compliant. Because it can be reasonably understood that a door will be operable without special knowledge if its latches and handles can be. Doors are often custom fabricated, but latches and handles rarely are. And a final check against idiocy can still be performed after construction, as it should be today.

&gt; the same building, under the same code provisions, had 0 violations of egress provisions in one jurisdiction, and 16 violations in another jurisdiction. Multiply this variation times the 20,000 permitting jurisdictions<p>There are lots of inefficiency here. Are there any effort to harmonize the code? Building code, fire code, tax code...

For anyone reading the comments first: this is about building codes (i.e. literal physical buildings), not software verification.