Document Control

Purpose

This procedure sets the requirements for controlling documents in the Rygen AI Management System.

Scope

This procedure applies to all AIMS documents, including policies, procedures, records, and forms. The identification and formatting rules below apply to the AIMS Handbook, which holds the policies, procedures, and processes. Other records, such as risk assessments and meeting minutes, must be identifiable and controlled but may follow tooling-specific formats.

Document Control Requirements

Document Identification and Formatting

Every AIMS Handbook document shall be a markdown (.md) file with the following.

Front Matter

Each document must begin with a YAML front matter block containing at least these fields:

  • id: A unique identifier matching the filename convention (e.g., AI-006).
  • version: The document version number (e.g., 1.0, 1.1).
  • visibility: The document’s classification (e.g., Public, Internal, Confidential).
  • owner: The person or role responsible for the document.
  • next_review_date: The date by which the next periodic review must be completed.

Filename Convention

AIMS Handbook documents must follow a standardized filename format: [ID]-[document-slug].md.

  • ID Format: AI-XXX, where AI is the prefix for AIMS documents and XXX is a unique, zero-padded three-digit number (e.g., AI-001). A companion document adds a numbered suffix to its parent’s ID (e.g., AI-020.1).
  • A blank form that a procedure links to, such as the AI Tool Request Form, is part of that procedure and carries no ID or front matter of its own.
  • Example: AI-006-document-control-procedure.md

Storage and Access

The AIMS Handbook is maintained in the “AIMS Handbook” GitLab repository.

  • Access: All employees have read access. GitLab project roles control write and merge access; document approval follows Review and Approval below.
  • Backup: GitLab keeps the version history and backups.
  • External documents: documents of external origin that the AIMS relies on, such as AI provider terms and SOC 2 reports, are kept in Sprinto with their source and date.

Version Control and Change Management

Version control is managed in GitLab. Changes to the AIMS Handbook follow these rules.

Minor Changes (e.g., typo fixes, clarifications): Increment the version number by a minor step (e.g., 1.0 to 1.1). The document owner approves them, except where Review and Approval names the CTO.

Major Changes (e.g., process overhauls, scope changes): Increment the version number by a major step (e.g., 1.1 to 2.0). The CTO approves them (Review and Approval).

Revision History: All changes, regardless of size, must be documented in the document’s “Revision History” table. The entry must include the new version number, the author of the change, the date, and a brief note summarizing the nature of the update.

Compliance Verification for Operational Documents

Operational governance documents, such as impact assessments, risk assessments, system specifications, and monitoring plans, must meet the requirements of their source procedures, such as AI-009 and AI-008. Unlike handbook documents, each has required fields and content set by its source procedure. They describe governance matters, such as what a system does, its data, impacts, risks, controls and requirements, and leave out implementation details such as file, class, function and configuration names; a control may name where it is built, as evidence.

Verification Requirements

When creating or revising an operational governance document, the document owner must verify that it meets every requirement of its source procedure:

  1. New documents: use the approved template from /content/templates/ and complete all required fields. Do not remove or skip fields the source procedure requires.
  2. Major revisions (version X.0): before submitting for review, verify that the revision does not remove required content, using the Review Checklists page for the document type.
  3. Minor revisions (version X.Y): verify that clarifications or corrections do not remove required content, using the Review Checklists page for the document type.

Compliance Checklists

Each document type listed in data/document_types.yaml in the governance repository has its required sections there and its reviewer checks on the Review Checklists page (content/templates/review-checklists.md). Owners use both when creating and revising documents.

Automated Validation

The governance repository holds validation scripts, utilities/validate_document.py and utilities/check_register.py, that check that system documents, corrective action reports and templates have the required sections listed in data/document_types.yaml and that risk records cite existing controls and treatments. Automated validation supplements manual compliance verification; it does not replace it.

Review and Approval

The CTO approves every new handbook document; every revision of a policy and of AI-002, AI-003, AI-004, AI-005 and AI-019; every major revision of other handbook documents; and any revision that changes an approval authority. The document owner approves minor revisions of all other handbook documents. Documents produced while operating the AIMS, such as specifications and assessments, are approved by the authority their source procedure names (AI-008, AI-013), or by the document owner where the procedure names none.

Periodic Reviews

Document owners review their documents by the next review date, using a GitLab merge request (MR).

If changes are required, the owner opens an MR with the updates and summarizes them in the Revision History table. The approved and merged MR is the formal approval record.

If no changes are required, the owner must still open an MR that only updates next_review_date in the front matter. The MR description must state that the periodic review was completed and no substantive changes were needed. The approved and merged MR is the record of the review.

3.5 Resource Documentation

Resources used in the AIMS are documented under ISO 42001 controls A.4.2 to A.4.6. AI-013 documents the typical resources for each lifecycle phase. Each AI System Design Specification documents the resources that system uses. When resources change, the documents AI-013 (Resource Change Management) names are updated through Version Control and Change Management above.

Distribution and Communication

All current, approved documents are on the main branch of the GitLab repository. The AIMS Handbook is published publicly through GitLab Pages.

Updates are communicated as AI-007 sets out.

Retention

  • Policies and procedures: the current and previous versions
  • Assessments: at least 3 years
  • Audit records: at least 3 years
  • Training records: duration of employment plus 3 years
  • Incident records: at least 3 years
  • A document removed from the repository is kept in its GitLab version history for the period above for its type.

Responsibilities

  • Principal AI Engineer: maintains the AIMS document control system and, as owner, approves minor revisions of the handbook documents they own, other than those Review and Approval assigns to the CTO.
  • CTO: approves the handbook documents and revisions that Review and Approval assigns to the CTO.
  • Document owners: keep their documents accurate and reviewed on schedule.
  • All staff: use the current, approved versions of documents in the GitLab repository.

Integration with Existing Systems

This procedure adds AIMS requirements to Rygen’s existing document control. Where it is silent, follow standard company document management practices.

Revision History

VersionDateAuthorSummary of Change
1.02025-06-05Field BradleyInitial draft.
1.12025-09-02Field BradleyMigrated to markdown and gitlab
1.22025-11-12Field BradleyUpdated review process to use GitLab Merge Requests and clarified version control and change management process
1.32026-01-14Field BradleyAdded Resource Change Management section (3.5) per ISO 42001 A.4.2-A.4.6
1.42026-01-20Hank GalbraithAdded compliance verification requirements for operational governance documents, including checklists and pre-commit validation (CAR-006)
2.02026-11-09Field BradleyShortened the procedure and set front matter, approval authorities, record locations and checklist references, with the CTO approving revisions that change an approval authority (AI-2173, AI-2131). Describes the governance validation scripts as they run, without a commit gate. GitLab project roles control write and merge access.