Intake Inventory Manifests
Relevant source files
The following files were used as context for generating this wiki page:
Intake Inventory Manifests serve as machine-readable records that track the provenance, status, and classification of all assets within a project. They ensure that original source files remain immutable while providing a structured registry for derived canonical outputs and automated workflows.
These manifests function within the broader Imperial Archive ecosystem to maintain the "Preserve Originals" policy. This policy dictates that original sources must never be overwritten, and all implementations must be built around these immutable foundations.
Sources: projects/tamara-learning-program/manifests/intake-inventory.yaml:1-12, projects/tamara-learning-program/README.md:14-18
Manifest Structure and Metadata
Every manifest defines project identification metadata to establish ownership and location within the repository.
Project Identification
The manifest uses a unique ID and organizational mapping to anchor the project.
| Field | Description | Example Value |
|---|---|---|
id | Unique project identifier | IA-EDU-TAMARA-001 |
name | Descriptive project name | Tamara Learning Program |
organization | Governing entity | Imperial Archive |
owner | Responsible individual | Latifah Almutairi |
project_path | Absolute repository path | projects/tamara-learning-program/ |
intake_status | Current lifecycle state | INSTALLED_NOT_RELEASED |
Sources: projects/tamara-learning-program/manifests/intake-inventory.yaml:1-10
Source Asset Classification
The manifest categorizes received files into specific classes to define their role in the system architecture.
Received Sources Registry
The following diagram illustrates the relationship between physical files and their functional classifications.
Classification Metadata
| Filename | Class | Status |
|---|---|---|
...TAMARA_MASTER_v1.0.0.yaml | GOVERNING_EDUCATIONAL_MASTER | RECEIVED_IN_CHAT_SOURCE_PENDING |
...GROWTH_PROMPT.txt | LOCKED_IDENTITY_AND_GROWTH_STANDARD | RECEIVED_IN_CHAT_SOURCE_PENDING |
...PORTAL_LITE_SOURCE🟦.txt | ENGLISH_PORTAL_SOURCE | RECEIVED |
...PORTAL_LITE🟦.html | ENGLISH_PORTAL_RUNTIME_CANDIDATE | RECEIVED |
Sources: projects/tamara-learning-program/manifests/intake-inventory.yaml:15-26
Gap Analysis and Release Blockers
The manifest explicitly tracks missing assets and technical requirements that prevent a production release.
Identified Gaps
- Asset Gaps: Independent approved signature assets, logos, and official seals are currently missing.
- Source Specs: Curriculum sources for Mathematics, Science, and Arabic are required.
- Technical Gaps: External audio URLs (e.g., HeyGen) must be replaced with local archival masters.
Sources: projects/tamara-learning-program/manifests/intake-inventory.yaml:33-46, projects/tamara-learning-program/reports/SOURCE_GAPS.md:7-22
The Release Validation Flow
The system prevents final release until all blockers are resolved via the following logic:
Installation and Preservation Protocols
The intake process follows the "Drop by Drop" installation protocol to ensure repository integrity.
Installation Steps
- RECEIVE: Accept the file.
- CLASSIFY: Assign a functional class (e.g., MASTER, ASSET).
- VALIDATE: Perform integrity and rights checks.
- COMMIT: Upload to a separate branch.
- MERGE: Integrate into the main branch after success.
Sources: 02_REPOSITORY/installation.yml:11-19
Directory Logic
The manifest maps assets to a specific directory structure to maintain separation of concerns:
source-original/: Immutable source evidence.canonical/: Derived implementation and logic.assets/: Verified and approved binary assets.manifests/: Machine-readable records (the inventory itself).
Sources: projects/tamara-learning-program/source-original/README.md:12-20, 02_REPOSITORY/structure.yml:33-35
Automation Manifesting
Workflows associated with the project are defined within the manifest to ensure data policy compliance.
Example: Daily Homework Digest
The manifest tracks automation metadata for the n8n platform.
automations:
- id: IA-EDU-TAMARA-AUTO-001
name: Tamara - Daily Homework Digest
platform: n8n Cloud (CONN-N8N)
path: projects/tamara-learning-program/canonical/automation/n8n/tamara-daily-homework-digest.json
status: PROPOSED_NOT_ACTIVE
data_policy: no child data, links, emails or credentials stored in the file
Sources: projects/tamara-learning-program/manifests/intake-inventory.yaml:55-61
Conclusion
Intake Inventory Manifests provide the necessary governance for the Imperial Archive's educational projects. By explicitly linking received files to functional classes and tracking release blockers, the manifests ensure that the "Steel Spine, Velvet Soul" philosophy is maintained through technical rigor and provenance tracking.
Sources: 00_FOUNDATION/origin.md:27, projects/tamara-learning-program/manifests/intake-inventory.yaml:1-12