Section 38 of 101
37. Configuration Validation
Stable section ID: S05-CON-006-SECTION-38 · 34 content blocks
Configuration Validation determines whether the reconstructed building configuration is complete, internally consistent, permitted, and suitable for the intended operating mode.
Validation shall include:
schema validity;
identity uniqueness;
version consistency;
Interface compatibility;
capability sufficiency;
complete required dependencies;
topology consistency;
spatial consistency;
Engineering Profile compliance;
authorization validity;
certification status;
required inspection status;
unresolved fault status;
safety-system availability;
configuration-signature integrity.
Validation rules shall identify whether a violation is:
informational;
warning;
operational restriction;
activation blocker;
emergency condition.
A missing optional Cartridge may generate a warning. A missing required structural, electrical-protection, fire-safety, or emergency dependency shall block the affected operating mode.
The BIOS shall validate both the complete building and relevant subgraphs. A fault in one isolated zone should not unnecessarily prevent safe operation of independent zones.
The validation report shall identify:
rule violated;
affected entities;
configuration version;
evidence evaluated;
operational consequence;
required corrective action;
responsible authority.
Configuration shall not become authoritative merely because it is syntactically valid. Physical verification and engineering approval shall be required where applicable.