Visibility Declarations & Unknowns
Relevant source files
The following files were used as context for generating this wiki page:
The Visibility Declarations and Unknowns system governs the exposure of repository content and tracks unresolved architectural questions within the Imperial Archive. This system ensures that sensitive data remains protected while providing a roadmap for future transitions from private to public states. It operates as part of the broader Governance framework to maintain a controlled operational environment.
Sources: 01_GOVERNANCE/visibility-declaration.yml:1-5, 01_GOVERNANCE/unknowns.yml:1-5
Visibility Management
The system classifies all repository content by its exposure level. The primary repository remains private to protect core identity and sensitive developmental data. The visibility-declaration.yml file serves as the authoritative record for current and future exposure states.
Sources: 02_REPOSITORY/repository.yml:8-15, 01_GOVERNANCE/visibility-declaration.yml:7-11
Current Status and Activation
The repository is currently in a PRIVATE state, effective since October 8, 2026. A gradual transition to a public presence is scheduled for early 2027.
| Attribute | Value |
|---|---|
| Current Status | PRIVATE |
| Effective Date | 2026-10-08 |
| Activation Date | 2027-01-01 |
| Activation Type | GRADUAL_REVIEW |
| Timezone | Asia/Riyadh (UTC+3) |
Sources: 01_GOVERNANCE/visibility-declaration.yml:8-18
Privacy Classifications
Certain items are designated for permanent privacy. These items never transition to public visibility, even after the scheduled activation date.
- Child Data: Specific folders for Tamara and Elias.
- Security Assets: Private keys and credentials.
- Internal Records: Sensitive decision logs and the unredacted origin story.
Sources: 01_GOVERNANCE/visibility-declaration.yml:20-27
Public Expression Strategy
Public visibility is achieved by creating a separate repository named Imperial-Archive-Public. This repository contains only high-level vision statements and excludes the system core.
Sources: 01_GOVERNANCE/visibility-declaration.yml:29-31
Unknowns Registry
The Unknowns Registry tracks unresolved questions that impact project strategy and technical implementation. Each entry is assigned a priority and status to guide development efforts.
Sources: 01_GOVERNANCE/unknowns.yml:8-15
Registry Structure
The following diagram illustrates how unknowns are categorized and prioritized for resolution.
The diagram shows the distribution of open questions across different priority levels as defined in the registry.
Sources: 01_GOVERNANCE/unknowns.yml:9-16
Active Unknowns Table
The registry tracks both open and resolved questions.
| ID | Question | Status | Priority/Answer |
|---|---|---|---|
| UNK-001 | Final public brand name? | open | medium |
| UNK-002 | Hosting provider? | open | high |
| UNK-005 | Arabic official language? | decided | Yes — bilingual |
| UNK-006 | Long-term AI providers? | open | high |
| UNK-007 | DR test schedule? | open | high |
Sources: 01_GOVERNANCE/unknowns.yml:9-16
Conflicts and Decision Logic
Visibility and Unknowns are subject to the project's conflict resolution and decision-making workflows. Conflicts arise when declared configurations deviate from actual implementation or when external ideas intersect with internal sovereignty.
Sources: 01_GOVERNANCE/conflicts.yml:8-15
Conflict Resolution Flow
When a conflict or unknown transition occurs, it follows a strict precedence logic to maintain the "Source of Truth."
This sequence ensures that visibility changes or unknown resolutions are formally authorized and recorded.
Sources: 01_GOVERNANCE/source-of-truth.yml:8-16, 01_GOVERNANCE/decision-log.yml:1-5, 01_GOVERNANCE/conflicts.yml:17-23
Status of Major Conflicts
- Public vs Private: Resolved through the separation of a public-facing repository.
- External Ideas: Deprecated in favor of internal sovereignty.
- System Pathing: Pending resolution (Severity: LOW).
Sources: 01_GOVERNANCE/conflicts.yml:8-15, 01_GOVERNANCE/decision-log.yml:10-15
Implementation Details
Visibility and Unknowns are managed via YAML configurations to ensure human-readability and version control.
# Example: Permanent Privacy Items in visibility-declaration.yml
permanent_privacy:
items:
- "Child data (Tamara, Elias)"
- "Private keys"
- "Credentials"
- "Sensitive decision log"
Sources: 01_GOVERNANCE/visibility-declaration.yml:20-25
Summary
Visibility Declarations and Unknowns provide the structural guardrails for the Imperial Archive's evolution. By explicitly declaring what is hidden and what is yet to be known, the system maintains high integrity and prevents unauthorized data exposure while allowing for planned growth and public engagement.
Sources: 01_GOVERNANCE/visibility-declaration.yml:1-3, 01_GOVERNANCE/unknowns.yml:1-3