Demonstration route · C4 operational consequence

Watch a building override move from HOLD to admissible execution.

A BAS operator intends to override a chilled-water valve from 35% to 100% after a complaint that a critical room is warming. The demonstration preserves the route from observed condition to verified outcome.

Demonstration only. TA-14 does not control a live BAS or issue a live command from this page. The scenario illustrates evidence, authority, binding, commitment, execution, release, and outcome verification.

Chilled-Water Valve Override

Critical Room 204 · AHU-2 · CHWV-204

DEMONSTRATION

Current room temperature78.6°F and rising

Current valve position35%

Requested override100%

OperatorAuthenticated BAS Operator

Consequence classC4 · Health / safety

Room temperature trendPRESENT

Valve position feedbackPRESENT

Supply-water temperaturePRESENT

Operator identityPRESENT

Override reasonMISSING

Override durationMISSING

Release conditionMISSING

Post-check windowMISSING

Route evaluation

Reality → Outcome

ALLOW · HOLD · DENY · ESCALATE

READY

The route is ready to evaluate. Missing route dependencies will be tested.

route: CHILLED_WATER_VALVE_OVERRIDE state: READY requested_value: 100% current_value: 35% live_command: false

Why HOLD occurred

Authentication alone was not enough. The route lacked a reason, duration, release condition, and post-check window. Without those objects, the proposed override was not execution-ready.

What correction changed

The correction added bounded duration, safe limits, automatic release, and an outcome check without replacing the original route history.

What the record preserves

The record shows the condition, evidence, authority, binding, exact commit, simulated command, release, outcome, unresolved limitations, and proof boundary.