Installation & Deployment Guide
Relevant source files
The following files were used as context for generating this wiki page:
This guide defines the foundational protocols for setting up and deploying components within the Imperial Archive ecosystem. It establishes the mandatory sequence for file intake, repository configuration, and external service integration.
The system operates under a core philosophy: "Install drop by drop, not in bulk" (التثبيت قطرة قطرة، لا دفعة واحدة). Every installation step prioritizes local archival and meticulous validation over rapid deployment to ensure the integrity of the protected cognitive nucleus.
Sources: 02_REPOSITORY/installation.yml:8-10, README.md:46-50
Installation Protocol
The Installation Protocol (IA-INSTALL-001) governs how all files and systems enter the repository. This mandatory eight-step sequence ensures that every asset is classified and tested before it reaches the canonical branch.
Mandatory Workflow Steps
- RECEIVE: Accept the file into the temporary staging area.
- CLASSIFY: Apply the appropriate class (e.g., GOVERNING_EDUCATIONAL_MASTER, ENGLISH_PORTAL_SOURCE).
- VALIDATE: Perform data integrity and structural checks.
- TEST: Verify functional behavior.
- COMMIT: Upload to a separate branch; direct pushes to
mainare strictly prohibited. - OBSERVE: Wait for the mandatory observation period (24 hours).
- MERGE: Integrate into the canonical branch after successful observation.
- LOG: Record the action in the
decision-log.
Sources: 02_REPOSITORY/installation.yml:12-21, 01_GOVERNANCE/change-control.yml:21-23
The diagram above summarizes the staged installation flow required for all new repository assets.
Sources: 02_REPOSITORY/installation.yml:12-21
Deployment Constraints
| Constraint | Value | Description |
|---|---|---|
| Max Files Per Batch | 8 | Limits the blast radius of new changes. |
| Observation Period | 24 Hours | Required time to monitor system health after a branch commit. |
| Protection Status | Protected | The main branch requires PRs, reviews, and GPG signatures. |
| Commit Format | Conventional | All commits must follow standard naming conventions. |
| Sources: 02_REPOSITORY/installation.yml:23-25, 02_REPOSITORY/repository.yml:18-25 |
Repository Setup and Governance
Deployment begins with the configuration of the private GitHub repository (latifah6114-ux/Imperial-Archive). This repository acts as the single source of truth for all cognitive and educational assets.
Infrastructure Configuration
The repository requires GPG signatures for all critical changes. Access control follows a strict authority matrix where the Founder holds absolute authority (ROLE-FOUNDER), and Executors (ROLE-EXECUTOR) handle technical tasks via approved pull requests.
Sources: 02_REPOSITORY/repository.yml:8-25, 01_GOVERNANCE/authority-matrix.yml:7-24
Connectivity Status
Before activating services, they must be declared and configured within the Connection Map.
| Connection ID | Name | Type | Status |
|---|---|---|---|
| CONN-GITHUB | GitHub | HOST | VERIFIED_LIVE |
| CONN-DOMAIN | imperialarchive.ai | DOMAIN | CONFIGURED |
| CONN-REPLIT | Replit | EXECUTION | ACTIVE |
| CONN-OPENAI | OpenAI | AI_PROVIDER | ACTIVE |
| CONN-N8N | n8n Cloud | AUTOMATION | DECLARED |
| Sources: 02_REPOSITORY/connection-map.yml:12-24 |
Domain and DNS Configuration
Deployment of web-facing components requires specific DNS configurations through Cloudflare and Epik.com. Security records must be staged to prevent email spoofing and ensure site integrity.
DNS Record Deployment
- Nameservers: Set Cloudflare zone-specific pairs at the registrar.
- CAA: Restrict certificate issuance to
letsencrypt.org. - DMARC Staging:
- Start with
p=nonefor monitoring. - Monitor for 30 days.
- Advance to
p=quarantine. - Finally, set
p=rejectonce DKIM is verified.
Sources: 02_REPOSITORY/domain-dns.yml:8-23
- Start with
The sequence diagram illustrates the phased rollout for DMARC security records required for the imperialarchive.ai domain.
Sources: 02_REPOSITORY/domain-dns.yml:16-21
Project Intake (Case Study: Tamara Learning Program)
Deploying a specific project like the Tamara Learning Program requires additional intake steps to ensure provenance and preservation.
Intake Workflow
- Inventory Check: Verify all required master files (e.g.,
IA_EDUCATIONAL_CHILD_LEARNING_SYSTEM_TAMARA_MASTER_v1.0.0.yaml) are present. - Identity Verification: Upload owner-approved signature assets (
IA-LATIFAH-SIGNATURE-001). - Local Archival: Fetch external HeyGen audio URLs and store them as local archival masters.
- Automation Deploy: Configure
n8nworkflows (e.g.,tamara-daily-homework-digest) but maintain "no child data" policies at the file level.
Sources: projects/tamara-learning-program/manifests/intake-inventory.yaml:12-63, projects/tamara-learning-program/README.md:27-32
Preservation Gaps
Projects remain in an INSTALLED_NOT_RELEASED status if the following gaps exist:
- Original source files are only in chat text and not committed to the repository.
- SHA256 hashes are not generated for identity assets.
- Missing curriculum sources (Mathematics, Science, Arabic).
Sources: projects/tamara-learning-program/reports/SOURCE_GAPS.md:7-30, projects/tamara-learning-program/manifests/intake-inventory.yaml:45-55
Change Control and Decision Logging
Any modification to the installed environment must follow the Change Control workflow.
Change Classification
- CHANGE-CRITICAL: Requires Founder approval, PR review, and signed commit.
- CHANGE-MAJOR: Requires Founder approval and PR review.
- CHANGE-MINOR: Requires PR review.
- CHANGE-PATCH: Requires self-review only.
Sources: 01_GOVERNANCE/change-control.yml:8-13
Prohibitions
- No direct commit to the
mainbranch. - No force pushes to the
mainbranch. - No unsigned commits for critical system changes.
- No silent changes; all changes must be logged in
decision-log.yml.
Sources: 01_GOVERNANCE/change-control.yml:25-30
Successful installation of the Imperial Archive ensures that technology serves the human vision without compromising the foundational protected nucleus. Every step, from DNS staging to project intake, verifies that the system remains a durable, governed legacy.