Atlas  →  Operational Topology

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.

Repository-Settled Contract

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

State Movement

  1. ImplementationRODZAKI.github.io/apps/quasantum
  2. App build outputdist/quasantum
  3. Tracked public productquasantum/
  4. Whole-site stagingdist/
  5. ProductionCloudflare Pages quasantum-poc

Application Boundary

Domain 8 Distinctions

Operational Entry

Workstation Storage Boundary

← Return to Atlas Topology JSON → Governing Contract → Return to Threshold