Section 19 of 101
18. State Engine
Stable section ID: S05-CON-006-SECTION-19 · 27 content blocks
The State Engine maintains the current state of BIOS services, components, Interfaces, Cartridges, building zones, and the building as a whole.
The State Engine shall distinguish among:
declared state;
commanded state;
observed state;
verified state;
inferred state;
desired state.
Each state record shall identify:
subject identity;
state type;
state value;
source;
timestamp;
confidence or verification level;
applicable configuration version;
expiration or validity conditions;
related event.
State transitions shall be governed by explicit rules. A component shall not enter Operational state directly from Disconnected state without completing the required intermediate states.
State conflicts shall be detected when:
different sources report incompatible conditions;
commanded state differs from physical feedback;
a component state conflicts with its Interface state;
a dependent system is active while its required service is unavailable;
the Digital Twin differs from verified physical configuration.
The Engine shall not resolve safety-relevant conflicts through arbitrary source priority. It shall apply the approved policy, restrict operation where necessary, and request verification.
Historical states shall remain available for diagnostics and lifecycle analysis.