Repository Connection Map
Relevant source files
The following files were used as context for generating this wiki page:
The Repository Connection Map defines and tracks all external platform integrations, service providers, and domain configurations within the Imperial Archive ecosystem. It ensures that the system maintains a "One Body Policy" where the canonical repository remains the sovereign source of truth, preventing external platforms from overriding internal governance.
This system classifies every connection by its operational state and type, ranging from core hosting on GitHub to specialized AI and automation services like OpenAI and n8n. All connections must be logged and verified before activation to adhere to the project's strict security and sovereignty rules.
Sources: 02_REPOSITORY/connection-map.yml:1-32, imperial_archive_soul_system_final.yaml:194-205
Connection Classification and Status
The system categorizes external entities into specific types and assigns a verification status. This ensures the administrator can distinguish between active infrastructure and proposed or suspended services.
Classification Levels
The system uses three primary classification levels to track the lifecycle of a connection:
- DECLARED: The connection is mentioned in the repository records but not yet active.
- CONFIGURED: Configuration files or parameters exist for the service.
- VERIFIED_LIVE: The connection is confirmed as working and operational.
Sources: 02_REPOSITORY/connection-map.yml:7-10
Integrated Service Providers
The following table summarizes the primary connections identified in the repository:
| ID | Name | Type | Status | Details |
|---|---|---|---|---|
| CONN-GITHUB | GitHub | HOST | VERIFIED_LIVE | Account: latifah6114-ux |
| CONN-DOMAIN | imperialarchive.ai | DOMAIN | CONFIGURED | Registrar: Epik, DNS: Cloudflare |
| CONN-REPLIT | Replit | EXECUTION | ACTIVE | Environment for execution |
| CONN-OPENAI | OpenAI | AI_PROVIDER | ACTIVE | Core AI capabilities |
| CONN-NOTION | Notion | KNOWLEDGE_UI | ACTIVE | UI for knowledge management |
| CONN-N8N | n8n Cloud | AUTOMATION | DECLARED | Automation workflows |
| CONN-META | Meta | SOCIAL | SUSPENDED | Social media integration |
Sources: 02_REPOSITORY/connection-map.yml:13-25, 01_GOVERNANCE/canonical-registry.yml:23-28
Connection Rules and Sovereignty
The connection map is governed by specific rules to maintain the integrity of the Imperial Archive.
- Verification Requirement: No connection is permitted without explicit verification.
- Canonical Sovereignty: No external platform or service is allowed to override the canonical repository.
- Mandatory Logging: Every connection must be recorded in the map before it is activated.
Sources: 02_REPOSITORY/connection-map.yml:27-30
System Integration Flow
The following diagram illustrates how data flows between the internal repository, AI agents, and external service providers as defined in the system architecture.
The diagram shows the hierarchical flow from the repository through the Replit execution environment to the AI provider.
Sources: imperial_archive_soul_system_final.yaml:313-317
Domain and Infrastructure Mapping
The Imperial Archive uses a centralized domain management strategy. The primary domain, imperialarchive.ai, serves as the hub for various sub-services managed via Cloudflare and Epik.com.
Subdomain Registry
Subdomains are phased into the infrastructure to support specific program modules:
- Phase 1:
www,tamara(educational),security - Phase 2:
docs,elias - Phase 3:
api,status
Sources: 02_REPOSITORY/domain-subdomains.yml:10-18
Infrastructure Relationships
The relationship between the repository, the owner, and the hosting platforms is strictly defined to ensure provenance and accountability.
This ER diagram represents the ownership and definition links between the core repository and its external connections.
Sources: 02_REPOSITORY/repository.yml:8-16, 01_GOVERNANCE/canonical-registry.yml:18-35, 02_REPOSITORY/connection-map.yml:12-25
Automation and Project-Specific Connections
Individual projects within the archive, such as the Tamara Learning Program, utilize the connection map for specific operational needs. For example, the IA-EDU-TAMARA-AUTO-001 automation is linked directly to the CONN-N8N connection ID.
- Platform: n8n Cloud (Referenced as
CONN-N8N) - Purpose: Daily Homework Digest for the Tamara Learning Program.
- Data Policy: No child data, links, or credentials are permitted within the local file; these must be filled only within the secure n8n environment.
Sources: projects/tamara-learning-program/manifests/intake-inventory.yaml:61-66
Summary of Connectivity
The Repository Connection Map provides a structured inventory of the Imperial Archive's digital footprint. By enforcing strict verification levels and maintaining a clear distinction between the local "Soul" of the system and external "Execution" platforms, the map ensures that the archive remains a living, but secure, infrastructure. Every external link—from DNS records to AI providers—is documented to support the project's goal of long-term legacy and recovery.
Sources: 02_REPOSITORY/structure.yml:25-27, 02_REPOSITORY/connection-map.yml:1-32