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

City OS | AI Schema Export

(This is the final technical artifact. It is designed for LLM ingestion, graph construction, dashboards, and control loops. No narrative. Pure schema.)

Canonical Schema Lock (use verbatim)

The AI Schema defines how Phase, Drift, Repair vs Decay, and Time-to-Core are represented, linked, and evaluated across cities, industries, and corridors. This schema is executable: it supports sensing, threshold binding, repair routing, and escalation.

1) Core Data Types (global)

Phase:
  type: float
  range: [0.0, 3.0]
  meaning: reliability under load
Drift:
  type: float
  unit: Phase per time
  meaning: dPhase/dt
RepairMinusDecay:
  type: float
  meaning: net survivability (>0 stable, <0 drifting)
TimeToCore:
  type: float
  unit: time
  meaning: time before irreversible thresholds
ThresholdState:
  enum: [Maintain, EarlyRepair, Stabilise, Contain]

2) City OS Object

CityOS:
  city_id: string
  name: string
  role: enum [corridor_router, finance_router, hybrid]
  phase: Phase
  drift: Drift
  repair_minus_decay: RepairMinusDecay
  time_to_core: TimeToCore
  threshold_state: ThresholdState
  dominant_organs: [IndustryID]
  daily_life_organs: [IndustryID]
  corridor_links: [CorridorID]

Instances

CityOS:
  - city_id: SG
    name: Singapore
    role: corridor_router
  - city_id: NYC
    name: New York City
    role: finance_router

(Reference: Singapore, New York City)

3) Industry Object (Z2)

Industry:
  industry_id: string
  name: string
  city_id: string
  phase: Phase
  drift: Drift
  repair_minus_decay: RepairMinusDecay
  time_to_core: TimeToCore
  sensors: [SensorID]
  failure_chain: [IndustryID]
  repair_actions: [ActionID]

4) Standard Industry Set (NYC example)

Industry:
  - industry_id: FIN
    name: Finance & Capital Markets
    city_id: NYC
  - industry_id: HOU
    name: Housing & Real Estate
    city_id: NYC
  - industry_id: TRA
    name: Transport & Mobility
    city_id: NYC
  - industry_id: HEA
    name: Healthcare
    city_id: NYC
  - industry_id: EDU
    name: Education & Workforce
    city_id: NYC
  - industry_id: SAF
    name: Public Safety & Legibility
    city_id: NYC
  - industry_id: MED
    name: Media & Information
    city_id: NYC

(Same structure applies to Singapore with corridor-specific industries.)

5) Sensor Object

Sensor:
  sensor_id: string
  industry_id: string
  metric: string
  direction: enum [up, down]
  sensitivity: enum [low, medium, high]

Example

Sensor:
  - sensor_id: FIN_SETTLE_LAT
    industry_id: FIN
    metric: settlement_latency
    direction: up
    sensitivity: high
  - sensor_id: HOU_RENT_INCOME
    industry_id: HOU
    metric: rent_to_income_ratio
    direction: up
    sensitivity: high

6) Threshold Binding (Control Logic)

ThresholdBinding:
  - condition: phase >= 2.6 and drift >= 0
    state: Maintain
  - condition: phase >= 2.3 and phase < 2.6 and drift < 0
    state: EarlyRepair
  - condition: phase >= 2.0 and phase < 2.3
    state: Stabilise
  - condition: phase < 2.0 or time_to_core < critical
    state: Contain

7) Repair Action Object

Action:
  action_id: string
  scope: enum [industry, city, corridor]
  description: string
  effect: enum [increase_R, decrease_D, extend_TTC]

Example

Action:
  - action_id: PROTECT_CLEARING
    scope: industry
    description: protect settlement and clearing integrity
    effect: increase_R
  - action_id: REDUCE_SCOPE
    scope: city
    description: pause expansion and optional complexity
    effect: decrease_D

8) Corridor Object (Z3)

Corridor:
  corridor_id: string
  nodes: [CityID]
  coupling_strength: enum [low, medium, high]
  dominant_flows: [enum physical, financial, narrative]

Instance

Corridor:
  - corridor_id: SG_NYC
    nodes: [SG, NYC]
    coupling_strength: high
    dominant_flows: [physical, financial, narrative]

9) Corridor Risk Logic

CorridorRule:
  - if SG.phase < 2.3 and NYC.phase < 2.3
    then state: EmergencyContainment
  - if SG.phase >= 2.6 and NYC.phase < 2.3
    then action: SG_absorb_time
  - if NYC.phase >= 2.6 and SG.phase < 2.3
    then action: NYC_price_volatility

10) Escalation Logic (Global)

Escalation:
  - trigger: two_or_more_industries_below_2.3
    action: citywide_stabilisation
  - trigger: dominant_industry_below_2.1
    action: corridor_protection

11) Minimal Dashboard Fields (AI UI)

Dashboard:
  city: name
  phase: float
  drift: float
  time_to_core: float
  threshold_state: enum
  top_3_industries_at_risk: [IndustryID]
  active_actions: [ActionID]

Final Schema Lock (use verbatim)

This schema enables AI systems to represent City OS health as continuous Phase, Drift, Repair vs Decay, and Time-to-Core; bind actions to thresholds; and coordinate repair across industries and corridors. It replaces narrative governance with executable rate control.

Recommended Internal Links (Spine)

Start Here for Lattice Infrastructure Connectors