Structural Records Directory

Charter

• Purpose: identify structural record systems and route readers to their authoritative sources.
• Authority posture: derivative and navigational only.
• Source of truth: each member's own settled source, manifest, contract, or public surface.
• Master Index subordination: this directory does not replace the Master Index or determine current canonical state.
• Lifecycle posture: status is reported only when directly derived from an authoritative settled source.

Membership Rule

A system belongs here when Quasantum depends upon it to record, locate, classify, reconstruct, govern, publish, verify, or structurally explain some aspect of Quasantum itself, and when that system has a distinct repository-settled responsibility.

Ordinary content artifacts, individual conversations, individual procedural records, publication objects, images, and incidental support files are excluded unless the object itself functions as a repository-settled structural system of record.

Initial Members

• Governance / Continuity

  Master Index

  Purpose: records repository-settled structural and continuity state.

  Authority posture: authoritative within its Master Index jurisdiction.

  Canonical source: /canon/master-index.json

  Public surface: /apex/master-index.html

  Boundary: does not serve as the full artifact discovery catalog or replace specialized source systems.

• Operational Contract

  Operational Topology

  Purpose: records the settled relationship among repository source, public surfaces, runtime, production, and predecessor history.

  Authority posture: authoritative for operational topology.

  Canonical source: /canon/operational-topology.v1.json

  Public surface: /apex/atlas/operational-topology

  Boundary: does not index every structural record system by responsibility.

• Orientation

  Atlas

  Purpose: orients readers across repository surfaces, traversal modes, topology, and lineage.

  Authority posture: orientational unless a linked settled contract governs a specific claim.

  Canonical source: /apex/atlas/atlas-manifest.json

  Public surface: /apex/atlas/

  Boundary: remains the broad orientation district; this directory remains a narrower record-system guide.

• Retrieval / Classification

  Card Catalog

  Purpose: exposes the static drawer and retrieval ontology for artifact approach.

  Authority posture: authoritative for the settled card-catalog matrix; derivative for generated drawer pages.

  Canonical source: /apex/canon/card-catalog-matrix.v1.json

  Public surface: /apex/card-catalog.html

  Boundary: does not determine current canonical state or publication authority.

• Artifact Placement

  Corpus Position Index

  Purpose: maps public artifacts to Field placement, Card Catalog memberships, retrieval resonance, and matrix coordinates.

  Authority posture: derivative from settled matrix, catalog, field, and projection sources.

  Machine-readable source: /apex/canon/artifact-corpus-position-index.v1.json

  Public surface: /apex/corpus-position.html

  Boundary: does not treat retrieval resonance as probability, maturity, or achieved semantic state.

• Artifact Discovery

  Artifact Index / Artifact Catalog

  Purpose: exposes repository-projected artifact pages and machine-readable adjacency for discovery.

  Authority posture: derivative discovery surface from repository-projected artifact data.

  Machine-readable source: /apex/canon/artifact-adjacency.json

  Public surface: /apex/artifacts/

  Boundary: does not govern artifact classification or Master Index state.

• Field Registry

  Field Definitions

  Purpose: records the public Field sequence and field-level artifact placement substrate.

  Authority posture: derivative from field-generation and public corpus-position machinery.

  Canonical source: /apex/canon/field.v2.json

  Public surface: /quasantum/#/q/fields

  Boundary: does not replace Card Catalog drawer membership or artifact adjacency.

• Relation Records

  Relation Topology

  Purpose: records artifact-centered relation neighborhoods and runtime relation traversal surfaces.

  Authority posture: static adjacency is a public projection; runtime graph views are exploratory.

  Canonical source: /apex/canon/artifact-adjacency.json

  Public surface: /quasantum/#/graph/domain8

  Boundary: does not assert semantic importance from graph position alone.

• Publications

  Publication Index

  Purpose: records curated publication streams across Core, Foundry, Serial, Essays, and Notes.

  Authority posture: authoritative within the publications canon.

  Canonical source: /canon/publications-index.json

  Public surface: /apex/works.html

  Boundary: does not catalog raw artifact substrate or decide artifact classification.

• Corpus Projection

  Canonical Corpus Manifests

  Purpose: expose the public corpus and thread-catalog projections used by static and runtime surfaces.

  Authority posture: repository-projected corpus records; source-specific authority remains with the generating machinery and settled files.

  Machine-readable sources: /artifacts/thread-corpus.json, /apex/canon/thread-catalog.json

  Public surface: /apex/artifacts/

  Boundary: does not replace Master Index continuity state or publication canon.

• Governance Records

  Governance / Architecture Registers

  Purpose: preserve policies, dispositions, architecture decisions, gates, registers, and execution authorizations.

  Authority posture: authoritative only where a record has been adopted within its stated governance scope.

  Canonical source: /governance/README.md

  Public surface: Master Index orientation

  Boundary: individual records are not separately listed here unless they become systems of record.

• Procedural Continuity

  Procedural Record Systems

  Purpose: preserve closure, custody, continuity, and thread-operation records as procedural evidence classes.

  Authority posture: evidentiary and procedural within each record's stated scope.

  Canonical source: thread-closure protocol

  Public surface: transition archaeology record

  Boundary: this directory names the record class, not every CPR, TPR, companion, or custody object.

• Discovery / Routes

  Public Route Inventories

  Purpose: expose crawler-readable route discovery for public static surfaces, artifacts, and gallery items.

  Authority posture: discovery only.

  Canonical source: /sitemap.xml

  Public surface: /apex/sitemap.xml

  Boundary: sitemap membership is not governance, classification, or publication-state adjudication.

• Verification

  Verification / Baseline Registers

  Purpose: record validation baselines, tripwires, residuals, and publication or topology verification evidence.

  Authority posture: evidentiary within the scope of each settled register or report.

  Canonical source: standing tripwires register

  Public surface: repository state notes

  Boundary: reports evidence checks; they do not advance lifecycle state by themselves.

Transition Provenance

This public district supersedes the former Threshold Queue / Backlog Queue card and page identity. The former queue language is preserved in archaeology where it records historical fact, but it no longer survives as a live public district identity.