Building BIOS Architecture

Building Definition Language, or BDL, shall provide the formal declarative language through which the intended structure, composition, Interfaces, capabilities, dependencies, Profiles, and constraints of a System05 building are described.

BDL represents what the building is intended to be. Building BIOS represents what is installed, verified, configured, and currently authorized.

The BDL model may define:

building identity and use;

spatial hierarchy;

structural topology;

required component Types;

Node and Interface relationships;

Cartridge locations;

required capabilities;

utility topology;

dependency requirements;

Engineering Profiles;

safety constraints;

permitted substitutions;

commissioning requirements;

future-reserved Interfaces.

The BIOS shall not execute unvalidated BDL source directly. BDL shall pass through the Engineering Compiler and produce a signed, validated configuration package.

The BIOS shall maintain traceability between:

BDL element identity;

compiled configuration object;

physical Component or Cartridge Instance;

Interface Instance;

commissioning evidence;

current Digital Twin object.

The BIOS shall report deviations from the compiled BDL intent, including:

missing component;

substituted type;

changed location;

incompatible Interface;

insufficient capability;

additional unplanned component;

modified dependency;

changed Engineering Profile.

Field changes shall not rewrite the original BDL silently. They shall create a proposed model revision or a documented As-Built deviation.

BDL schema versions and BIOS-supported configuration schema versions shall be explicitly mapped.