Section 25 of 102
24. Constraints and Assertions
Stable section ID: S05-CON-007-SECTION-25 · 41 content blocks
Constraints define conditions that a valid BDL configuration shall satisfy.
Constraint classes shall include:
require;
prohibit;
limit;
prefer;
warn;
assert.
Examples:
require @Node_N01.capacity.axial
>= @Node_N01.demand.axial;
- prohibit connect(
- @PotableWaterInterface,
- @WastewaterInterface
);
limit @KitchenCartridge.power
<= @Circuit_12.available_power;
prefer @ExteriorWall.thermal_resistance
>= 4.0 m2*K/W;
Every Constraint shall define:
Constraint ID;
source authority;
applicable scope;
severity;
evaluation stage;
condition;
failure message;
permitted exception;
evidence requirement.
An assertion states a condition claimed to be true:
assert @EndCartridge_EC01.locked
evidence @Inspection_Record_021;
Assertions without sufficient evidence shall not be promoted automatically to verified status.
Constraint results shall include:
passed;
failed;
warning;
indeterminate;
not applicable;
- deferred.
- A deferred safety-critical Constraint shall block the configuration stage at which resolution is required.