Change Control Protocol
Relevant source files
The following files were used as context for generating this wiki page:
The Change Control Protocol defines the mandatory procedures for modifying the Imperial Archive ecosystem. It ensures that all updates align with the Source of Truth and maintain the integrity of the "LOCKED_CANONICAL" status of foundational documents. This protocol applies to all repository branches, with specific protections enforced on the main branch to prevent unauthorized or silent changes.
Sources: 01_GOVERNANCE/change-control.yml:1-5, 02_REPOSITORY/repository.yml:13-18
Change Classification and Requirements
The system categorizes changes into four distinct types based on their impact and criticality. Each type carries specific validation and approval requirements that must be met before a change is merged.
| Change ID | Type | Requirements |
|---|---|---|
| CHANGE-CRITICAL | Critical | Founder approval, PR review, Signed commit |
| CHANGE-MAJOR | Major | Founder approval, PR review |
| CHANGE-MINOR | Minor | PR review |
| CHANGE-PATCH | Patch | Self-review |
Sources: 01_GOVERNANCE/change-control.yml:7-11
Approval Authority
The Authority Matrix defines who can authorize these changes. The Founder holds absolute authority and can override any decision, while Executors are limited to creating branches and opening PRs for approved tasks.
Sources: 01_GOVERNANCE/authority-matrix.yml:8-20
Operational Workflow
The change control process follows an eight-step linear workflow to ensure traceability and validation against the project's core principles.
The diagram illustrates the sequential steps required to move a proposal from initial submission to final verification.
Sources: 01_GOVERNANCE/change-control.yml:13-21
Installation Protocol
For technical file additions, the system follows an "Install drop by drop" rule. This limits batches to a maximum of 8 files and requires a 24-hour observation period following the merge.
Sources: 02_REPOSITORY/installation.yml:7-18
Source of Truth Validation
Every change must be validated against the Source of Truth (SoT). The SoT establishes a hierarchy of precedence to resolve conflicts during the change process.
- Founder Canonical Decision: Direct decisions by Latifah Almutairi.
- Canonical Repository Main: The state of the
mainbranch. - Verified Decision Log: Records of past executed changes.
- Approved System Config: Validated configuration files.
Sources: 01_GOVERNANCE/source-of-truth.yml:9-16
Conflict Resolution Rules
If a proposed change conflicts with existing data, the following rules apply:
- Higher precedence sources always win.
- If precedence is equal, the newer date wins.
- If dates are also equal, the Founder decides.
- Conflicts must be logged before they are resolved.
Sources: 01_GOVERNANCE/source-of-truth.yml:18-25
Repository Protections and Prohibitions
To maintain the "Steel Spine" of the archive, the repository enforces strict technical prohibitions. These rules prevent the bypass of the Change Control Protocol.
- No Direct Commits: Direct pushes to the
mainbranch are disabled. - No Force Pushes: Force pushing to
mainis strictly prohibited. - No Silent Changes: Every modification must be visible and logged.
- Signature Requirements: Critical changes require GPG-signed commits.
- Conventional Commits: All commits must follow the conventional format.
Sources: 01_GOVERNANCE/change-control.yml:23-28, 02_REPOSITORY/repository.yml:15-22
Decision Logging
Once a change is merged, it must be recorded in the decision-log.yml. This log serves as a historical record of the system's evolution and acts as a level 3 Source of Truth.
# Example of a logged change in decision-log.yml
decisions:
- { id: "DEC-2026-009",
date: "2026-10-10",
title: "Declare n8n Cloud + Tamara homework digest workflow (CHANGE-MINOR)",
status: "proposed" }
Sources: 01_GOVERNANCE/decision-log.yml:8-17
Summary
The Change Control Protocol acts as the primary safeguard for the Imperial Archive's integrity. By enforcing a structured workflow, clear authority levels, and strict repository protections, the system ensures that all growth is intentional, documented, and founder-approved. This protocol prevents the "silent decay" of governance and maintains the archive as a living, governed infrastructure.