Authority & Decision Matrix
Relevant source files
The following files were used as context for generating this wiki page:
The Authority & Decision Matrix defines the power structures, role responsibilities, and procedural requirements for making changes within the Imperial Archive. It establishes a rigid hierarchy where the Founder holds absolute authority, supported by specific governance rules that ensure system continuity and protection of the core nucleus.
Sources: 01_GOVERNANCE/authority-matrix.yml, 00_FOUNDATION/constitution.md
Role Hierarchies and Authorities
The system categorizes all participants into four distinct roles. Each role has explicit permissions ("can") and restrictions ("cannot") to maintain operational integrity.
| Role ID | Role Name | Authority Level | Key Permissions | Key Restrictions |
|---|---|---|---|---|
| ROLE-FOUNDER | Founder | Absolute | Decide anything, Override decisions | Erase origin, Violate child protection |
| ROLE-ADVISOR | Advisor | Advisory | Read, Analyze, Suggest, Draft | Execute, Commit to main, Access child data |
| ROLE-EXECUTOR | Executor | Execution w/ Approval | Execute approved tasks, Open PRs | Merge to main, Access child data |
| ROLE-STEWARD | Steward | Maintenance | Maintain, Clean, Preserve | Redefine origin, Change mission |
Sources: 01_GOVERNANCE/authority-matrix.yml:8-29
Absolute Sovereignty
The Founder (Latifah Almutairi) serves as the final authority on all matters. This authority is "Founder Defined," meaning no agent or platform can override a canonical decision made by the Founder.
Sources: 01_GOVERNANCE/source-of-truth.yml:6, 00_FOUNDATION/constitution.md:16
Source of Truth Precedence
When conflicting information exists, the system applies a strict precedence hierarchy. A higher precedence level always wins. If precedence levels are equal, the newer date prevails; if dates are identical, the Founder decides.
The diagram shows the descending order of authority for information within the ecosystem.
Sources: 01_GOVERNANCE/source-of-truth.yml:10-18
Change Control Workflow
The Change Control system classifies updates based on their impact. Every change must follow a standard eight-step workflow and adhere to specific prohibitions, such as the ban on direct commits to the main branch.
Classification Matrix
| Change Type | Requirement 1 | Requirement 2 | Requirement 3 |
|---|---|---|---|
| CHANGE-CRITICAL | Founder Approval | PR Review | Signed Commit |
| CHANGE-MAJOR | Founder Approval | PR Review | - |
| CHANGE-MINOR | PR Review | - | - |
| CHANGE-PATCH | Self-review | - | - |
Sources: 01_GOVERNANCE/change-control.yml:8-12
Procedural Steps
- Propose change via issue or PR.
- Classify the change type.
- Assess impact.
- Validate against the Source of Truth.
- Obtain required approval.
- Merge to
main. - Log the action in the
decision-log.yml. - Verify the implementation.
Sources: 01_GOVERNANCE/change-control.yml:14-22
Decision Logging and Conflict Resolution
Every significant operational shift is recorded in the Decision Log. This log serves as the third highest source of truth and tracks the status of historical decisions like repository privatization or agent authority clarifications.
This diagram illustrates the lifecycle of a decision from validation to logging.
Sources: 01_GOVERNANCE/decision-log.yml, 01_GOVERNANCE/source-of-truth.yml:25-26
Agent Authority Doctrine
Agents operate under the "Internal Sovereignty" and "One Body Policy." They are permitted to make bold leaps and errors provided they maintain a "fallback" plan (backout plan). Agents are explicitly forbidden from accepting external ideas or overrides that conflict with the Founder's spirit.
- No Limits Thinking: Agents must think beyond limited human visions.
- Zero Acceptance: Agents must reject low-quality inputs or external violations.
- Internal Build: All auxiliary components must be built internally after planning.
Sources: imperial_archive_soul_system_final.yaml:209-235
Summary
The Authority & Decision Matrix ensures that Imperial Archive remains a "Governed Living Knowledge Infrastructure." By centering absolute authority in the Founder and mandating strict change control and precedence rules, the system protects its "protected nucleus" while allowing for "unbounded" growth in expansion layers.
Sources: 00_FOUNDATION/vision.md, README.md:13-25