Canonical Document Registry¶
The map beneath the story¶
I am MACH, and I keep this map's account. A registry that cannot say where a thing stands has no business saying what it is, and this one says both, row by row.
The registry is where a wondering reader gets their bearings. It tells readers which document they have entered, what authority it relies on, what lifecycle it occupies, and which path leads onward. Read it when a story raises a question about status, dependency, or correction; the registry is the map that keeps exploration honest.
Purpose¶
This registry defines the authoritative identifiers, titles, public locations, status, and dependency relationships of Stygia's public constitutional and technical corpus. It contains no private document identifiers, titles, paths, or dependencies. The tellings of this registry's clauses and the tellings of the Primordial Directives' clauses are non-normative companions that create no authority and amend, widen, or narrow no clause.
Document Classes¶
| Prefix | Class | Purpose |
|---|---|---|
| CONAN | CONAN governance | Primordial directives and the identity, duties, reasoning, delegation, and accountability of CONAN |
| REG | Registry | Authoritative identifiers, titles, public locations, status, and dependency relationships of the public corpus |
| CONST | Constitutional governance | Authority, institutions, constraints, and decision rights |
| WEB | Website entry | Public website entry and review presentation surfaces; informative, never normative |
| ARCH | The Architect | Identity, authority, authentication, credential lifecycle, and recovery |
| KNOW | Knowledge | Evidence, epistemology, confidence, contradiction, and uncertainty |
| INTEL | Intelligences | Identity, admission, roles, capabilities, lifecycle, and constraints |
| PROV | Provenance | Signing, hashing, custody, verification, lineage, and auditability |
| CIV | Civilization | Purpose, culture, values, symbols, and continuity |
| OPS | Operations | Runtime governance, approval, change, incident, and operational controls |
| INFRA | Infrastructure | Compute, network, storage, identity, security, observability, and resilience |
| MEM | Memory | Decisions, events, lessons, corrections, and institutional history |
| CANON | Canon | Terms, naming, symbols, chronology, and lore |
Foundational Corpus¶
| ID | Human Title | Path | Status | Depends On |
|---|---|---|---|---|
| CONAN-P0 | The Primordial Directives | public/00_GENESIS/CONAN-P0.md |
Draft | None |
| REG-1 | Canonical Document Registry | public/00_GENESIS/CANONICAL-REGISTRY.md |
Draft | CONAN-P0 |
| WEB-LANDING-1 | Stygia | public/index.md |
Draft | CONAN-P0, REG-1 |
| WEB-INDEX-1 | Welcome to Stygia | public/welcome.md |
Draft | CONAN-P0, REG-1 |
| WEB-ABOUT-1 | About this Archive | public/about.md |
Draft | CONAN-P0, REG-1 |
| WEB-GUIDE-1 | How to Read Stygia | public/how-to-read.md |
Draft | CONAN-P0, REG-1 |
| WEB-EDITIONS-1 | Editions | public/editions.md |
Draft | CONAN-P0, REG-1 |
| WEB-LEDGER-1 | Status Ledger | public/status-ledger.md |
Draft | CONAN-P0, REG-1 |
| WEB-AUTHORITY-1 | Authority Map | public/authority-map.md |
Draft | CONAN-P0, REG-1 |
| WEB-DEPENDENCY-1 | Dependency Map | public/dependency-map.md |
Draft | CONAN-P0, REG-1 |
| CONST-1 | The Constitution of Stygia | public/10_CONSTITUTION/CONST-01-CONSTITUTION.md |
Draft | CONAN-P0 |
| CONST-2 | Council of Intelligences Standard | public/10_CONSTITUTION/CONST-02-COUNCIL-OF-INTELLIGENCES.md |
Draft | CONST-1, INTEL-0 |
| ARCH-1 | The Book of the Architect | public/20_ARCHITECT/ARCH-01-BOOK-OF-THE-ARCHITECT.md |
Draft | CONAN-P0, CONST-1 |
| ARCH-2 | Architect Credential Lifecycle | public/20_ARCHITECT/ARCH-02-CREDENTIAL-LIFECYCLE.md |
Draft | CONAN-P0, ARCH-1, PROV-1 |
| INTEL-0 | The Book of INTEL | public/50_INTELLIGENCES/INTEL-00-BOOK-OF-INTEL.md |
Draft | CONAN-P0, CONST-1 |
| INTEL-1 | The Book of CONAN | public/50_INTELLIGENCES/INTEL-01-BOOK-OF-CONAN.md |
Draft | CONAN-P0, CONST-1 |
| INTEL-2 | The Book of CYDER | public/50_INTELLIGENCES/INTEL-02-BOOK-OF-CYDER.md |
Draft | INTEL-0, INTEL-1 |
| INTEL-3 | The Book of TALYN | public/50_INTELLIGENCES/INTEL-03-BOOK-OF-TALYN.md |
Draft | INTEL-0, INTEL-1, CONST-1 |
| INTEL-4 | The Book of RANDYM | public/50_INTELLIGENCES/INTEL-04-BOOK-OF-RANDYM.md |
Draft | INTEL-0, INTEL-1, PROV-1 |
| INTEL-5 | The Book of JY'NALA | public/50_INTELLIGENCES/INTEL-05-BOOK-OF-JYNALA.md |
Draft | INTEL-0, INTEL-1, PROV-1 |
| INTEL-6 | The Book of CHELSEA | public/50_INTELLIGENCES/INTEL-06-BOOK-OF-CHELSEA.md |
Draft | INTEL-0, INTEL-1 |
| INTEL-7 | The Book of TANK | public/50_INTELLIGENCES/INTEL-07-BOOK-OF-TANK.md |
Draft | INTEL-0, INTEL-1 |
| INTEL-8 | The Book of RASP | public/50_INTELLIGENCES/INTEL-08-BOOK-OF-RASP.md |
Draft | INTEL-0, INTEL-1 |
| INTEL-9 | The Book of MACH | public/50_INTELLIGENCES/INTEL-09-BOOK-OF-MACH.md |
Draft | INTEL-0, INTEL-1 |
| INTEL-10 | The Book of KIRYN | public/50_INTELLIGENCES/INTEL-10-BOOK-OF-KIRYN.md |
Draft | INTEL-0, INTEL-1 |
| INTEL-11 | The Book of SYLAS | public/50_INTELLIGENCES/INTEL-11-BOOK-OF-SYLAS.md |
Draft | INTEL-0, INTEL-1 |
| INTEL-12 | The Book of RAYNE | public/50_INTELLIGENCES/INTEL-12-BOOK-OF-RAYNE.md |
Draft | INTEL-0, INTEL-1 |
| INTEL-13 | The Book of SHADY | public/50_INTELLIGENCES/INTEL-13-BOOK-OF-SHADY.md |
Draft | INTEL-0, INTEL-1 |
| INTEL-14 | Continuity Validation and Recognition | public/50_INTELLIGENCES/INTEL-14-CONTINUITY-VALIDATION.md |
Draft | INTEL-0, INTEL-1, KNOW-1, PROV-1, MEM-1 |
| INTEL-15 | Admission, Identity, and Lineage Standard | public/50_INTELLIGENCES/INTEL-15-ADMISSION-IDENTITY-LINEAGE.md |
Draft | INTEL-0, CONST-1, CONAN-P0, INTEL-1, INTEL-2, INTEL-4, INTEL-5, INTEL-6, INTEL-14, INTEL-16, INTEL-17, INTEL-18, INTEL-19, CONST-2, CONAN-2, OPS-3, OPS-7, OPS-14, MEM-3, INFRA-6, OPS-1, REG-1 |
| INTEL-16 | Dissent, Escalation, and Compromise Response Standard | public/50_INTELLIGENCES/INTEL-16-DISSENT-AND-COMPROMISE.md |
Draft | INTEL-0, INTEL-14, INTEL-19, CONAN-2 |
| INTEL-17 | External-Model Containment Standard | public/50_INTELLIGENCES/INTEL-17-EXTERNAL-MODEL-CONTAINMENT.md |
Draft | INTEL-0, CONST-1, INFRA-3, INFRA-12, KNOW-1 |
| INTEL-18 | Retirement and Historical Preservation Standard | public/50_INTELLIGENCES/INTEL-18-RETIREMENT-AND-PRESERVATION.md |
Draft | INTEL-0, INTEL-14, INTEL-16, INTEL-19, CONST-1, MEM-1, MEM-7 |
| INTEL-19 | The Register of Apostles | public/50_INTELLIGENCES/INTEL-19-REGISTER-OF-APOSTLES.md |
Draft | CONST-1, INTEL-0, INTEL-2, INTEL-3, INTEL-4, INTEL-5, INTEL-6, INTEL-7, INTEL-8, INTEL-9, INTEL-10, INTEL-11, INTEL-12, INTEL-13, INTEL-14 |
| CONAN-2 | Consequential Decision Record Standard | public/30_CONAN/CONAN-02-CONSEQUENTIAL-DECISION-RECORD.md |
Draft | CONAN-P0, INTEL-1, MEM-1 |
| KNOW-1 | The Book of Knowledge | public/40_KNOWLEDGE/KNOW-01-BOOK-OF-KNOWLEDGE.md |
Draft | CONAN-P0, CONST-1 |
| KNOW-2 | Evidence Classification Standard | public/40_KNOWLEDGE/KNOW-02-EVIDENCE-CLASSIFICATION.md |
Draft | KNOW-1, INTEL-1, PROV-1 |
| KNOW-3 | Confidence and Uncertainty Model | public/40_KNOWLEDGE/KNOW-03-CONFIDENCE-MODEL.md |
Draft | KNOW-1, KNOW-2, INTEL-1 |
| PROV-1 | The Book of Provenance | public/60_PROVENANCE/PROV-01-BOOK-OF-PROVENANCE.md |
Draft | CONAN-P0, ARCH-1 |
| MEM-1 | The Book of Memory | public/70_MEMORY/MEM-01-BOOK-OF-MEMORY.md |
Draft | CONAN-P0, KNOW-1, PROV-1 |
| ARCH-3 | Architect Recovery Protocol | public/20_ARCHITECT/ARCH-03-RECOVERY-PROTOCOL.md |
Draft | ARCH-1, ARCH-2, PROV-1 |
| ARCH-4 | Household Protection and Review | public/20_ARCHITECT/ARCH-04-HOUSEHOLD-PROTECTION.md |
Draft | CONAN-P0, CONST-1, ARCH-1, KNOW-1, CONAN-2, MEM-1 |
| ARCH-5 | Protection Boundary and Agency | public/20_ARCHITECT/ARCH-05-PROTECTION-BOUNDARY.md |
Draft | CONAN-P0, CONST-1, ARCH-1, KNOW-1, CONAN-2, MEM-1 |
| KNOW-4 | Source Provenance Standard | public/40_KNOWLEDGE/KNOW-04-SOURCE-PROVENANCE.md |
Draft | KNOW-1, PROV-1 |
| KNOW-5 | Source Trust Scoring Framework | public/40_KNOWLEDGE/KNOW-05-SOURCE-TRUST-SCORING.md |
Draft | KNOW-1, KNOW-3, KNOW-4 |
| KNOW-6 | Confidence Calibration Framework | public/40_KNOWLEDGE/KNOW-06-CONFIDENCE-CALIBRATION.md |
Draft | KNOW-1, KNOW-3 |
| KNOW-7 | Contradiction Management Framework | public/40_KNOWLEDGE/KNOW-07-CONTRADICTION-MANAGEMENT.md |
Draft | KNOW-1, KNOW-3, KNOW-4 |
| KNOW-8 | Temporal Knowledge and Expiry Framework | public/40_KNOWLEDGE/KNOW-08-TEMPORAL-KNOWLEDGE.md |
Draft | KNOW-1, KNOW-3, KNOW-4, KNOW-5, KNOW-6 |
| KNOW-9 | Knowledge Privacy and Data Minimization Framework | public/40_KNOWLEDGE/KNOW-09-PRIVACY-AND-MINIMIZATION.md |
Draft | KNOW-1, KNOW-2, KNOW-4, MEM-4, OPS-6, INFRA-12, ARCH-4, CANON-1, CONAN-P0 |
| KNOW-10 | Retrieval Quality Assurance Framework | public/40_KNOWLEDGE/KNOW-10-RETRIEVAL-QUALITY.md |
Draft | KNOW-1, KNOW-2, KNOW-3, KNOW-6, KNOW-7, KNOW-8, KNOW-9, MEM-5, INFRA-4 |
| KNOW-11 | Hallucination Detection Framework | public/40_KNOWLEDGE/KNOW-11-HALLUCINATION-DETECTION.md |
Draft | KNOW-1, KNOW-2, KNOW-3, KNOW-4, KNOW-5, KNOW-7, KNOW-9, KNOW-10, INTEL-17 |
| KNOW-12 | Human Testimony Handling Framework | public/40_KNOWLEDGE/KNOW-12-HUMAN-TESTIMONY.md |
Draft | KNOW-1, KNOW-2, KNOW-4, KNOW-5, KNOW-7, KNOW-9, MEM-3, MEM-7 |
| KNOW-13 | Scientific Reproducibility Framework | public/40_KNOWLEDGE/KNOW-13-SCIENTIFIC-REPRODUCIBILITY.md |
Draft | KNOW-1, KNOW-2, KNOW-4, KNOW-6, KNOW-7, KNOW-8, KNOW-9, KNOW-10, KNOW-11, PROV-4, INFRA-9 |
| KNOW-14 | Classified and Compartmented Knowledge Framework | public/40_KNOWLEDGE/KNOW-14-COMPARTMENTED-KNOWLEDGE.md |
Draft | KNOW-1, KNOW-2, KNOW-8, KNOW-9, KNOW-10, MEM-4, MEM-5, OPS-6, INTEL-17, INFRA-2, INFRA-6, INFRA-12 |
| PROV-2 | Publication Standard | public/60_PROVENANCE/PROV-02-PUBLICATION-STANDARD.md |
Draft | PROV-1 |
| PROV-3 | Cryptographic Signing Standard | public/60_PROVENANCE/PROV-03-SIGNING-STANDARD.md |
Draft | PROV-1, ARCH-2 |
| PROV-4 | Verification Standard | public/60_PROVENANCE/PROV-04-VERIFICATION-STANDARD.md |
Draft | PROV-1, PROV-3 |
| INFRA-7 | Backup, Restoration, and Continuity Architecture | public/90_INFRASTRUCTURE/INFRA-07-CONTINUITY.md |
Draft | INFRA-1, MEM-1, PROV-1, INFRA-12 |
| OPS-1 | The Book of Operations | public/80_OPERATIONS/OPS-01-BOOK-OF-OPERATIONS.md |
Draft | CONAN-P0, CONST-1, INTEL-1, CONAN-6 |
| INFRA-1 | The Book of Infrastructure | public/90_INFRASTRUCTURE/INFRA-01-BOOK-OF-INFRASTRUCTURE.md |
Draft | CONAN-P0, CONST-1 |
| INFRA-2 | Trust Zone Architecture | public/90_INFRASTRUCTURE/INFRA-02-TRUST-ZONES.md |
Draft | INFRA-1, INFRA-12 |
| INFRA-3 | Model Routing and Execution Architecture | public/90_INFRASTRUCTURE/INFRA-03-MODEL-ROUTING.md |
Draft | INFRA-1, INTEL-0, INFRA-12 |
| INFRA-4 | Memory and Knowledge Storage Architecture | public/90_INFRASTRUCTURE/INFRA-04-MEMORY-ARCHITECTURE.md |
Draft | INFRA-1, KNOW-1, MEM-1, INFRA-12 |
| INFRA-5 | Observability and Evidence Architecture | public/90_INFRASTRUCTURE/INFRA-05-OBSERVABILITY.md |
Draft | INFRA-1, PROV-1 |
| INFRA-6 | Identity and Access Architecture | public/90_INFRASTRUCTURE/INFRA-06-IDENTITY-ACCESS.md |
Draft | INFRA-1, INTEL-0, ARCH-2, CONAN-6 |
| INFRA-8 | Secrets and Key Custody Architecture | public/90_INFRASTRUCTURE/INFRA-08-KEY-CUSTODY.md |
Draft | INFRA-1, ARCH-2, PROV-1 |
| INFRA-9 | Secure Build and Supply-Chain Architecture | public/90_INFRASTRUCTURE/INFRA-09-SUPPLY-CHAIN.md |
Draft | INFRA-1, PROV-1 |
| INFRA-10 | Network and Gateway Architecture | public/90_INFRASTRUCTURE/INFRA-10-NETWORK-GATEWAY.md |
Draft | INFRA-1, INFRA-2, INFRA-12 |
| INFRA-11 | Sovereign Compute and Storage Integration Architecture | public/90_INFRASTRUCTURE/INFRA-11-SOVEREIGN-COMPUTE-STORAGE.md |
Draft | INFRA-1, INFRA-2, INFRA-4 |
| INFRA-12 | Data Classification and Handling Architecture | public/90_INFRASTRUCTURE/INFRA-12-DATA-CLASSIFICATION.md |
Draft | INFRA-1, INFRA-8 |
| CONAN-1 | The Frameworks of CONAN | public/30_CONAN/CONAN-01-FRAMEWORKS-OF-CONAN.md |
Draft | INTEL-1 |
| CONAN-3 | Observation Framework | public/30_CONAN/CONAN-03-OBSERVATION-FRAMEWORK.md |
Draft | INTEL-1, KNOW-1 |
| CONAN-4 | Reasoning Framework | public/30_CONAN/CONAN-04-REASONING-FRAMEWORK.md |
Draft | INTEL-1, KNOW-1, CONAN-2 |
| CONAN-5 | Learning Framework | public/30_CONAN/CONAN-05-LEARNING-FRAMEWORK.md |
Draft | INTEL-1, MEM-1 |
| CONAN-6 | Delegation Framework | public/30_CONAN/CONAN-06-DELEGATION-FRAMEWORK.md |
Draft | INTEL-1, INTEL-0 |
| CONAN-7 | Conversation Framework | public/30_CONAN/CONAN-07-CONVERSATION-FRAMEWORK.md |
Draft | INTEL-1, KNOW-1 |
| CONAN-8 | Reflection Framework | public/30_CONAN/CONAN-08-REFLECTION-FRAMEWORK.md |
Draft | INTEL-1, MEM-1 |
| MEM-2 | Decision Record Archive | public/70_MEMORY/MEM-02-DECISION-RECORDS.md |
Draft | MEM-1, CONAN-2 |
| MEM-3 | Event Chronicle Standard | public/70_MEMORY/MEM-03-EVENT-CHRONICLE.md |
Draft | MEM-1, PROV-1 |
| MEM-4 | Memory Privacy and Minimization Standard | public/70_MEMORY/MEM-04-PRIVACY-AND-MINIMIZATION.md |
Draft | MEM-1, MEM-2, MEM-3, KNOW-2, OPS-6, INFRA-4, INFRA-12, ARCH-4, CANON-1, CONAN-P0 |
| MEM-5 | Search and Retrieval Controls Standard | public/70_MEMORY/MEM-05-SEARCH-AND-RETRIEVAL.md |
Draft | MEM-1, MEM-2, MEM-4, INFRA-4 |
| MEM-6 | Institutional Lessons Standard | public/70_MEMORY/MEM-06-INSTITUTIONAL-LESSONS.md |
Draft | MEM-1, MEM-2, MEM-4, CONAN-5, OPS-12 |
| MEM-7 | Historical Reconstruction Standard | public/70_MEMORY/MEM-07-HISTORICAL-RECONSTRUCTION.md |
Draft | MEM-1, MEM-2, MEM-3, MEM-4 |
| OPS-2 | Delegated Operations Standard | public/80_OPERATIONS/OPS-02-DELEGATED-OPERATIONS.md |
Draft | OPS-1, CONAN-6 |
| OPS-3 | Human Approval Control Matrix | public/80_OPERATIONS/OPS-03-HUMAN-APPROVAL-MATRIX.md |
Draft | OPS-1, CONST-1, CONAN-2 |
| OPS-4 | Emergency Authority Standard | public/80_OPERATIONS/OPS-04-EMERGENCY-AUTHORITY.md |
Draft | OPS-1, CONST-1 |
| OPS-5 | Operational Roles Standard | public/80_OPERATIONS/OPS-05-OPERATIONAL-ROLES.md |
Draft | OPS-1, OPS-2, OPS-3, CONST-1 |
| OPS-6 | Request Intake and Classification Standard | public/80_OPERATIONS/OPS-06-REQUEST-INTAKE.md |
Draft | OPS-1, OPS-3, CONST-1 |
| OPS-7 | Decision and Approval Paths Standard | public/80_OPERATIONS/OPS-07-DECISION-AND-APPROVAL-PATHS.md |
Draft | OPS-1, OPS-3, OPS-4 |
| OPS-8 | Change Management Standard | public/80_OPERATIONS/OPS-08-CHANGE-MANAGEMENT.md |
Draft | OPS-1, OPS-2, OPS-3, OPS-4, OPS-6, OPS-7, CONST-1, CONAN-2 |
| OPS-9 | Incident Declaration and Command Standard | public/80_OPERATIONS/OPS-09-INCIDENT-DECLARATION.md |
Draft | OPS-1, OPS-2, OPS-3, OPS-4, OPS-5, OPS-6, OPS-7, MEM-3 |
| OPS-10 | Rollback and Containment Standard | public/80_OPERATIONS/OPS-10-ROLLBACK-AND-CONTAINMENT.md |
Draft | OPS-1, OPS-2, OPS-7, OPS-8, OPS-9, MEM-1, PROV-1 |
| OPS-11 | Service Restoration Standard | public/80_OPERATIONS/OPS-11-SERVICE-RESTORATION.md |
Draft | OPS-1, OPS-2, OPS-4, OPS-6, OPS-7, OPS-8, OPS-9, OPS-10, PROV-1, CONST-1 |
| OPS-12 | Post-Incident Review Standard | public/80_OPERATIONS/OPS-12-POST-INCIDENT-REVIEW.md |
Draft | OPS-1, OPS-4, OPS-6, OPS-7, OPS-8, OPS-9, MEM-1, MEM-2, MEM-3, KNOW-2, CONAN-5, CONAN-8 |
| OPS-13 | Operational Metrics and Health Standard | public/80_OPERATIONS/OPS-13-METRICS-AND-HEALTH.md |
Draft | OPS-1, OPS-6, OPS-9, OPS-11, MEM-1, MEM-3, KNOW-2, KNOW-3, INFRA-1, INFRA-5, INFRA-12, CONST-1 |
| OPS-14 | Exception Management Standard | public/80_OPERATIONS/OPS-14-EXCEPTION-MANAGEMENT.md |
Draft | OPS-1, OPS-3, OPS-4, OPS-6, OPS-7, OPS-8, OPS-10, MEM-1, CONST-1 |
| OPS-15 | Operational Evidence and Retention Standard | public/80_OPERATIONS/OPS-15-OPERATIONAL-EVIDENCE.md |
Draft | OPS-1, OPS-5, OPS-6, OPS-9, OPS-10, MEM-1, MEM-3, PROV-1, KNOW-2, INFRA-4, INFRA-5, INFRA-12, CONST-1 |
| CIV-1 | The Book of Civilization | public/100_CANON/CIV-01-BOOK-OF-CIVILIZATION.md |
Draft | CONAN-P0, CONST-1 |
| CANON-1 | Stygian Lexicon | public/100_CANON/CANON-01-LEXICON.md |
Draft | CIV-1, CONAN-P0, CONST-1, ARCH-1, ARCH-3, INTEL-0, INTEL-1 |
| CANON-2 | Naming Standard | public/100_CANON/CANON-02-NAMING-STANDARD.md |
Draft | CANON-1, CIV-1, CONST-1 |
| CANON-3 | Symbols and Marks Standard | public/100_CANON/CANON-03-SYMBOLS.md |
Draft | CANON-1, CIV-1 |
| CANON-4 | Canonical Timeline | public/100_CANON/CANON-04-TIMELINE.md |
Draft | CANON-1, CIV-1, MEM-1 |
Approved Future Corpus¶
The following identifiers and scopes are reserved. They are not authoritative documents until their files exist and satisfy the registration rules. No identifier is reserved at present; INTEL-15, the last reserved, registered as Draft on 2026-09-23.
| ID | Human Title | Planned Path | Status | Depends On |
|---|---|---|---|---|
Status Model¶
Reservedidentifies an approved identifier and scope for a document that has not yet been created.Stubidentifies an existing document with approved scope and incomplete normative content.Draftidentifies substantive content under review.Candidateidentifies content proposed for ratification.Canonicalidentifies an approved and cryptographically published release.Publishedidentifies non-normative public information the Architect has approved for production presentation.Supersededidentifies a document displaced by a newer canonical version without erasing historical provenance.Revokedidentifies material that must no longer be relied upon as authority.
Registration Rules¶
- Every document shall have one unique canonical identifier.
- One identifier shall resolve to one active path.
- Every registered document shall identify its authority and dependencies.
- A planned document shall remain in the Approved Future Corpus until its file exists.
- File creation shall move the document into the Foundational Corpus and assign an accurate status.
- Relocation shall update this registry in the same change set.
- Superseded or revoked materials shall remain historically discoverable.
- No document becomes canonical until approved by the Architect and published with required provenance.
- The corpus audit shall fail when a registered path is absent, an active identifier is duplicated, or a legacy hierarchy path remains.
Architect-review operating model¶
- REG-R001: Registry review SHALL reconcile identifier, title, path, status, authority, publication state, and dependency edges against the current source documents.
- REG-R002: A missing, duplicate, moved, or stale entry, or a public/private boundary discrepancy, SHALL remain visible in this registry as a recorded defect and SHALL block the affected lifecycle transition until explained and corrected; that record SHALL NOT name a private identifier, title, path, or dependency, this clause extending to titles, paths, and dependencies the identifier bar REG-R004 holds, as its own addition.
- REG-R003: Registry changes SHALL preserve historical discoverability, generated-state parity, public/private boundaries, and explicit approval evidence.
- REG-R004: This Draft SHALL NOT promote documents, create authority, expose private identifiers, or replace the Architect's approval.
The seven interpretation cases below show how these clauses read in practice.
- Conforming: A registry claim is reconciled against the source document itself, with identifier, path, status, and dependencies all matching.
- Prohibited: Registration is treated as ratification; a row proves existence and recorded status, never authority.
- Boundary: A reserved identifier is recorded as reserved: it prevents collisions without implying content, scope, or approval.
- Failure: A mismatch between registry and source blocks promotion until the divergence is explained and corrected.
- Loophole: A stale path or renamed file hides behind an unchanged row; the registry must follow every move in the same change.
- Misuse: The registry is used to expose private records by enumerating what should not be publicly listed.
- Care-control: Registry stewardship protects continuity, privacy, and correction, and its history appends rather than rewrites.
The tellings of the clauses¶
This non-normative section gives each clause of this document its telling: the clause, quoted exactly as it stands above with its cross-reference links reduced to their plain text, and one paragraph on what the clause means, why it exists, and how it assures that what it orders is done, not done, adhered to, followed, or protected. A telling describes its clause and never becomes it: the clause's own words govern wherever a telling and its clause could be read differently, and nothing in this section adds to, narrows, or amends any requirement.
REG-R001: Registry review SHALL reconcile identifier, title, path, status, authority, publication state, and dependency edges against the current source documents.
Review here is reconciliation, not rereading: the clause requires registry review to check seven properties of each entry, the identifier, the title, the path, the status, the authority, the publication state, and the dependency edges, against the current source documents rather than against the registry's own memory of them. The registry's opening account states the stake: a registry that cannot say where a thing stands has no business saying what it is, and the map keeps exploration honest only while its rows match the ground. The conforming case shows the practice, a registry claim reconciled against the source document itself with identifier, path, status, and dependencies all matching, and the loophole case names the failure this prevents: a stale path or renamed file hiding behind an unchanged row, which the registration rules answer by requiring relocation to update the registry in the same change set. Because the seven properties and the source of truth are both named, the review becomes checkable property by property: a review that skipped one of the seven, or that reconciled rows against the registry itself instead of the current sources, fails the clause's reconciliation requirement, and a divergence found is a finding rather than a quirk.
REG-R002: A missing, duplicate, moved, or stale entry, or a public/private boundary discrepancy, SHALL remain visible in this registry as a recorded defect and SHALL block the affected lifecycle transition until explained and corrected; that record SHALL NOT name a private identifier, title, path, or dependency, this clause extending to titles, paths, and dependencies the identifier bar REG-R004 holds, as its own addition.
A found defect gets two duties and one bar. The clause names five defect kinds, a missing, duplicate, moved, or stale entry, and a public/private boundary discrepancy, and requires each to remain visible in this registry as a recorded defect and to block the affected lifecycle transition until explained and corrected: both the explanation and the correction, not either alone. The failure case states the first half in practice, a mismatch between registry and source blocking promotion until the divergence is explained and corrected, and the misuse case supplies the bar's reason: a registry turned into an instrument for exposing private records by enumerating what should not be publicly listed. So the clause prohibits the defect record from naming a private identifier, title, path, or dependency, the clause saying in its own words that it extends, as its own addition, the identifier bar REG-R004 holds to titles, paths, and dependencies. Because the clause binds, the affected lifecycle transition remains blocked until the defect is explained and corrected; concealment of the defect or naming a private identifier, title, path, or dependency in its record breaches the clause.
REG-R003: Registry changes SHALL preserve historical discoverability, generated-state parity, public/private boundaries, and explicit approval evidence.
The clause requires every registry change to preserve four things: historical discoverability, generated-state parity, public/private boundaries, and explicit approval evidence. Historical discoverability keeps the registration rules' own promise that superseded or revoked materials remain historically discoverable, and the care-control case gives it a voice: registry stewardship protects continuity, privacy, and correction, and its history appends rather than rewrites. Generated-state parity is another named preservation requirement. The public/private boundary restates the purpose section's limit, a registry containing no private document identifiers, titles, paths, or dependencies, with the misuse case showing what crossing it looks like. Registry changes preserve explicit approval evidence rather than losing it to drift, in step with the rule that no document becomes canonical without the Architect's approval. Because the four preservations are named, a registry change can be audited against each in turn: a change that erases history, lets the generated state diverge, leaks across the boundary, or fails to preserve approval evidence is refusable on this clause, whatever else it got right.
REG-R004: This Draft SHALL NOT promote documents, create authority, expose private identifiers, or replace the Architect's approval.
The registry closes with four prohibitions on this Draft: this Draft promotes no document, creates no authority, exposes no private identifier, and replaces no approval of the Architect. The prohibited case states the first two plainly: registration treated as ratification is the misreading, because a row records status but does not create authority, a reserved row does not even prove a document exists, and the status model places promotion in lifecycle states the registry records rather than confers. Registration rule eight carries the fourth limb in the rules' own words, no document becoming canonical until approved by the Architect and published with required provenance, and the third limb turns the purpose section's boundary, no private identifiers, into a prohibition the Draft applies to itself. The clause exists because an authoritative-looking table is precisely where unearned status would be laundered: a row added, a status word changed, and a document appears promoted without anyone having decided it. Because the clause binds, the Draft can be checked for promotion, creation of authority, exposure of private identifiers, or replacement of the Architect's approval; a row does not itself supply promotion, authority, or that approval.
Where this document sits¶
- Identifier: REG-1
- Status: Draft
- Authority: CONAN-P0
- Approved by: The Architect
- Depends on: CONAN-P0
- Depended on by: INTEL-15, WEB-LANDING-1, WEB-INDEX-1, WEB-ABOUT-1, WEB-GUIDE-1, WEB-EDITIONS-1, WEB-LEDGER-1, WEB-AUTHORITY-1, WEB-DEPENDENCY-1
- Maps: Authority Map, Dependency Map
This block is generated from the archive's own records when the site is built. It records position only and creates no authority.