Governance Committee

Purpose

This document assigns and communicates the roles, responsibilities and authorities of Rygen Technologies’ AI Governance Committee under ISO/IEC 42001:2023 Clause 5.3.

Scope

This document applies to all members of the AI Governance Committee.

Committee Members and Assigned Roles

RoleResponsibilities
Chair (AIMS Owner)Leads AIMS implementation, leads the committee’s work in #ai-governance, chairs committee meetings when they are held, ensures ISO 42001 compliance, owns the internal audit program (AI-015), and reports on progress and compliance to the CTO.
Advisor (CTO)Provides strategic oversight, allocates resources, and supports executive alignment.
Director of Data ProductsLeads AI-related data governance, data pipelines, data products, and data infrastructure integration.
Operational Systems LeadEnsures AI deployment infrastructure, monitoring systems, and traceability mechanisms are operational.
Engineering Team LeadsSupport AIMS compliance, and take part in governance reviews, audits, and continual improvement.
Lead Product ManagersSupport AIMS compliance, the implementation of strategic objectives, system design, and improvement. May lead problem definitions, impact assessments and risk assessments with the AI Engineering Team (AI-005).

Meetings and Decisions

The committee holds no regular meetings. It works in the private #ai-governance Slack channel, following the channel protocol in AI-007 Annex A, and meets only as needed.

Governance decisions that need committee input are discussed in #ai-governance as DECISION threads, which link to the merge request. The deciding authority that the governing procedure names (AI-005 lists them) approves the GitLab merge request, which is the only record of approval. When the committee meets, the Chair keeps minutes.

Communication and Confirmation

Each member confirms they have reviewed and understood their role and responsibilities in the Acknowledgment Form in the AIMS Training Hub (AI-021 Section 4).

Revision History

VersionDateAuthorSummary of Change
1.02025-06-05Field BradleyInitial draft.
1.12025-09-02Field BradleyMigrated to markdown and gitlab
1.22026-11-04Field BradleyThe committee holds no regular meetings; it works in #ai-governance and meets as needed. Decisions are discussed in DECISION threads and approved only in GitLab merge requests, which are the record of approval (AI-2173)
1.32026-11-09Field BradleyCut repeated text with no change to roles; merge request authority follows the governing procedure, and the Chair owns the audit program without auditing their own work (AI-2173). DECISION threads are for decisions that need committee input. Members confirm their role in the AIMS Training Hub Acknowledgment Form.
1.42026-11-11Field BradleyLead Product Managers may lead problem definitions, impact assessments and risk assessments with the AI Engineering Team (AI-2205)