Welcome to lesson one. We begin with a deceptively simple proposal: a supervisory optimization service wants to send STOP A H U seven to reduce electrical demand. The controller recognizes the command, the communication path is working, and the sequence may be technically capable of stopping the fan. Those facts establish capability. They do not establish permission to create the physical consequence. Imagine that the building has changed operating modes, or that the same air handler has acquired a smoke-control responsibility. The question is no longer merely, can the command be sent? The question is: does this proposed consequence have sufficient Admissible Evidence, Applicable Authority, and Established Standing to become reality now? TA14 treats the proposed action as a specific, bounded decision, not a general license for an optimizer to act. Its answer may be ALLOW, HOLD, DENY, or ESCALATE. A HOLD means the present basis is not yet sufficient; it is not a substitute for required life-safety behavior. Throughout this demonstration, existing fire and smoke-control systems, native interlocks, and competent site authority retain their responsibilities. The numbers and events shown are teaching assumptions, not actual building observations. As you move to lesson two, ask what we would have to know about AHU seven before any consequence could be considered.

Distinguish technical command validity from present execution eligibility.

Continue to lesson 02 and test the next governance boundary.

Lesson two begins at the first anchor: Reality. Before we trust a command proposal, we must establish what is physically true about the specific equipment it would affect. The illustration shows an air handler and operating signals. A fan-speed value, an enable point, or a dashboard's normal-operation label can be useful observations. But none of those signals alone proves the full operating context. Is AHU seven serving ordinary ventilation? Is it assigned to a smoke-control sequence? Has a fire-alarm or building mode transition occurred? Does the asset identifier actually correspond to the intended physical unit? We must distinguish what the system observed from what someone inferred. A point value is not the entire physical reality. The relevant evidence sources may include controller feedback, authoritative fire and smoke status, the verified asset relationship, and the governing sequence of operations. The example does not specify which sources are authoritative for every installation; that must be established by the competent designer and site operators. TA14 does not measure the building by itself. It evaluates whether the available, identified observations sufficiently support a proposed consequence. If the current reality cannot be established, an earlier optimization recommendation does not become permission through repetition. The next lesson asks whether our observations have become trustworthy records.

Identify the specific real-world facts required before assessing a command.

Continue to lesson 03 and test the next governance boundary.

Lesson three is about the difference between seeing a value and possessing a record that can support a consequential determination. A trend chart might say that the fan was running at a particular time. A controller log might identify the command source. An asset register might associate the point with AHU seven. A fire and smoke-control record might identify a changed operating role. Each item answers a different question. To evaluate them together, preserve the source, the observation timestamp, the receiving timestamp where relevant, the equipment identity, the measurement or state semantics, and any known clock uncertainty. Preserve raw observations rather than silently overwriting them with a cleaned or adjusted interpretation. If two authoritative sources disagree, record the conflict; do not choose the convenient answer because it favors the proposed shutdown. BACnet and building automation systems already provide valuable command priorities, source information, timestamps, histories, and alarms where implemented. TA14 must give those native mechanisms full credit. Its candidate role is not to invent logging, but to establish whether the collected record is sufficient for this exact physical consequence. A dashboard that looks complete may still lack decisive evidence. In lesson four, we will see why even a well-supported record can become insufficient when time and conditions change.

Separate available data from records fit to support an exact consequential proposition.

Continue to lesson 04 and test the next governance boundary.

Lesson four examines Continuity. At time T zero, suppose the proposed demand-response shutdown appears supportable. The equipment is serving ordinary ventilation, the relevant evidence is current, and an authorized optimization service is acting within its normal scope. Now suppose that at time T one, before the command is committed, AHU seven becomes part of an active smoke-control path. The original facts no longer describe the same consequential situation. A prior ALLOW candidate cannot be carried forward as permanent permission. The material change breaks the continuity of the evidence and authority basis, and the proposed optimization shutdown must be revalidated or placed on HOLD. But be precise about the timing boundary. If the change becomes observable before final validation, TA14 must account for it. If physical state changes after the final admissible observation and before actuation, software cannot truthfully claim it observed the unobserved event. That residual race must be handled by the native control and life-safety mechanisms required for the installation. Freshness windows, clock tolerances, and the maximum validation-to-write interval must be defined for the actual system, not invented from a generic slide. This lesson does not prove zero latency or perfect atomicity. It teaches why permission is bounded in time. Next, we ask whether the evidence actually proves the proposition needed for this action.

Explain why material changes break continuity, and where native safety must govern.

Continue to lesson 05 and test the next governance boundary.

Lesson five introduces Admissibility. Having accurate data is not the same as having enough evidence to justify the exact proposed consequence. Imagine a reliable energy model predicts savings from stopping AHU seven. The prediction may be correct about demand. It still may not establish that shutdown is acceptable under the building's present operating requirements. Likewise, a fan-speed reading may prove that the fan is operating, but not that the fan may safely or lawfully be stopped. TA14 asks which proposition each record supports, which critical proposition remains unproven, and whether the required evidence is current and tied to the correct equipment and action. The evidence must be evaluated against STOP A H U seven, not against a vague objective such as efficiency. The example also requires us to acknowledge existing controls: sequences of operation, BACnet priority mechanisms, alarms, and functional tests may already establish important portions of the decision. Those are not TA14 inventions. What remains under examination is whether a cross-system, consequence-bound record can establish the sufficiency of present evidence alongside authority and standing. When a required fact is missing, we do not turn absence into permission. Next we move from the evidence itself to the actor proposing to act.

Test evidence against the precise action rather than general system relevance.

Continue to lesson 06 and test the next governance boundary.

Lesson six separates three questions that are often collapsed. First, who is the actor? Authentication may establish that a command originated from a known optimization service or identified operator. Second, what is the Applicable Authority? That concerns the valid rule, delegation, policy, or operating scope permitting a class of action. Third, does the actor possess Established Standing for this particular asset, capacity, condition, and moment? An authenticated optimization service might be permitted to adjust ordinary ventilation for energy management while lacking standing to stop an air handler serving a life-safety function. Identity is not unlimited authority, and general authority is not necessarily current standing. In TA14's Standing Architecture, examine the actor, capacity, standing basis, and authority relationship. Preserve the supporting source and any limits or expiry. Do not merely display an authorized flag without showing what it authorizes and for whom. This example is an architectural teaching case, not a legal or regulatory determination for a real building. It also remains open to technical challenge: standing must demonstrate a function beyond existing scope and contextual authorization mechanisms, or its distinctness is not established. Lesson seven brings the evidence, authority, standing, and exact action together at the final commit boundary.

Distinguish Applicable Authority from Established Standing.

Continue to lesson 07 and test the next governance boundary.

Lesson seven is Commit: the final governed decision boundary before a proposed physical action is dispatched. Here the system must bind the decision to the exact consequence, STOP A H U seven, the identified equipment, the current supporting evidence, the actor, the applicable authority, and the established standing. The earlier candidate decision is not sufficient merely because it was once valid. The system must evaluate the frozen material-change predicates, evidence freshness, bounded clock uncertainty, and the maximum permitted interval between final validation and command dispatch. If required evidence is stale, continuity is broken, or authority cannot be established, the earlier candidate cannot silently advance. Depending on the site-specific failure policy, the determination may be HOLD, DENY, or ESCALATE. Those words must not be interpreted as permission to interfere with a required emergency or smoke-control response. Native interlocks, safety sequences, and competent physical-control authority remain responsible for the final safety behavior. The existing R seven through R nine examination goes further: it defines an executable contract, identifies the residual observation-to-actuation race, and runs illustrative timing simulations. Those simulations establish internal logic only. They are not hardware validation or ASHRAE certification. The next lesson follows the command beyond the gate to determine what actually happened.

Describe a governed commit without claiming zero-latency sensing or replacing equipment interlocks.

Continue to lesson 08 and test the next governance boundary.

Lesson eight is Outcome, and it closes the bounded chain. A command being issued does not mean the controller accepted it. Controller acknowledgement does not mean the actuator changed state. And a reported state change does not necessarily establish the complete physical consequence. In this hypothetical illustration, the system depicts a successful stop. Treat that as an example, not evidence from an actual AHU. In a real examination, preserve the decision and dispatch record, controller acknowledgement or rejection, authoritative fan and equipment feedback, observation times, and any discrepancy between expected and observed behavior. If a native smoke-control interlock overrides the proposed stop, preserve that as the outcome rather than labeling the governance system successful because a command was sent. If the result cannot be established, record it as unresolved. The full TA14 chain is Reality, Record, Continuity, Admissibility, Binding, Commit, Execution, and Outcome. Outcome becomes part of the reality that must be examined for the next proposed consequence. An earlier ALLOW does not renew itself. The technical examination below these lessons deliberately challenges whether native HVAC controls and other pre-execution authorization architectures already provide equivalent functions. TA14's distinct contribution remains a bounded hypothesis requiring comparison and measured hardware evidence. The governing question remains: does this proposed consequence have sufficient Admissible Evidence, Applicable Authority, and Established Standing to become reality now?

Differentiate command acceptance from independently verified physical outcome.

Continue into the R1-R9 technical challenge and empirical-test requirements below.