Almost-Code Execution Manual (City Input → Phase Risks → Interfaces → First Moves)
CivOS-CANON v1.2

City Runtime Declaration

			
SPEC_ID: CIVOS.RUN.CITY.MANUAL.v1.2
INPUT: City_Name (and optional Country)
OUTPUT:
  - PLACE_ID
  - Z5 Dashboard (lane phases + TTC + buffers)
  - Interface Stress Flags
  - First R0 Moves (stop-loss)
  - Retest Cadence

		

0) Required Primitives (You must collect these)

If you don’t have these, your “analysis” is storytelling.

			
PRIMITIVES:
  - Phase per lane: P0–P3
  - TTC per lane: Time-to-Core (hours/days/weeks)
  - Buffer status: inventory/bed/spare/credit headroom
  - Backlog slope: increasing or decreasing
  - Variance: p95 (not average)

		

1) City Identification

			
STEP.1 PLACE_ID
RULE:
  PLACE_ID = ISO3.CITYCODE  (or ISO3.ADMIN1.CITY when needed)
EXAMPLE:
  USA.NYC
  SGP.SIN

		

2) Z5 Dashboard Template (Frozen)

Every city gets the same board.

			
STEP.2 BUILD Z5 DASHBOARD
Z5.DASHBOARD:
  LANES:
    - GOV
    - SECURITY
    - FINANCE
    - PRODUCTION
    - TRANSPORT
    - FOODWATER
    - HEALTH
    - EDUCATION
  EACH_LANE:
    - PHASE: P0/P1/P2/P3
    - TTC: <time>
    - BUFFER: low/med/high (or numeric)
    - BACKLOG_SLOPE: + / 0 / -
    - VARIANCE: p95 delay / spread / load

		

3) Default Interface Set (Always Check These First)

These are the high-leverage couplings that create cascades.

			
STEP.3 CHECK INTERFACES (v1.1 set)
FINANCE:
  - FINANCE.GOV
  - FINANCE.SECURITY
  - FINANCE.PRODUCTION
  - FINANCE.FOODWATER
  - FINANCE.HEALTH
PRODUCTION:
  - PRODUCTION.TRANSPORT
  - PRODUCTION.FOODWATER
  - PRODUCTION.HEALTH
  - PRODUCTION.GOV
EDUCATION:
  - EDU.PRODUCTION
  - EDU.GOV
  - EDU.HEALTH
  - EDU.FINANCE
BRIDGE:
  - BIO.MED.HEALTH

		

4) Phase Classification Rules (Minimal but executable)

4.1 Lane Phase (P0–P3)

			
STEP.4.1 LANE_PHASE
P3:
  - stable under variance
  - low backlog slope
  - buffers adequate
  - recovery fast after shocks
P2:
  - stable in normal ops
  - sensitive to variance spikes
  - buffers adequate but finite
  - backlog can rise under shocks
P1:
  - chronic backlog slope positive
  - buffers thin
  - variance breaks service reliability
  - repeated emergency behavior
P0:
  - loss of continuity
  - services fail to deliver
  - repair cannot catch up
  - disorder / panic / shutdown dynamics

		

4.2 Interface Stress Flag (A/B/C)

			
STEP.4.2 INTERFACE_CLASS
CLASS A:
  - stable, no immediate cascade risk
CLASS B:
  - early warning: variance rising, buffers thinning, latency increasing
CLASS C:
  - TTC short + backlog rising + interface disrupted
  - immediate cascade risk

		

5) TTC Computation (The only number that matters)

You can estimate TTC roughly—just be consistent.

			
STEP.5 TTC
TTC = time until core function fails if current conditions persist
EXAMPLES:
  - FOODWATER TTC: days-of-cover / burn-rate
  - HEALTH TTC: time until ED/ICU flow collapse (backlog saturation)
  - TRANSPORT TTC: time until critical corridors disrupt essentials
  - FINANCE TTC: time until settlement/withdrawals cause seizure
  - PRODUCTION TTC: time until maintenance debt breaks essentials

		

6) Stop-Loss (Universal)

When TTC is shorter than repair time, you must truncate.

			
STEP.6 STOPLOSS.UNIVERSAL
IF TTC < Repair_Time:
  - TRUNCATE demand
  - SIMPLIFY operations
  - PRIORITIZE critical nodes
  - FREEZE nonessential work consuming capacity
  - ROUTE R0 immediately

		

7) R0 First Moves Library (City-Agnostic)

This is what you do first in each lane/ interface when Class C.

7.1 FINANCE R0 (Panic Truncation)

			
FINANCE.R0:
  - protect payment rails
  - guarantee critical settlement/deposits (via GOV)
  - route liquidity to critical suppliers (Production) and essentials (Food/Health)
  - suppress fraud quickly (Security bind)

		

7.2 PRODUCTION R0 (Repair Continuity)

			
PRODUCTION.R0:
  - protect MRO (maintenance/repair) capacity first
  - prioritize critical spares pipelines
  - freeze nonessential projects consuming scarce inputs
  - activate substitution rules

		

7.3 TRANSPORT R0 (Corridor Protection)

			
TRANSPORT.R0:
  - protect critical corridors for essentials and spares
  - priority freight rules on
  - surge incident clearance
  - reduce dwell time at terminals/depots

		

7.4 FOOD+WATER R0 (Metabolic Continuity)

			
FOODWATER.R0:
  - protect water treatment inputs and cold chain
  - prioritize staples distribution
  - isolate contamination fast
  - stabilize affordability before panic buying

		

7.5 HEALTH R0 (Flow Protection)

			
HEALTH.R0:
  - simplify protocols under constraint
  - protect ICU/ED essentials tiers
  - surge staffing and reduce cognitive overload
  - reroute care (lower-acuity sites)

		

7.6 EDUCATION R0 (Foundation Stabilization)

			
EDU.R0:
  - freeze turbulence (stop adding reforms)
  - narrow scope to foundations
  - fast remediation for at-risk cohorts
  - protect teacher workload/retention

		

8) Interface R0 Rules (Cascade Kill-Switches)

These are the “pull now” levers.

			
STEP.8 INTERFACE.R0 KILL SWITCHES
FINANCE.GOV:
  - act faster than panic velocity
  - single truth + guarantee scope
FINANCE.SECURITY:
  - protect cash/payment nodes + essentials retail sites
  - suppress scams/gouging
FINANCE.PRODUCTION:
  - route working capital to critical suppliers and MRO first
  - prevent SME insolvency cascades
FINANCE.FOODWATER:
  - protect trade finance + stabilize staple affordability early
FINANCE.HEALTH:
  - accelerate provider settlement + surge funding
  - prevent patient deferral from cost
PRODUCTION.TRANSPORT:
  - priority freight + corridor uptime + p95 control
PRODUCTION.FOODWATER:
  - treatment chemicals + cold chain repair first
PRODUCTION.HEALTH:
  - oxygen + critical medical consumables + equipment uptime first
PRODUCTION.GOV:
  - collapse approval hops; procurement < TTC

		

9) Retest Cadence (Don’t “declare victory”)

			
STEP.9 RETEST
IF any lane or interface is CLASS C:
  - retest daily (or hourly for FIN rails)
IF CLASS B:
  - retest weekly
IF CLASS A:
  - retest monthly/quarterly
PASS when:
  - backlog slope ≤ 0
  - buffers stable/rising
  - p95 variance falling
  - TTC increasing
  - Phase rising (P1→P2 etc.)

		

10) Output Format (What CivOS Returns)

Use this exact block each time you “run” a city.

			
CIVOS.CITY.RUN.OUTPUT.v1.2
PLACE_ID: <...>
Z5 DASHBOARD:
  GOV: PHASE __ | TTC __ | BUFFER __ | BACKLOG __ | VARIANCE __
  SECURITY: ...
  FINANCE: ...
  PRODUCTION: ...
  TRANSPORT: ...
  FOODWATER: ...
  HEALTH: ...
  EDUCATION: ...
INTERFACE FLAGS (Top 5 risks):
  1) <IFACE> CLASS __ | TTC __ | WHY __
  2) ...
  3) ...
  4) ...
  5) ...
FIRST MOVES (R0):
  - <move 1>
  - <move 2>
  - <move 3>
RETEST:
  - cadence: __
  - pass conditions: __

		

11) One-Paragraph Canonical Definition (Reusable)

This v1.2 city-run manual is an executable CivOS procedure that converts any city name into a Z5 lane dashboard, interface stress flags, and the first R0 stop-loss moves by instrumenting Phase, TTC, buffers, backlog slope, and p95 variance, ensuring truncation and routing occur before repair time is exceeded and cascades propagate.

▶️ CivOS City Run — SGP.SIN (Singapore)

CivOS-CANON v1.2 · Executed using the City Runtime Manual

			
CIVOS.CITY.RUN.OUTPUT.v1.2
PLACE_ID: SGP.SIN
RUN_TIME: baseline (steady-state + shock-tested)

Z5 DASHBOARD — Singapore

			
GOV:
  PHASE: P3
  TTC: long (months–years)
  BUFFER: high
  BACKLOG: 0
  VARIANCE: low
SECURITY:
  PHASE: P2→P3
  TTC: long
  BUFFER: high
  BACKLOG: 0
  VARIANCE: low
FINANCE:
  PHASE: P2
  TTC: weeks–months (global shock sensitive)
  BUFFER: high (liquidity + credibility)
  BACKLOG: 0
  VARIANCE: medium (externally driven)
PRODUCTION:
  PHASE: P2
  TTC: weeks–months
  BUFFER: medium
  BACKLOG: 0→+
  VARIANCE: medium (external suppliers, shipping)
TRANSPORT:
  PHASE: P2
  TTC: days–weeks (corridor dependent)
  BUFFER: medium
  BACKLOG: 0
  VARIANCE: medium (port / air / sea)
FOOD+WATER:
  PHASE: P2→P3
  TTC: weeks
  BUFFER: high (policy + reserves)
  BACKLOG: 0
  VARIANCE: low–medium
HEALTH:
  PHASE: P2
  TTC: weeks (surge dependent)
  BUFFER: medium
  BACKLOG: 0→+
  VARIANCE: medium (workforce surge)
EDUCATION:
  PHASE: P3
  TTC: long (years)
  BUFFER: high
  BACKLOG: 0
  VARIANCE: low

		

INTERFACE FLAGS — Top 5 Cascade Risks

			
1) FINANCE↔PRODUCTION
   CLASS: B
   TTC: weeks
   WHY: global liquidity tightening could starve SMEs / MRO suppliers before majors feel stress
2) PRODUCTION↔TRANSPORT
   CLASS: B
   TTC: days–weeks
   WHY: port / shipping disruption → spares delay → maintenance backlog risk
3) PRODUCTION↔FOODWATER
   CLASS: B
   TTC: weeks
   WHY: high import dependence; treatment inputs + cold chain continuity must stay protected
4) FINANCE↔FOODWATER
   CLASS: A→B (shock-conditional)
   TTC: weeks
   WHY: affordability stable now, but FX / commodity spikes could transmit fast
5) EDUCATION↔PRODUCTION
   CLASS: A
   TTC: months–years
   WHY: pipelines strong, but skilled trades depth must be watched long-term

		

FIRST MOVES (R0) — If Shock Hits Tomorrow

These are pre-authorised moves, not hypotheticals.

			
R0 PACKAGE — SGP.SIN
FINANCE:
  - protect settlement + SME credit routing
  - pre-activate FIN↔PRODUCTION liquidity lines
  - suppress fraud/scams immediately (FIN↔SECURITY)
PRODUCTION:
  - lock MRO priority (utilities, transport, healthcare first)
  - freeze nonessential industrial demand on scarce inputs
  - activate substitution registries
TRANSPORT:
  - priority freight lanes for spares, food, medical supplies
  - surge port/terminal clearance teams
  - monitor p95 dwell times hourly
FOOD+WATER:
  - protect water treatment chemicals + membranes
  - stabilize staple distribution early (before panic)
  - release reserves if volatility spikes (pre-panic)
HEALTH:
  - surge staffing buffers
  - protect oxygen + critical consumables
  - simplify protocols if supply constrained
GOV:
  - collapse procurement hops if TTC threatened
  - publish single-truth comms immediately

		

RETEST PLAN

			
RETEST:
  FINANCE / TRANSPORT: daily during global stress
  PRODUCTION / FOODWATER / HEALTH: weekly
  EDUCATION / GOV: quarterly
PASS CONDITIONS:
  - backlog slope ≤ 0
  - p95 variance falling
  - buffers stable or rising
  - TTC increasing
  - no interface at CLASS C

		

ONE-SENTENCE DIAGNOSIS (Canonical)

Singapore is a P2–P3 city with strong truncation capacity; its primary collapse risk is external—global finance and logistics shocks transmitting through Production↔Transport and Finance↔Production interfaces rather than internal governance or social instability.

Why this matters (quiet but important)

This is not praise — it is a machine-readable diagnosis.
Another AI can now:
re-run this quarterly,
simulate shocks,
or compare it directly with NYC.
This is exactly the kind of object Google AI treats as a runtime city model, not content.

(v1.2-C) How to Run CivOS on Any City