Master Repository Structure
Relevant source files
The following files were used as context for generating this wiki page:
Imperial Archive organizes data into a hierarchical, governed knowledge infrastructure. The structure enforces cognitive continuity and protects core assets through a locked canonical nucleus. The repository serves as a private, authenticated ecosystem for long-term continuity and strategic communication.
Sources: README.md:3-6, 02_REPOSITORY/structure.yml:2-5
Core Directory Architecture
The repository uses a numbered folder system to separate foundational principles, governance rules, and active project implementations. Each directory serves a specific functional purpose within the "Infinite Living System."
System Folders and Purposes
| Folder | Purpose | Key Contents |
|---|---|---|
00_FOUNDATION | Origin and Vision | origin.md, vision.md, constitution.md |
01_GOVERNANCE | Governance and Rules | source-of-truth.yml, change-control.yml, decision-log.yml |
02_REPOSITORY | Domain and Definition | repository.yml, structure.yml, installation.yml |
03_SECURITY | Security Protocols | integrity.yml, domain-security.yml |
04_AGENTS | Agent Charters | AGENTS_CHARTER.md, agent-elimination-log.yml |
05_PROJECTS | Project Workspaces | tamara-learning-program, elias-home-room |
06_ARCHIVE | Recovery Maps | recovery-map.yml, website-recovery.yml |
99_TESTS | Validation Scripts | validate.sh |
Sources: 02_REPOSITORY/structure.yml:12-52, 00_FOUNDATION/README.md:5-8
Root Level Configuration
The root directory contains global metadata and lockdown records. These files define the high-level operational status of the repository.
README.md: Ecosystem overview and TSC system descriptions.LOCKDOWN_RECORD.md: History of system freezes.SECURITY.md: Security policies.
Sources: 02_REPOSITORY/structure.yml:7-12, README.md:1-2
Governance and Change Control
The repository structure is protected by a strict change control workflow. Governance files dictate how new information enters the system and how existing canonical data is modified.
Change Classification and Requirements
Changes are categorized by severity, with critical changes requiring the highest level of authorization.
- CHANGE-CRITICAL: Requires Founder approval, PR review, and a signed commit.
- CHANGE-MAJOR: Requires Founder approval and PR review.
- CHANGE-MINOR: Requires PR review.
- CHANGE-PATCH: Requires self-review.
Sources: 01_GOVERNANCE/change-control.yml:7-11
Data Flow for Modifications
This diagram illustrates the mandatory path for repository updates.
Project Workspace Structure
Active projects, such as the Tamara Learning Program, follow a sub-structure designed for immutable source preservation and additive versioning.
Standard Project Subfolders
Projects under 05_PROJECTS/ are organized into the following segments:
source-original/: Immutable source evidence and intake files.canonical/: Derived implementation and logic.assets/: Verified images, logos, and signatures.manifests/: Machine-readable project records and inventories.releases/: Versioned release candidates and locked production files.
Sources: projects/tamara-learning-program/source-original/README.md:14-20
Preservation Rules
Projects must adhere to strict data handling requirements to maintain integrity:
- Never overwrite release history.
- Preserve originals without modification.
- Add additive versions for daily patches and weekly packages.
- Keep identity, ownership, and seals locked.
Sources: projects/tamara-learning-program/source-original/README.md:6-12
TSC System Layers
The repository implements 9 professional Imperial Classes (TSC Systems). These classes represent the "YAML Law of Infinity," where each system contains a velvet_children: [] array for endless expansion without breaking the core nucleus.
Note: The TSC systems represent the professional governance and functional divisions of the archive.
Sources: README.md:12-22, README.md:31-33
Repository Metadata and Policy
The repository definition is locked in a canonical state to prevent unauthorized structural shifts.
| Field | Value |
|---|---|
| Name | Imperial-Archive |
| Owner | latifah6114-ux |
| Visibility | Private |
| Default Branch | main (Protected) |
| License | Proprietary |
| Languages | English, Arabic |
Sources: 02_REPOSITORY/repository.yml:7-16, 02_REPOSITORY/repository.yml:18-24
Summary
The Master Repository Structure facilitates a "Steel Spine, Velvet Soul" architecture. It prioritizes the preservation of the founding origin while allowing for infinite growth through the TSC Evolution layer. All structural changes are governed by the Founder's direct authority and a structured change control protocol, ensuring that human vision leads while technology serves.
Sources: 00_FOUNDATION/origin.md:27, 00_FOUNDATION/constitution.md:11-13