MODULE: WaterOS↔EnergyOS.Coupling
VERSION: v1.2
STATUS: Cross-Kernel Coupling Module (Frozen Grammar)
SCOPE: Defines how WaterOS stability depends on EnergyOS via treatment/desalination,
       pumping, distribution pressure, and recovery operations.
DEPENDENCIES:
  - CivOS.Kernel.WaterOS (frozen)
  - CivOS.Kernel.EnergyOS (frozen)
  - CivOS.Zoom Z0–Z3
  - CivOS.Phase P0–P3
  - FenceOS (Truncation + Stitching)
CONSTRAINTS:
  - No new primitives
  - Coupling only (does not redefine either OS)
  - City-agnostic (place-parameterized)

This module specifies the mechanical coupling between WaterOS and EnergyOS.
Water continuity requires energy for treatment, desalination, pumping, pressure
maintenance, leak detection, repair operations, and emergency response. When EnergyOS
drifts below threshold, WaterOS regeneration capacity G(t) shrinks, causing WaterOS
rate-dominance risk (Ḋ > Ġ). This coupling is strongest in desalination-heavy cities.

COUPLING POINTS:
Z3 (Basin/Buffer):
  - Reservoir control systems
  - Raw water transfer pumping
  - Buffer reconfiguration under drought
Z2 (Institution/Plant):
  - Treatment works energy load
  - Desalination plants energy load (high coupling)
  - Wastewater processing (quality + compliance)
Z1 (Pipe/Distribution):
  - Pumping stations
  - Pressure zone control
  - Leak detection + telemetry power
Z0 (End-user):
  - Emergency distribution support (critical sites)
  - Communication + command systems (indirect)

WATEROS ENERGY DEPENDENCE VARIABLES:
E_load(t): energy required to sustain current water throughput
E_supply(t): energy available to water operations (priority-allocated)
E_margin(t) = E_supply(t) - E_load(t)
CouplingIndex κ(t) = clamp01( E_supply(t) / max(ε, E_load(t)) )
Interpretation:
  κ ≈ 1  → energy sufficient for water operations
  κ < 1  → water regeneration capacity shrinks (repairs delayed, throughput reduced)

COUPLING LAW:
WaterOS Decay Pressure:
  D(t) increases when κ(t) drops because:
    - pressure instability rises
    - leak detection weakens
    - repair time increases
    - quality incidents can rise (verification constrained)
WaterOS Regeneration Capacity:
  G(t) decreases when κ(t) drops because:
    - treatment/desal throughput reduced
    - pumping capacity reduced
    - repair routing slows (crew + machinery constrained)
    - emergency response bandwidth shrinks
Therefore:
  κ(t) ↓  →  D(t) ↑ and G(t) ↓  →  R(t)=D/G ↑

COUPLING SENSORS (generic; adapters map local feeds):
  S.Energy.AvailableToWaterOps      // E_supply
  S.Energy.WaterOpsLoad             // E_load
  S.Energy.OutageDurationRolling
  S.Energy.PriceShockIndex          // optional economic proxy
  S.Energy.PriorityAllocationFlag   // whether water is protected
Derived:
  κ(t) = E_supply / E_load
  EnergyDriftFlag = (κ(t) < Θ_kappa_low) OR (outages persistent)

DEFAULT THRESHOLDS:
  Θ_kappa_low  = 0.90   // below 90% of required energy → drift risk
  Θ_kappa_fail = 0.75   // below 75% → likely WaterOS P1 acceleration
  Θ_outage_crit = 6h    // rolling outages >6h are critical for water ops

PHASE COUPLING:
If EnergyDriftFlag TRUE:
  - degrade WaterOS effective G(t) by factor κ(t)
  - increase WaterOS R_proxy by factor (1/κ(t))
If κ(t) < Θ_kappa_fail sustained:
  - force WaterOS GateB (Active P1) unless buffers extremely high

TTC COUPLING:
If EnergyOS outage affects pumping/treatment:
  - reduce CriticalSiteBufferHours faster
  - TTC.HealthOS decreases
Rule:
  If Energy outage rolling > Θ_outage_crit:
     GateC becomes easier to trigger (Pre-P0)

COUPLED CORRIDORS:
When κ(t) drops:
TRUNCATION (Water side):
  - DemandThrottle
  - Pressure staging to prevent uncontrolled bursts
STITCHING (Energy side):
  - Priority allocation to water ops
  - Backup generation for treatment/pumping
  - Fast restoration routing for water-critical substations
MIXED:
  - Protect critical sites first (hospitals)
  - Execute both truncation (water) + stitching (energy) simultaneously

SENSITIVITY CLASSES:
Class A (High coupling):
  - desalination-heavy systems (e.g., Gulf cities)
Class B (Medium coupling):
  - large pumping + treatment dependent metros
Class C (Lower coupling):
  - gravity-fed / high natural head systems (still non-zero coupling)

FAILURE TRACE (coupled canonical):
EnergyOS drift (κ↓)
  → WaterOS Z2 throughput ↓ + Z1 pressure instability ↑
    → Repair time ↑, leak losses ↑
      → WaterOS R_proxy crosses >1
        → GateB triggers
          → TTC.HealthOS tightens
            → If uncontained → WaterOS P2→P1→P0

WHERE TO INCLUDE:
  - On WaterOS Global RuntimeHub (as Cross-OS coupling block)
  - On city pages where desalination/pumping is dominant (Dubai, Singapore, Sydney desal mode)
  - On EnergyOS pages (as Water coupling dependency)