The Change Control / Configuration Manager is the management owner of identity: what combination of model, training data, prompt, agent tools, feature store, code and infrastructure is the system Role 1.1 signed. Role 2.2 promotes. Role 15.1 gates release. Role 7.1 watches providers. This role baselines the bundle, classifies change, and forces Act when a change would alter intended purpose in fact.

Standing duties

• Define configuration items for AI systems as a bundle — model + data + prompt + tools + code + infra — not as a weights file alone.
• Baseline every high-risk system before placement and keep the live baseline identical to what Role 2.2 is serving.
• Classify change: maintenance versus substantial modification versus purpose change (ACT02) versus incident-driven change (ACT03).
• Refuse silent swaps: provider updates, prompt edits, feature-store shifts and agent-permission changes are changes.
• Do not treat a ticket, a Git tag or a model card as residual-risk acceptance or as a substitute for Role 15.1 go-live.

Accountable to: Head of AI Architecture / Role 15.1 (transition) / Role 13.1 (architecture)

Primary domain: Implement (configuration identity and change). Names what Operate is running. Does not Direct or accept residual risk.

Linked EN 18286 clauses: 8.7, 8.8, 9.1, 9.4

Format: 3 hours of training, EUR 200.