Singapore COVID — Truncation & Stitching mapped to APRC (Almost-Code Canonical Case)

F1: Circuit Breaker announced 3 Apr 2020; measures effective 7 Apr 2020 to 4 May 2020 (initial window). :contentReference[oaicite:0]{index=0}
F2: Circuit Breaker period was extended to 1 Jun 2020 (inclusive) under government directive (extension referenced in regulatory guidance). :contentReference[oaicite:1]{index=1}
F3: MOH announced end-of-circuit-breaker phased reopening plan (19 May 2020).
F4: Phase 2 (Heightened Alert) tightening effective 16 May 2021 through 13 Jun 2021. :contentReference[oaicite:3]{index=3}
F5: Changi Airport cluster occurred May 2021 (acknowledged in Changi Airport Group annual report; also widely reported). :contentReference[oaicite:4]{index=4}

OBJECTIVE:
Prevent persistent regime where R(t) < D(t)
and prevent COEE (pipeline extinction) events in core HRL / RePOC pillars.
Operationally:
Keep core pillars ≥ P2 at Z2/Z3 while using truncation to create stitching windows.

Protected objects (not buildings, not money):
- HRL continuity: core roles remain staffed; replacement pipelines remain alive
- Bind integrity: public health rules + enforcement remain credible
- RePOC continuity: governance, healthcare capacity, essential flows, education pipeline continuity

EVENT:
Circuit Breaker effective from 7 Apr 2020 (initial 4-week window). :contentReference[oaicite:5]{index=5}
Extension to 1 Jun 2020 (inclusive) is referenced in official guidance following the extension directive. :contentReference[oaicite:6]{index=6}

CIVOS CLASSIFICATION:
- OP TYPE: Truncation (early cut-off of accelerating transmission regime)
- GOAL: reduce D(t) drivers (rapid spread) and protect HRL nodes and binds
- PRIMARY EFFECT: create a stitching window by reducing shock frequency and load

EVENT:
MOH set out phased approach to resuming activities safely (end-of-circuit-breaker plan). :contentReference[oaicite:7]{index=7}

CIVOS CLASSIFICATION:
- OP TYPE: Stitching (regeneration catch-up)
- MECHANISM:
  - restore activity gradually to keep binds credible
  - preserve buffer thickness (avoid re-entering acceleration)
  - maintain enforcement and sensing loops

EVENT:
Phase 2 (Heightened Alert) tightened measures from 16 May 2021 through 13 Jun 2021. :contentReference[oaicite:8]{index=8}
CONTEXT ANCHOR:
Changi Airport cluster noted in May 2021. :contentReference[oaicite:9]{index=9}

CIVOS CLASSIFICATION:
- OP TYPE: Truncation (again)
- WHY:
  - variation spike / cluster shock increases volatility
  - bind integrity and enforcement need reinforcement to prevent drift
- TARGET:
  - stop-loss before instability becomes Mode III

FOLLOW-ON:
Stitching occurs when measures ease and flows resume while keeping recovery time < next shock interval.
(Details differ across sub-episodes; pattern remains truncation → stitching.)

Symptom appears as Z3-level risk:
- population-level transmission threatens healthcare capacity and coordination bandwidth

Routing is Z3 → Z2/Z0:
- Z2: hospitals, workplaces, schools, transport, border operations (interfaces/binds)
- Z0: individual compliance, role execution, frontline operator safety

Target:
- keep core pillars at least P2Z2/P2Z3
- push key binds (public health compliance, healthcare protocols) toward P3 where variation is unavoidable

Truncation contribution:
- cuts off acceleration early (reduces D(t) slope)
- prevents bind rupture and overload cascades
- preserves time window for repair
Stitching contribution:
- rebuilds normal function gradually
- maintains bind integrity (credibility) while restoring throughput
- restores buffers to survive next variation spike

NOT CLAIMED:
- “No waves occurred”
- “No costs existed”
- “Outputs (GDP, buildings) define success”
CLAIMED (only):
This is a recoverable control pattern:
Repeated truncation + stitching can keep the system away from irreversible collapse envelopes
by protecting HRL + RePOC pipelines.

FAILURE MODE TRACE (schematic):
variation spike (cluster / new variant)
→ D(t) accelerates; bind errors rise (compliance drift)
→ if no truncation: recovery window disappears (shock interval < recovery time)
→ healthcare and governance binds degrade to P1 under load
→ COEE risk rises (pipeline extinction in staffing/training)
→ Civλ jumps; R(t) < D(t) persists → Mode III possible
Observed control pattern:
stop-loss truncation
→ stitching restores buffers + throughput
→ return toward P2/P3 band in core pillars

CLAIMS (frozen):
- Singapore COVID provides a clean APRC pattern example: truncation followed by stitching.
- The stabilised object is HRL + RePOC pipeline continuity (not infrastructure, not money).
- Re-truncation during later turbulence (e.g., 16 May–13 Jun 2021 heightened alert) matches stop-loss logic. :contentReference[oaicite:10]{index=10}
- Timeline anchors are fixed by official releases (MOH + related official guidance). :contentReference[oaicite:11]{index=11}