00 / 00

BOOKCASE

7 MIN READ•ARCHIVE

Bibliotheca Governance

Purpose: Rules for maintaining the knowledge governance system. What goes where, what gets fixed, what gets preserved. Created: 2026-05-20 (Bibliotheca stabilization pass 3) Status: Stable — updated as governance rules evolve

Core Principle

If it is knowledge, it belongs in Bibliotheca.

Bibliotheca is the single source of truth for all project knowledge. Runtime code, operational docs, and app-specific configuration live outside Bibliotheca in their respective apps/ directories.

Layer Map

| Layer | Location | Role | Authority | |-------|----------|------|-----------| | Philosophy | bibliotheca/philosophy/ | Canonical beliefs — what the project holds true | Authoritative | | ContinuityGate | /continuitygate/ | Active reconstruction runtime — how to re-enter the room | Operational | | ContinuityGateHistory | bibliotheca/continuitygatehistory/ | Deep historical continuity archive — archaeology, evolution, accumulated continuity history | Archival | | Atlas | bibliotheca/atlas/ | Conceptual topology — maps the territory, interprets structure | Interpretive | | Projects | bibliotheca/projects/ | Project-specific docs, research, and historical snapshots | Historical | | Research | bibliotheca/research/ | Active research artifacts and findings | Exploratory | | Observatory | bibliotheca/observatory/ | Runtime observation records and archive | Archival | | Experiments | bibliotheca/experiments/ | Experiment logs and results | Temporary | | Field Notes | bibliotheca/field-notes/ | Operator observations and qualitative notes | Informal | | Findings | bibliotheca/findings/ | Stabilized discoveries from research | Reference | | Archive | bibliotheca/archive/ | Historical records, retired paths, legacy docs | Permanent |

What Goes Where

Philosophy (bibliotheca/philosophy/)

  • Canonical belief statements
  • Stable, authoritative documents
  • Documents that should survive all refactors
  • Do NOT put: research findings, operational handoffs, conceptual maps

ContinuityGate (/continuitygate/)

  • Active reconstruction runtime — always-read-first entry surface
  • Onboarding lore / first orientation (elderscroll.md)
  • Operational behavior + governance layer (avatar.md)
  • Compressed institutional principles (manifesto.md)
  • Latest stable reconstruction checkpoint (bonfire.md)
  • High-signal traversal routes (fasttravel.md)
  • Continuity ritual and re-entry protocol (continuitygate.md)
  • Root ecosystem map (nufikri.xyz.md)
  • Do NOT put: expanded conceptual maps, research findings, philosophy archives, deep historical archaeology
  • Naming convention: Uses world-building/game-language metaphors for memorability and reconstruction clarity

ContinuityGateHistory (bibliotheca/continuitygatehistory/)

  • Deep historical continuity archive
  • Accumulated continuity history and evolution
  • Legacy handoffs and archaeology
  • Historical continuity research
  • Do NOT put: active reconstruction surfaces, runtime operational docs

Atlas (bibliotheca/atlas/)

  • Conceptual topology and interpretive maps
  • Terminology definitions with emotional/architectural meaning
  • Relationship diagrams between concepts
  • Do NOT put: re-entry protocols, canonical philosophy, operational handoffs

Projects (bibliotheca/projects/)

  • Project-specific documentation
  • Historical snapshots of app docs
  • Research docs scoped to a specific project
  • Do NOT put: active operational docs (keep in apps/), cross-project research

Research (bibliotheca/research/)

  • Active research artifacts
  • Cross-project research findings
  • Papers, theories, and frameworks
  • Do NOT put: project-specific docs, operational handoffs

Archive (bibliotheca/archive/)

  • Historical records that should not be deleted
  • Retired path registries (e.g., HISTORICAL-PATHS.md)
  • Legacy docs preserved for reference
  • Do NOT put: active documents, operational docs, research findings

Reference Classification

When encountering a reference to a path, classify it using this framework:

| Reference Type | Action | Example | |---------------|--------|---------| | Active/broken navigation path | FIX | docs/atlas/continuity-philosophy.md → bibliotheca/atlas/continuity-philosophy.md | | Historical prose in research docs | PRESERVE | "The entrypoint/ directory was created to..." | | Archival reference | PRESERVE | References in bibliotheca/archive/ files | | Intentional historical mention | PRESERVE | "Previously at root docs/research/" | | Prose references (Bibliotheca/ with capital B) | PRESERVE | "The Bibliotheca/ directory contains..." | | Self-referencing docs/research/ paths | PRESERVE | Research doc referencing its own location |

Document Types

Canonical

  • Authoritative source of truth
  • Lives in bibliotheca/philosophy/
  • Example: CANONICAL-CORE-PHILOSOPHY.md
  • Do NOT edit without explicit philosophical consensus

Pointer

  • Lightweight doc that redirects to canonical source
  • Lives in any Bibliotheca layer
  • Example: bibliotheca/projects/teteh-lab/docs/research/BIG-BRAIN-LIBRARY.md
  • Keep minimal — just enough to redirect

Historical Snapshot

  • Preserved copy of a document at a point in time
  • Lives in bibliotheca/projects/ or bibliotheca/archive/
  • Example: bibliotheca/projects/api-lab/docs/imported-from-tarot-app/HANDOFF.md
  • Do NOT edit — preserve as-is

Operational Surface

  • Active document used for runtime reconstruction
  • Lives in /continuitygate/ or apps/
  • Example: /continuitygate/continuitygate.md
  • Update as project state changes

Governance Rules

Rule 1: One concept, one location

Each concept lives in exactly one Bibliotheca layer. If a concept spans layers, document the relationship in both locations with cross-references.

Rule 2: Cross-references must be valid

All cross-references between Bibliotheca documents must point to existing files. Broken references should be fixed during stabilization passes.

Rule 3: Preserve historical context

Do not rewrite historical prose to update path references. Historical documents document what existed at the time of writing. Update only active navigation paths.

Rule 4: Archive, don't delete

When retiring a path or document, move it to bibliotheca/archive/ and update HISTORICAL-PATHS.md. Do not delete knowledge — it may be needed for continuity reconstruction.

Rule 5: Label document types

Every Bibliotheca document should have a header indicating its type (canonical, pointer, historical snapshot, operational surface) and its layer.

Rule 6: Stabilization passes

Periodic stabilization passes should:

  1. Audit cross-references for broken paths
  2. Harden boundaries between layers
  3. Update HISTORICAL-PATHS.md with newly retired paths
  4. Verify TypeScript compilation in apps/
  5. Produce a stabilization report

Boundary Rules

Atlas vs ContinuityGate

  • Atlas = conceptual map. Expanded, interpretive, topological.
  • ContinuityGate = operational entry surface. Compressed, actionable, re-entry-focused.
  • Atlas documents may reference ContinuityGate documents, but they are not part of the reconstruction protocol.
  • Atlas is for understanding the territory; ContinuityGate is for entering the room.

Atlas vs Philosophy

  • Atlas = the conceptual map. Expanded, interpretive, topological.
  • Philosophy = the beliefs themselves. Compact, stable, authoritative.
  • atlas/continuity-philosophy.md maps the conceptual territory of the philosophy — it explains relationships, provides emotional and architectural meaning, and connects beliefs to research. It is not a duplicate — it is an interpretation layer.

ContinuityGate vs Philosophy

  • ContinuityGate = the reconstruction protocol. "This is how you re-enter the room."
  • Philosophy = the stable set of beliefs. "This is what we believe."
  • CORE-PHILOSOPHY.md in ContinuityGate is the compressed worldview used for continuity reconstruction. It is not a duplicate of the canonical philosophy — it is a different document serving a different purpose (re-entry posture vs canonical belief).

Bibliotheca vs Apps

  • Bibliotheca = knowledge governance system. All project knowledge.
  • Apps = runtime code, operational docs, app-specific configuration.
  • Operational docs that are actively used in development (README, HANDOFF, AGENTS, CLAUDE) stay in apps/.
  • Knowledge docs that are not runtime-operational belong in Bibliotheca.

Maintenance

Adding a new document

  1. Determine which layer it belongs to (see Layer Map)
  2. Add a header with type and layer
  3. Add cross-references to related documents
  4. Update HISTORICAL-PATHS.md if retiring an old path

Updating an existing document

  1. Preserve the document type header
  2. Update cross-references if paths have changed
  3. Do not rewrite historical prose
  4. Add a stabilization note if the update is part of a pass

Retiring a path

  1. Move content to its new location
  2. Update bibliotheca/archive/HISTORICAL-PATHS.md
  3. Run a cross-reference audit to fix broken references
  4. Remove the old path only after all references are updated

Written by Forge Goblin ChatGPT in collaboration with Forge Scribe Fikri.

RETURN