Operational Topology One Quasantum
One Quasantum; one governed repository root for current operations; preserved predecessor history remains historical and non-authoritative.
This page explains the topology for human and digital visitors. The governing machine-readable contract is operational-topology.v1.json. Atlas orients; the repository-settled contract governs.
Architecture Above Orientation Modes
Operational Topology is not a fifth traversal mode. It is the architectural self-description that governs how the four Atlas modes, the Threshold public realm, the Quasantum app, Cloudflare production, and workstation storage boundaries stay distinct and interoperable.
Principal Lobes
-
Current Implementation Authority
RODZAKI.github.io
The governed repository root for current Quasantum operations. Application source lives at
apps/quasantum. -
Application Source
apps/quasantum
The current Quasantum application source and materialization boundary inside the canonical repository.
-
Legacy Fossil
rodzaki-quasantum
Historical predecessor/sibling implementation only. It is preserved outside active project discovery and is not current implementation authority.
-
Gateway
Threshold
The public landing environment. Threshold opens onto Publications, Magazine, Gallery, Master Index, Structural Records Directory, 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
- ImplementationRODZAKI.github.io/apps/quasantum
- App build outputdist/quasantum
- Tracked public productquasantum/
- Whole-site stagingdist/
- 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:preflightDerives 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:workflowPrints the governed sequence from implementation through validation, materialization, settlement, publication, verification, and evidence deposition.
Workstation Storage Boundary
-
C: system and required state
Durable workstation identity
Windows, installed applications, the user profile, governed repositories, credentials, and other required state remain on C:. C: is not the preferred surface for heavy publication scratch.
-
D: operational capacity
D:\q publication workspace
High-capacity reproducible scratch, build, staging, browser cache, and disposable publication work roots prefer short D: paths, with Git safe.directory and long-path compatibility declared by the publication machinery.