(AA) Chicago City OS — Z0–Z6 Canonical Spine (USA.CHI)

CivOS-CANON v1.0

Summary

This is the single canonical CivOS reference for Chicago. Same executable spine as your other major cities—tuned to Chicago’s archetype: rail + lake/river + regional transit governance + stormwater/wastewater coupling.

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

Identity Block (Frozen)

			
SPEC_ID: CIVOS.PLACE.USA.CHI.SPINE.v1.0
PLACE:
  COUNTRY: United States
  ISO3: USA
  PLACE_ID: USA.CHI
  CANONICAL_NAME: Chicago (Metro Core)
  ALIASES: Chicago | City of Chicago | Chicagoland (interface)

		

Z6 — Organisation Layer (Ownership Index)

Z6 answers: who owns / operates / controls the city’s organs.

			
Z6.ORGS (minimum viable index)
USA.CHI.GOV:
  - City of Chicago (Mayor + City departments)
USA.CHI.FOODWATER (Potable Water):
  - Chicago Department of Water Management (DWM) (purification + transmission of potable water)  [city dept]
USA.CHI.FOODWATER (Wastewater/Stormwater):
  - Metropolitan Water Reclamation District of Greater Chicago (MWRD) (wastewater + stormwater in Cook County)  (:contentReference[oaicite:1]{index=1})
USA.CHI.TRANSPORT:
  - Chicago Transit Authority (CTA) (bus + rail)  (:contentReference[oaicite:2]{index=2})
USA.CHI.HEALTH:
  - Cook County Health (public health system)  (:contentReference[oaicite:3]{index=3})
USA.CHI.SECURITY:
  - Publish as Z6 add-on page (CPD + CFD + County Sheriff interfaces) once you want the agency blocks locked.

		

Archetype note: Chicago is “water + transit” coupled: failures propagate via corridor congestion and stormwater/wastewater load into Health.

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
  - Corridor uptime (CTA lines + key interchanges)
  - Water reliability (potable) + wastewater/stormwater capacity margin
  - ICU/ED intake latency + staffing headroom
  - Shock log (extreme rain, heat, winter storms)

		

Z4 — Subregions (Execution Geography)

			
Z4.AREAS:
  - Chicago community areas / wards (city execution geography)
  - Cook County interface zones (metro spillover)

Z3 — Corridors & Critical Networks

			
Z3.CORRIDORS:
TRANSPORT:
  - CTA rail trunk lines + interchange megastations (corridor propagation)  (:contentReference[oaicite:4]{index=4})
FOODWATER:
  - Lake Michigan intake → treatment → trunk distribution mains (DWM)  (:contentReference[oaicite:5]{index=5})
  - Wastewater/stormwater trunk system + flood abatement corridors (MWRD)  (:contentReference[oaicite:6]{index=6})
PRODUCTION / LOGISTICS (interface):
  - Port / lake-river-rail freight interfaces (publish as Z3 add-on)

		

Rule: In Chicago, Z3 water corridors can dominate failure propagation during heavy rain events (FoodWater ↔ Health coupling).

Z2 — Institutions

			
Z2.INSTITUTIONS (examples)
TRANSPORT:
  - Control centers, depots, maintenance bases (CTA ecosystem)  (:contentReference[oaicite:7]{index=7})
FOODWATER:
  - Water treatment plants + pumping stations (DWM)  (:contentReference[oaicite:8]{index=8})
  - Wastewater treatment plants + stormwater assets (MWRD)  (:contentReference[oaicite:9]{index=9})
HEALTH:
  - County hospitals/clinics + emergency intake hubs (Cook County Health)  (:contentReference[oaicite:10]{index=10})

		

Z1 — Service Catchments

Examples:

CTA station catchments around major interchanges
hospital catchments (county system + private interfaces)
water pressure zones / service zones
flood-risk catchments (stormwater load basins)

Z0 — Ground Nodes (Reality)

Examples:

interchange disruption → citywide corridor congestion
extreme rain → wastewater/stormwater exceedance pressure → Health load spike (MWRD coupling) ((mwrd.org))
localized water main issue / boil notice dynamics (DWM domain) ((chicago.gov))
ED surge → intake overflow (Cook County Health domain) ((Cook County Health))

Rule: Z0 symptoms ≠ root cause (root cause usually Z2 staffing/maintenance or Z3 corridor constraints).

Chicago Failure Mode Trace (Canonical)

			
Z0 local disruption (transit node / stormwater event / ED surge)
→ Z2 institutional overload (staffing + maintenance debt)
→ Z3 corridor congestion (transit + water coupling)
→ Z5 Phase drop (Transport/FoodWater/Health)
→ TTC shortens under peak load
→ cascade if stop-loss delayed

		

Expansion Rules (Anti-cannibal)

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

		

One-paragraph Canonical Chicago Definition (Reusable)

Chicago City OS is the CivOS instantiation of Chicago as a transit-and-water-coupled metropolitan system mapped across Z0–Z6, anchoring ownership (City of Chicago Department of Water Management for potable water, MWRD for wastewater/stormwater, CTA for transit, Cook County Health for public healthcare) and standardizing how corridor and water-load failures propagate so repairs can be routed before Time-to-Core collapses under peak-load and extreme-weather shocks. (chicago.gov)