Operational Topology One Quasantum

Principal Lobes

• Implementation Authority

  rodzaki-quasantum

  The application implementation repository. It is the source of bounded app changes before they cross into publication.

  C:\Users\david\Projects\rodzaki-quasantum

• Publication Authority

  RODZAKI.github.io

  The whole-site publication repository. It governs static/public surfaces, evidence, the app publication copy, and Cloudflare publication.

  apps/quasantum → quasantum/ → Cloudflare

• Gateway

  Threshold

  The public landing environment. Threshold opens onto Publications, Magazine, Gallery, Master Index, Threshold Queue, Archive, Atlas, and the Quasantum Cognitive Engine.

• Orientation District

  Atlas

  Atlas makes the public realm and repository relationships legible. It does not replace governed surfaces or runtime authority.

• Runtime Application

  Quasantum Cognitive Engine

  The JavaScript application for fields, threads, artifacts, graph traversal, and operational work. Its server-visible mount is /quasantum/; its browser routes live after #/.

• Operational Workbench

  Domain 8

  The production-verified Domain 8 manifold: steward invocation, inquiry, corpus retrieval, relation-aware synthesis, provenance, preservation, closure, and clean reinvocation.

State Movement

1. Implementationrodzaki-quasantum
2. Publication source copyapps/quasantum
3. App build outputdist/quasantum
4. Tracked public productquasantum/
5. Whole-site stagingdist/
6. ProductionCloudflare Pages quasantum-poc

Application Boundary

• Server-visible mount

  /quasantum/

  Cloudflare, byte verification, and crawlers see this app shell and its assets. They do not see the browser fragment as a server route.

• Browser route layer

  #/

  Routes such as #/q/topology and #/graph/domain8 are React HashRouter identities. Functional verification is required for these workflows beyond deployment byte parity.

• Crawler-readable relation surface

  artifact-adjacency.json

  Static artifact-centered relation neighborhoods. This is the public repository-projected edge surface for crawlers and tools.

Domain 8 Distinctions

• Current Domain 8

  Operational Workbench

  Current production-verified workbench over the static public corpus projection and adjacency surface. It is not identical to the historical field manifestations.

• Surviving field manifestation

  7ac54512 / {([8])}

  A UUID field associated with the Domain 8 lineage. Production home currently exposes it as a personal field with 61 artifacts. Direct detail-route observation remains qualified by a Supabase runtime fetch issue and is not collapsed into the Domain 8 workbench.

• Historical route

  Topology (paused)

  Sealed at L4 / Master Index 5.1.1 and explicitly not the current relation authority. It points to runtime fields and static adjacency JSON instead.

Operational Entry

• Preflight

  npm run topology:preflight

  Derives expectations from the topology contract and checks whether the repositories, boundaries, publication machinery, public corpus projections, Python runtime, and routing facts are coherent enough for ordinary work to proceed.

• Workflow

  npm run topology:workflow

  Prints the governed sequence from implementation through validation, materialization, settlement, publication, verification, and evidence deposition.