Section 18 of 101
17. Configuration Engine
Stable section ID: S05-CON-006-SECTION-18 · 37 content blocks
The Configuration Engine maintains, validates, compares, and changes the authoritative building configuration.
It shall manage four distinct configuration views:
Declared Configuration: information supplied by manufacturers, designers, or registered components;
Approved Configuration: configuration formally authorized for the building;
Observed Configuration: configuration detected or verified in the physical building;
- Requested Configuration: proposed future change awaiting validation or implementation.
- The Engine shall prevent these views from being silently merged.
A configuration object shall identify:
object identity;
object type and version;
location;
interfaces;
relationships;
capabilities;
dependencies;
selected Profiles;
permissions;
approved limits;
evidence;
effective date;
authorizing authority.
A configuration change shall follow:
submission;
identity and authority check;
schema validation;
compatibility validation;
dependency analysis;
policy evaluation;
safety and Engineering Profile validation;
impact assessment;
approval;
transactional application;
physical verification where required;
baseline update;
- event recording.
- Rejected changes shall include a machine-readable and human-readable explanation.
The Configuration Engine shall support rollback only when the previous physical and digital conditions remain achievable and safe. A digital rollback shall not falsely represent reversal of an irreversible physical change.