Building BIOS Architecture

Configuration Versioning preserves the complete sequence of approved building configurations.

Every configuration version shall have:

unique Version ID;

parent Version ID;

creation timestamp;

effective timestamp;

author;

approving authority;

change summary;

affected entities;

applicable Manifest version;

Profile versions;

software and firmware references;

evidence;

digital signature;

status.

Version status may include:

draft;

proposed;

under review;

approved;

active;

superseded;

rejected;

recovery candidate;

archived;

invalidated.

Configuration versioning shall support:

comparison between versions;

identification of added, removed, relocated, or modified entities;

identification of changed capabilities and dependencies;

restoration planning;

audit;

lifecycle analysis.

A configuration version shall not be activated partially unless the change was explicitly designed as a phased configuration with defined intermediate states.

Software version, Interface version, Cartridge version, Profile version, and whole-building Configuration Version shall remain distinct but linked.

Branching may be used for design alternatives, simulations, proposed renovation, or emergency planning. Only one configuration—or an explicitly defined coordinated set of zone configurations—shall hold authoritative Active status for the physical building.

Version numbers shall not be reused. Deleting or hiding an unsuccessful version shall not be permitted where it affected the physical building or approval process.