SIP-023 — Governance Evolution and Operational Execution

Go to Annex C: Requirements

The Reference Architecture SHALL separate the evolution of Governance Artifacts from execution of the operational processing flow.

Governance Artifacts may change while operational processing continues. Applying every change to an active processing flow immediately could alter outcomes without an explicit transition, invalidate comparisons, or prevent reproduction of earlier Interpretations.

Separating Artifact evolution from operational execution allows changes to be reviewed, approved, versioned, and activated through controlled lifecycle transitions. Each execution can remain associated with the exact Governance Artifact versions applicable to it.

The Submission satisfies this requirement when the Reference Architecture:

1. Defines Governance Artifact evolution separately from operational processing
2. Supports creation and review of a new Artifact version without automatically applying it to an active processing flow
3. Identifies the Authority responsible for approving an Artifact version
4. Defines how an approved version becomes applicable to an operational processing flow
5. Supports identification of an effective version, time, event, or Baseline
6. Associates each execution with the Governance Artifact versions applied to it
7. Prevents an Artifact revision from silently changing an active or completed execution
8. Supports concurrent use of different approved versions when permitted by applicable Governance
9. Preserves previous versions needed for Traceability and reproducible Interpretation
10. Records the transition from one applicable version or Baseline to another

This requirement defines logical and lifecycle separation. It does not require Governance activities and operational execution to use physically separate infrastructure.

SIP-019 — Data Plane and Control Plane Separation defines the related architectural separation between operational information flows and Governance or control flows.