Section 66 of 102
65. Canonical Operational State
Stable section ID: S05-CON-010-SECTION-66 · 29 content blocks
System05 shall maintain a Canonical Operational State through which authorized systems can obtain a consistent interpretation of the building’s current operational condition.
The Canonical Operational State may combine:
- Approved configuration from the Building BIOS.
- Observed physical state from the Digital Twin.
- Current equipment status.
- Active commands.
- Pending actions.
- Agent runtime states.
- Alarms and emergency conditions.
- Communication availability.
- Degraded capabilities.
- Temporary overrides.
- Unresolved configuration conflicts.
- Confidence and uncertainty.
- Applicable time and validity information.
Operational state shall distinguish among:
- Approved state.
- Desired state.
- Commanded state.
- Reported state.
- Observed state.
- Estimated state.
- Verified state.
- Predicted state.
- Unknown state.
- Conflicted state.
No single state label shall conceal a material disagreement between these categories. For example, a valve commanded closed but observed open shall be represented as a command–feedback conflict.
The Canonical Operational State shall be assembled through defined rules rather than informal AI interpretation alone. AI agents may assist with state estimation and conflict explanation, but the origin, confidence, and authority of each state element shall remain visible.
Systems consuming the Canonical Operational State shall be able to determine its timestamp, completeness, freshness, affected scope, and applicable limitations.