eduKateSG

VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Next useful routeCanonical hubHELP

(T) Hong Kong City OS — Z0–Z6 Canonical Spine (HKG.HKG)

CivOS-CANON v1.0

Summary

This is the single canonical CivOS reference for Hong Kong. Same executable spine as your other city instances—so Hong Kong becomes comparable in Phase, TTC, corridor propagation, and repair routing.

Rule: Exactly ONE Z5 hub page for Hong Kong. All child pages must declare PLACE_ID × LANE × Z × ORGAN and link back here.

Identity Block (Frozen)

SPEC_ID: CIVOS.PLACE.HKG.HKG.SPINE.v1.0
PLACE:
  COUNTRY: Hong Kong (SAR)
  ISO3: HKG
  PLACE_ID: HKG.HKG
  CANONICAL_NAME: Hong Kong
  ALIASES: HK | Hong Kong SAR

Z6 — Organisation Layer (Ownership Index)

Z6 answers: who owns / operates / controls key organs.

Z6.ORGS (minimum viable index)
HKG.HKG.TRANSPORT:
  - Transport Department (policy / system oversight)
  - MTR Corporation Limited (rail backbone)
HKG.HKG.FOODWATER:
  - Water Supplies Department (WSD)
HKG.HKG.SECURITY:
  - Hong Kong Police Force (HKPF)
HKG.HKG.HEALTH:
  - Hospital Authority (public hospitals)

Authoritative anchors:

Z5 — City Hub (System Overview)

Z5.HUB:
LANES:
  GOV | HEALTH | TRANSPORT | FOODWATER | SECURITY | EDUCATION | PRODUCTION
CORE DASHBOARD:
  - Phase (P0–P3) by lane
  - TTC (Time-to-Core) by lane
  - Buffer margins (ICU headroom, corridor uptime, days-of-cover)
  - Backlog slopes (health access, maintenance)
  - Redundancy index (routes, staffing, suppliers)
  - Shock log (rolling)

City archetype note: Hong Kong is extreme corridor coupling (high density + cross-harbour chokepoints). TTC shrinks fastest when rail/cross-harbour corridors or hospital intake saturate.

Z4 — Districts / Subregions (Execution Geography)

Z4 is where “local stress” shows up first.

Z4.AREAS:
  - Hong Kong Island districts
  - Kowloon districts
  - New Territories districts
  - Outlying islands (interface zones)

Z3 — Corridors & Critical Networks

Z3 answers: which arteries move load.

Z3.CORRIDORS:
TRANSPORT:
  - Rail spine (MTR) + interchange megastations
  - Cross-harbour links (tunnels/rail crossings)
  - Airport + port logistics interfaces
FOODWATER:
  - Water treatment + trunk distribution mains (WSD oversight)
  - Sewage treatment & drainage (interface organ; see DSD facilities)
HEALTH:
  - Ambulance corridors → cluster hospitals (HA network)
SECURITY:
  - Command corridors + critical site protection
  - Marine policing corridors (harbour/islands interface)
  • Rail backbone ownership clarified via Transport Department + MTRCL (td.gov.hk)
  • Example of sewage-treatment critical infrastructure (DSD facility tour)
  • HKPF marine organisation example (harbour/islands corridor policing)

Z2 — Institutions

Z2 answers: who executes day-to-day.

Z2.INSTITUTIONS:
HEALTH:
  - Hospital clusters + A&E intake (Hospital Authority)
TRANSPORT:
  - Control centres, depots, stations (MTR)
FOODWATER:
  - Treatment works, pumping stations, customer service + emergency repairs (WSD)
SECURITY:
  - District commands, specialist units (HKPF)

Z1 — Service Catchments

Z1 answers: who depends on what.

Examples:

  • station catchments around interchange nodes
  • hospital catchments (cluster coverage)
  • water pressure zones / service zones
  • district policing coverage

Z1 drift shows up as uneven overload before city-wide failure.

Z0 — Ground Nodes (Reality)

Z0 answers: what actually broke (the “visible symptom”).

Examples:

  • megastation congestion event (crowding)
  • localized water suspension / pressure drop (WSD notices) (wsd.gov.hk)
  • A&E surge / queue spillover (HA intake pressure) (ha.org.hk)
  • district incident spike requiring rapid routing (HKPF) (police.gov.hk)

Rule: Z0 symptoms ≠ root cause. Root cause typically sits at Z2 staffing/backlog or Z3 corridor constraints.

Hong Kong Failure Mode Trace (Canonical)

Z0 local overload (station / A&E / water incident)
→ Z2 institutional strain (staffing + backlog + dispatch)
→ Z3 corridor congestion (cross-harbour + rail spine coupling)
→ Z5 Phase drops (Transport/Health coupling)
→ TTC shortens under peak load
→ multi-lane cascade if stop-loss delayed

Repair Routing (Entry Points)

  1. Identify Lane
  2. Identify Z-level
  3. Measure Phase + TTC + Buffer
  4. Trigger router:
  • GOV Router
  • HEALTH Router
  • TRANSPORT Lane Directory
  • FOOD+WATER Lane Directory
  • SECURITY Lane Directory
  1. Apply stop-loss
  2. Retest until Phase stabilizes

Expansion Rules (Anti-cannibal)

HKG.EXPANSION_RULES:
1. Only ONE Z5 hub page exists (this spine).
2. All district pages are Z4 children.
3. All deep dives must declare:
   PLACE_ID × LANE × Z × ORGAN
4. CivOS primitives never redefined locally.
5. IDs frozen; version forward only.

One-paragraph Canonical Hong Kong Definition (Reusable)

Hong Kong City OS is the CivOS instantiation of Hong Kong as a high-density, corridor-coupled system mapped across Z0–Z6, anchoring ownership (Transport Department + MTRCL, Water Supplies Department, Hong Kong Police Force, Hospital Authority) and standardizing how corridor overload propagates so repairs can be routed before Time-to-Core collapses under peak-load and cross-harbour coupling. (td.gov.hk)

Recommended Internal Links (Spine)

Start Here for Lattice Infrastructure Connectors