SG Z4 Nation Education Stability Panel v0.1 — Macro HGW Forecasting + Drift Pockets + Coupling Risk

TITLE: SG Z4 Nation Education Stability Panel v0.1 — Macro HGW Forecasting + Drift Pockets + Coupling Risk
VERSION: CivOS Unified Spec v1.x
MODE: Almost-Code / Panel spec + sensors + outputs / WordPress paste-ready
OWNER: eduKateSG Fence Learning Systems
PLACE: SG
ZOOM: Z4 (Nation)
GOAL: Provide a national-level “Education Stability Panel” that:
      - aggregates lane stability (ENG/MATH/SCI/HUM/VL),
      - detects drift pockets early (before exam-visible failure),
      - forecasts near-term risk and repair load,
      - shows coupling-break risks (ENG→MATH, MATH→SCI, ENG→HUM),
      - outputs operator actions (policy-neutral; coordination-first).
NOTE (FACT BOUNDARY):
This is a CivOS/EducationOS operational panel spec, not a statement of MOE policy.
It can be run by schools, centres, or communities as an instrumentation layer.
========================================================
1) Z4 PANEL: SG NATIONAL EDUCATION STABILITY PANEL
========================================================
PanelRecord:
- id: SG×EDU×Z4×Operator×Panel×SG-NESP-v0.1
  name: Singapore National Education Stability Panel (NESP)
  zoom: Z4
  inputs_required: [
    "Cohort segmentation (bands): P3–P6, Sec1–Sec4, JC1–JC2",
    "WeeklyPack completion rates (PackIDs)",
    "Sensor distributions (TR/ERC/SII/NIT/NITS/NITA) by lane",
    "Signature prevalence rates (%) by lane",
    "Coupling-edge failure indicators (COUP-SG-01/02/03)",
    "Tool-with-Proof compliance rate (TracePresent%)",
    "Time buffer proxies (sleep/attendance/avoidance; aggregated)"
  ]
  output_fields: [
    "National Phase Distribution (overall + by band + by lane)",
    "Drift Pocket Map (top pockets by signature cluster)",
    "Coupling Risk Table (COUP edges: green/amber/red)",
    "Repair Load Forecast (hours/week required by protocol class)",
    "Stability Forecast 4–12 weeks (qualitative: stable/fragile/declining)",
    "Operator Actions (protocol deployment recommendations)",
    "Backtest Readiness (data quality + feedback latency)"
  ]
  alert_rules: [
    "If NIT/NITS/NITA cluster >20% in any band => S3 THRESHOLD CLUSTER",
    "If TracePresent% <80% => S3 AI-BRITTLENESS SYSTEMIC",
    "If P1 share rises 2 consecutive cycles => S2 P1 INFLATION",
    "If COUP edge turns red => S2 CASCADE RISK",
    "If CompletionRate drops below 85% in timed minis => S2 TIME CRASH"
  ]
  output_format: |
    [SG-NESP v0.1]
    Place: SG
    Date: <YYYY-MM-DD>
    Window: <last 2–4 weeks>
    Coverage: <n learners / schools / centres> (if known)
    1) National Phase Distribution
    - Overall: P0 <..>% | P1 <..>% | P2 <..>% | P3 <..>%
    - P3–P6: ...
    - Sec1–Sec4: ...
    - JC1–JC2: ...
    - By lane:
      ENG: ...
      MATH: ...
      SCI: ...
      HUM: ...
      VL: ...
    2) Drift Pocket Map (Top 5)
    - Pocket #1: <SignatureID> — band: <...> — prevalence: <..>% — protocol: <ProtocolID>
    - Pocket #2: ...
    - Pocket #3: ...
    - Pocket #4: ...
    - Pocket #5: ...
    3) Coupling Risk Table
    - COUP-SG-01 (ENG→MATH WP): <Green/Amber/Red> — indicator: <...>
    - COUP-SG-02 (MATH→SCI): <Green/Amber/Red> — indicator: <...>
    - COUP-SG-03 (ENG→HUM Essay): <Green/Amber/Red> — indicator: <...>
    - COUP-SG-04 (VL→ALL trace compliance): <Green/Amber/Red> — indicator: <TracePresent%>
    4) Repair Load Forecast (next 4 weeks)
    - Emergency Coherence (PROT-ENG-EMERGENCY-COHERENCE): <hours/wk>
    - Emergency Mechanism (PROT-SCI-EMERGENCY-MECHANISM): <hours/wk>
    - Coupling Repair ENG→MATH (PROT-COUP-ENG→MATH-WP): <hours/wk>
    - Graph Meaning Repair (PROT-MATH-GRAPH-MEANING): <hours/wk>
    - Speed Stability Ladder (PROT-SPEED-STABILITY-LADDER): <hours/wk>
    - Tool-with-Proof (PROT-TWP-ENFORCEMENT / PROT-VL-TRACE-ENFORCE): <hours/wk>
    5) Stability Forecast (4–12 weeks)
    - Direction: <Stable / Fragile / Declining>
    - Why (top 3 drivers): <...>
    6) Operator Actions (Coordination-First)
    - Action A: deploy <ProtocolID> to <band> — goal: reduce <SignatureID> cluster
    - Action B: tighten <WeeklyPackID> compliance — goal: restore sensor visibility
    - Action C: enforce trace compliance (VL-OS) — goal: reduce AI-brittleness
    7) Backtest Readiness
    - Data quality: <H/M/L>
    - Feedback latency: <H/M/L>
    - Next backtest question: <1 line>
========================================================
2) Z4 MACRO SENSORS (AGGREGATION SENSORS)
========================================================
MacroSensorRecord := {
  id, name, inputs, output_metric, threshold_alerts
}
- id: SG×EDU×Z4×Operator×Sensor×MS-PHASE-DIST
  name: National Phase Distribution Sensor
  inputs: "lane phase estimates from sensors"
  output_metric: "%P0/%P1/%P2/%P3"
  threshold_alerts: "P1 rising 2 cycles => S2"
- id: SG×EDU×Z4×Operator×Sensor×MS-NIT-CLUSTER
  name: Threshold Cluster Sensor
  inputs: "NIT_w/NITS_w/NITA_w across cohorts"
  output_metric: "cluster prevalence %"
  threshold_alerts: ">20% => S3"
- id: SG×EDU×Z4×Operator×Sensor×MS-COUP-RISK
  name: Coupling Risk Sensor
  inputs: "COUP edges indicators"
  output_metric: "Green/Amber/Red per edge"
  threshold_alerts: "Red => S2"
- id: SG×EDU×Z4×Operator×Sensor×MS-TRACE-COMP
  name: Trace Compliance Sensor (VL-OS)
  inputs: "TracePresent rate from TWP checks + VL micro"
  output_metric: "TracePresent%"
  threshold_alerts: "<80% => S3"
- id: SG×EDU×Z4×Operator×Sensor×MS-REPAIR-LOAD
  name: Repair Load Forecast Sensor
  inputs: "signature prevalence × protocol hours per case"
  output_metric: "hours/week by protocol"
  threshold_alerts: "repair load rising => S2 (capacity risk)"
========================================================
3) COUPLING EDGE DEFINITIONS (Z4 VIEW)
========================================================
COUP-SG-01: ENG inference stability → MATH WP constraint capture
COUP-SG-02: MATH algebra/graph meaning → SCI physics/application stability
COUP-SG-03: ENG paragraph/argument spine → HUM essay coherence and evaluation
COUP-SG-04: VL trace compliance → ALL lanes robustness (AI-era brittleness control)
========================================================
4) REQUIRED FAILURE TRACE (Z4)
========================================================
Trace:
micro-failures uninstrumented →
drift pockets grow →
coupling breaks propagate →
repair load spikes →
late national decline.
Repair:
weekly sensors →
signature clustering →
protocol deployment →
coupling protection →
repair capacity planning →
stable national flight.
========================================================
END: SG Z4 Nation Education Stability Panel v0.1
========================================================