eduKate Singapore

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

(X) São Paulo City OS — Z0–Z6 Canonical Spine (BRA.SAO)

CivOS-CANON v1.0

Summary

This is the single canonical CivOS reference for São Paulo. Same executable spine as your other major cities—so São Paulo becomes directly comparable in Phase, TTC, corridor propagation, and repair routing.

Rule: Exactly ONE Z5 hub page for São Paulo. All child pages must declare PLACE_ID × LANE × Z × ORGAN and link back here.

Identity Block (Frozen)

SPEC_ID: CIVOS.PLACE.BRA.SAO.SPINE.v1.0
PLACE:
  COUNTRY: Brazil
  ISO3: BRA
  PLACE_ID: BRA.SAO
  CANONICAL_NAME: São Paulo (City / Metro core)
  ALIASES: Sao Paulo | São Paulo

Z6 — Organisation Layer (Ownership Index)

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

Z6.ORGS (minimum viable index)
BRA.SAO.GOV:
  - Prefeitura de São Paulo (City Government)
BRA.SAO.TRANSPORT:
  - SPTrans (bus system management + corridor monitoring)
  - Metrô (Companhia do Metropolitano de São Paulo) (metro operator)
BRA.SAO.FOODWATER:
  - Sabesp (water & sanitation company for the wider system interface)
(BRA.SAO.SECURITY / BRA.SAO.HEALTH / BRA.SAO.EDUCATION / BRA.SAO.PRODUCTION):
  - Publish as Z6 add-on pages after Z5 hub is live (to lock exact agencies/operators cleanly).

Authority anchors: Prefeitura (Prefeitura de São Paulo), SPTrans (sptrans.com.br), Metrô (metro.sp.gov.br), Sabesp (sabesp.com.br)

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 (maintenance, health access, justice)
  - Redundancy index (corridors, staffing, suppliers)
  - Shock log (rolling)

City archetype note: São Paulo is mega-corridor + metro/bus coupling: TTC collapses fastest when high-volume commuting corridors choke and spill into Health/Production.

Z4 — Subregions (Execution Geography)

Z4.AREAS:
  - City districts / subprefeituras (publish as Z4 children later)
  - High-load commuter basins (corridor catchments)

Z3 — Corridors & Critical Networks

Z3 answers: which arteries move load.

Z3.CORRIDORS:
TRANSPORT:
  - Bus corridors + citywide bus routing layer (SPTrans)
  - Metro trunk lines + interchange stations (Metrô)
  - Road spines (interfaces; publish Z3 add-on later)
FOODWATER:
  - Water sourcing + treatment + trunk distribution (Sabesp interface)

Corridor monitoring/ops anchor (SPTrans) (sptrans.com.br)
Metro ops anchor (Metrô) (metro.sp.gov.br)
Water/sanitation interface anchor (Sabesp) (sabesp.com.br)

Z2 — Institutions

Z2 answers: who executes day-to-day.

Z2.INSTITUTIONS (examples)
TRANSPORT:
  - Bus operations control, depots, corridor enforcement nodes (SPTrans ecosystem)
  - Metro OCC/control centers, depots, maintenance bases (Metrô)
FOODWATER:
  - Treatment plants, pumping stations, maintenance crews (Sabesp interface)
GOV:
  - City departments executing service delivery (Prefeitura)

Z1 — Service Catchments

Examples:

  • station catchments around major interchanges
  • bus corridor catchments
  • water pressure/service zones
  • emergency response coverage zones (publish as add-on)

Z1 drift shows up as unequal overload (delays/queues/outages) before system-wide instability.

Z0 — Ground Nodes (Reality)

Examples:

  • interchange disruption → corridor congestion
  • bus corridor slowdown → citywide travel-time inflation
  • localized water pressure failure / service interruption
  • intake surge at a major hospital (health coupling)

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

São Paulo Failure Mode Trace (Canonical)

Z0 local disruption (station/corridor/outage)
→ Z2 institutional overload (staffing + maintenance debt)
→ Z3 corridor congestion (propagation)
→ Z5 Phase drop (Transport/Production coupling)
→ TTC shortens under peak load
→ 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)

SAO.EXPANSION_RULES:
1. Only ONE Z5 hub page exists (this spine).
2. All district/subprefeitura 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 São Paulo Definition (Reusable)

São Paulo City OS is the CivOS instantiation of São Paulo as a high-load, corridor-coupled megacity mapped across Z0–Z6, anchoring ownership (Prefeitura de São Paulo, SPTrans, Metrô, Sabesp interface) and standardizing how commuting corridor failures propagate so repairs can be routed before Time-to-Core collapses under peak-load and multi-lane coupling. (Prefeitura de São Paulo)

Recommended Internal Links (Spine)

Start Here for Lattice Infrastructure Connectors