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.

London ↔ Singapore City Comparative (GBR-LON ↔ SGP-SIN) — Z5↔Z5

Divergence-Tails vs Compression-Cliffs (Almost-Code v1.1)

Publishing role: This is the cleanest city-level contrast for World Education OS adoption.
Both are “strong cities,” but their failure physics are opposite.


0) Header Lock

SYSTEM: World Education OS
MODULE: City↔City Comparative (Z5↔Z5)
PAIR:
CITY_A: GBR-LON (London City Education OS)
CITY_B: SGP-SIN (Singapore City Education OS)
REFERENCE: CivOS (Phase P0–P3, Zoom Z0–Z7)
PURPOSE:
Compare city execution mechanisms using shared sensors,
map failures to GF*, and export repairs as GR* sets with proof requirements.
COMPARISON RULES (LOCK):
- Compare variance + tails + latency, not averages
- Identify where gates cluster shocks
- Export repairs with sensor proofs (G-M*)

1) One-Line Mechanism Contrast

MECHANISM:
London = divergence + tails + continuity fragmentation → long repair latency → polarised outcomes.
Singapore = compression ramps + high-stakes synchronisation → timed cliffs → late repair collapses at gates.

2) Pipeline Alignment (Functional Equivalence)

PIPELINE ALIGNMENT (E0–E6):
London:
E0 early years
E1 early primary
E2 late primary
E3 KS3 / lower secondary (T2 shock amplifier)
E4 GCSE ramp + verification
E5 post-16 (A-Level/vocational; autonomy jump)
E6 post-18 transition
Singapore:
E0 preschool
E1 P1–P2
E2 P3–P4
E3 P5–P6 (PSLE ramp)
E4 Sec1–Sec2
E5 Sec3–Sec4/5 (O/N verification)
E6 post-sec (JC/Poly/ITE)
KEY DIFFERENCE:
London’s largest amplification is T2 (primary→secondary) + system divergence.
Singapore’s largest amplification is PSLE ramp + Sec2→3 + O/N verification (compression cliffs).

3) Comparative Scoreboard (City Mechanics)

DIMENSIONS:
D1 Compression intensity
D2 Divergence intensity (inter-school/area variance)
D3 Tail thickness persistence (P0 pockets)
D4 Repair latency distribution
D5 Transition shock clustering (T1–T5)
D6 Timed vs untimed gap
D7 Transfer gap under novelty
D8 Shadow repair dependence (masking factor)
D9 Continuity fragmentation (reset risk)
D10 Endurance stability (long-paper deterioration)
EXPECTED SHAPE:
London:
D1 MID
D2 HIGH
D3 MID-HIGH (clustered)
D4 LONG in tails
D5 HIGH at T2 and GCSE ramp
D6 MID (varies by cluster)
D7 MID-HIGH (transfer varies widely)
D8 MID-HIGH (uneven private support)
D9 MID-HIGH
D10 HIGH relevance post-16
Singapore:
D1 HIGH
D2 LOW-MID
D3 MID (often masked by tuition)
D4 BIMODAL (early repair possible, late repair common)
D5 VERY HIGH at PSLE + Sec2→3 + O/N gate
D6 HIGH relevance (timed cliffs)
D7 MID-HIGH (format novelty triggers collapse)
D8 HIGH (tuition masking)
D9 LOW-MID
D10 MID relevance

4) GF Cluster Crosswalk (What dominates where)

LONDON DOMINANT GF:
{GF1, GF4, GF5, GF7, GF8, GF9, GF10, GF11, (GF12)}
SINGAPORE DOMINANT GF:
{GF1, GF2, GF3, GF5, GF6, GF7, GF8, GF9, (GF12)}
PRIMARY CONTRAST:
London: GF4 + GF11 are structural (tails + resets).
Singapore: GF3 + GF6 are structural (compression cliffs + timed collapse).

5) Shared Sensor Pack (City comparability requirement)

SHARED SENSORS (P-S*):
P-S1 retrieval reliability
P-S2 error histogram
P-S3 time-to-solve distribution
P-S4 transfer under wrapper variation
P-S5 timed stability variance
CITY OUTPUTS (G-M*):
G-M1 variance spread
G-M2 tail thickness
G-M3 repair latency distribution
G-M4 transition shock clustering
G-M5 timed vs untimed gap
G-M6 transfer gap under novelty
G-M7 shadow repair dependence index

6) Exportable Repairs (London → Singapore)

London’s advantage is managing heterogeneity and making tails visible and repairable.

EXPORTS (LON → SIN):
L→S1: GR7 Tail Visibility Protocol
- make tuition-masked pockets visible earlier
- publish tails + latency pre-ramps
L→S2: GR9 Cluster Targeting Protocol
- route repair capacity by tail thickness + repair latency
- avoid “average illusion” at city scale
L→S3: GR6 Continuity Loop
- protect consolidation during compression ramps
- reduce volatility and reset cycles
L→S4: GR10 Standardised Repair Protocols
- ensure repairs survive across teachers/schools
PROOF REQUIREMENTS (LON → SIN):
- G-M2 tails shrink before PSLE/Sec2→3
- G-M3 repair latency shortens
- P-S5 volatility decreases near ramps
- G-M7 masking factor decreases (dependency reduced)

7) Exportable Repairs (Singapore → London)

Singapore’s advantage is tight protocol discipline for timed stability and early triggers.

EXPORTS (SIN → LON):
S→L1: GR8 Early-Warning Thresholds (pre-ramp triggers)
- enforce repair BEFORE GCSE ramp (reduce GF7)
S→L2: GR4 Time-Pressure Loop (timed execution stability)
- reduce volatility and timed collapse (G-M5↓)
S→L3: GR2 Error-Log Closure Loop (systematic repeat elimination)
- reduce repeat error density in tails
S→L4: GR12 Algebra Readiness Stabilisation
- protect T2/T3 transitions (primary→secondary / KS3→GCSE ramp)
PROOF REQUIREMENTS (SIN → LON):
- G-M3 repair latency decreases before GCSE ramp
- G-M5 timed gap decreases in tail clusters
- G-M4 transition shock clustering reduces (T2)
- G-M6 transfer gap decreases on wrapper audits

8) Failure Trace Contrast (City-level)

LONDON FAILURE TRACE:
GF1 early language drift →
GF4 divergence hides tails →
GF11 continuity fragmentation resets loops →
GF5 transition shock at T2 amplifies →
GF7 late repair becomes default →
GCSE outcomes polarise; tails persist
SINGAPORE FAILURE TRACE:
GF2 practice without model (or GF1 language drift) →
GF3 compression ramps exceed buffers →
GF6 timed execution collapse →
GF7 late repair trap →
cliff failures at PSLE/Sec2→3/O/N gates
SHARED REPAIR TRACE:
publish tails/variance/latency →
trigger early repair →
run transfer audits + timed stability loops →
verify closure before gates →
shrink tails + reduce volatility

9) Registry Update (W3 entry)

W3 REGISTRY ENTRY:
COMP_ID: COMP-GBR-LON-SGP-SIN
DOMINANT_CONTRAST_TAGS:
{Divergence-Tails vs Compression-Cliffs, Continuity-Reset vs Protocol-Discipline, Late-Repair vs Pre-Trigger}
DOMINANT_GF_CLUSTER:
{GF1,GF2,GF3,GF4,GF5,GF6,GF7,GF8,GF9,GF10,GF11,GF12}
GR_EXPORTS_LON_TO_SIN: {GR7,GR9,GR6,GR10}
GR_EXPORTS_SIN_TO_LON: {GR8,GR4,GR2,GR12}

10) Closing Lock

LOCK:
London and Singapore are both strong, but fail differently:
London fails by unmanaged divergence, tails, and resets.
Singapore fails by compression cliffs and timed collapse when repair is late.
The world lattice advances when they exchange GR exports with proof via G-M sensors.

Recommended Internal Links (Spine)

Start Here for Lattice Infrastructure Connectors