plenum-change-control

A Plenum HVAC control pull request requires passing CI gates, providing review evidence, and fulfilling validation rules based on change classification. Required checks vary depending on whether the modification targets thermostat logic, UI controls, configuration options, or engine safety components.

Changes to the Plenum smart HVAC repository are classified by target area, including temperature fields, API endpoints, configuration options, dependencies, UI changes, and safety-critical engine edits. Classification determines the specific testing expectations, unit conversion contracts, and review evidence required for merge.

Release procedures for Plenum API changes are required whenever modifications target endpoints, configuration options, or safety-critical engine logic. Following these procedures ensures CI validation, adherence to unit conversion contracts, and proper review evidence before deployment.

Yes, the Plenum change control workflow enforces unit conversion contracts for temperature fields. Modifications to thermostat logic or temperature handling must pass validation rules and CI gates that verify correct unit conversions before the pull request can be merged.

The best way to prepare a safe Plenum repository modification is to classify the change, identify required CI gates and testing expectations, and gather review evidence. This prevents risky or incomplete modifications to safety-critical HVAC engine logic, UI controls, and API endpoints.

Plenum configuration updates fail CI validation when they do not meet repository-specific quality and safety gates. Failures occur if changes lack required testing evidence, violate unit conversion contracts for temperature fields, or bypass the enforced validation workflow for API and engine safety edits.