7. Governance Controls

Governance controls define the execution‑side mechanisms that ensure chkpt applies certified workflows predictably and consistently. These controls prevent drift, enforce version alignment, and maintain the integrity of the execution environment. chkpt does not govern or certify workflows; it provides the execution guarantees required for institutions to rely on certified workflow versions while preserving the strict separation between governance and execution.

7.1 Execution‑Side Governance

Execution‑side governance refers to the controls chkpt enforces during execution. These controls ensure that execution behaviour remains aligned with the certified workflow version and that evidence obligations are fulfilled. Execution‑side governance is distinct from workflow governance, which is defined externally. This distinction is foundational to the chkpt architecture and is introduced in the Workflow Certification Context.

7.2 Version Alignment

chkpt must ensure that each execution is bound to the correct workflow version and that the execution version used is recorded in the evidence. Version alignment prevents unauthorised variation and ensures that institutional reviewers can understand the behavioural context of the execution. Versioning rules are defined in Versioning.

7.3 Change Control

Changes to workflow versions or execution versions must be controlled by the adopting organisation. chkpt requires that workflow versions be explicitly selected and that execution versions be stable for the duration of an Application. Any change that occurs during execution constitutes a failure condition. Change control supports determinism as defined in the Execution Model.

7.4 Execution Environment Requirements

The execution environment must be stable, predictable, and free from external influences that could alter execution behaviour. chkpt requires that the environment provide consistent behaviour across executions and that any environmental dependencies be controlled by the adopting organisation. Environmental stability is essential for maintaining deterministic execution and preventing drift.

7.5 Drift Prevention

Drift occurs when execution diverges from the authorised workflow version. chkpt prevents drift by enforcing admissible behaviour boundaries, validating intermediate states, and ensuring that execution behaviour matches the workflow’s defined structure. Drift prevention is essential for maintaining institutional trust in deterministic execution and is supported by the behavioural rules defined in the Execution Model.

7.6 Institutional Responsibilities

Institutions are responsible for defining workflow governance, certifying workflow versions, and ensuring that chkpt is provided with authentic and authorised workflow definitions. Institutions must also ensure that evidence is retained according to their regulatory and operational requirements. chkpt provides the execution guarantees; institutions provide the governance framework. This separation ensures clarity, accountability, and long‑term institutional alignment.