Nexus Synergy Engagement Package — A03 · OPW + Met Éireann (Flood Forecasting Centre) + Local Authorities (LCC tier)

STATUS HONESTY. Nexus Synergy Ltd is pre-incorporation, pre-revenue, pre-pilot. OPW, Met Éireann and the Local Authorities named here are TARGETS, not customers — there is no engagement, no LOI, no deployment. The ~178-surface UI gallery is a gallery, not traction; the storm-replay flood COP is a build-spec, not a built system, with no live Irish-feed integration today. ANTI-COOKIE-CUTTER. The §8 mockups are programmatically generated for this buyer's geography (River Slaney / Enniscorthy / Wexford LCC), feeds (Met Éireann FFC, OPW floodinfo.ie CFRAM, OPW/EPA gauges) and entities — they are not a shared template with swapped text. DECLINE-SAFE. Hydrological/environmental situational awareness + resource coordination only. No predictive policing, no biometric ID, no emotion recognition, no social scoring, no untargeted scraping, no psychometric profiling, no individual risk-scoring. Every probability below is a subjective [PRIOR], for prioritisation, not a forecast.

---

§0 — Header & one-line thesis

Thesis. Ireland can model a flood but cannot warn a street; the official localised-warning system is 5–10 years out. Nexus Synergy delivers the operational layer now — a sovereign, human-gated, fully-audited street-level flood common operating picture (COP) that consumes Met Éireann's FFC output and OPW's CFRAM maps, fuses them with live gauges onto one map across an LA's Local Co-ordination Centre, and closes the loop with a dual-control public warning + evacuation-coordination action — complementary to the State's programme, not a competitor to it.

§1 — Entity snapshot (cited)

A three-body buying constellation, which is the structural reality of Irish flood management — not one account but a horizontal coordination layer:

• Office of Public Works (OPW) — lead State body for flood-risk management; owns the National CFRAM Programme (hazard/risk maps for Areas for Further Assessment, published on floodinfo.ie) and the Minor Flood Mitigation Works & Coastal Protection Scheme; administers the NDP flood capital line. Minister of State: Kevin "Boxer" Moran. [verified — gov.ie OPW; RTÉ 2026]
• Met Éireann — Flood Forecasting Centre (FFC) — operational since January 2024, the first stage of the National Flood Forecasting and Warning Service led by OPW; issues daily catchment guidance/advisories to NDFEM and Local Authorities. The localised public-warning service is Phase 2, not yet delivered. [verified — met.ie; gov.ie FFC briefing]
• Local Authorities (31 LAs) — designated Principal Response Agencies (PRAs) under the Framework for Major Emergency Management (FMEM); run Local Co-ordination Centres (LCCs) where An Garda Síochána, the HSE and the LA share situational information during a flood. Coordinated via the CCMA across 8 MEM regions, reporting to a National Steering Group; FMEM governance runs out of DHLGH / NDFEM. [verified — gov.ie FMEM; EU civil-protection Ireland profile]

The named beachhead in this package is Wexford County Council (Enniscorthy, River Slaney) — a repeatedly-flooded LA that received part of the post-Storm-Chandra €6.6m interim tranche, so budget is already moving at its tier.

§2 — The pain (web-verified, dated, cited)

• The forecasting–response gap is the headline problem. Communities hit by Storm Chandra (January 2026) reported "little or no meaningful notice before floodwaters arrived, with alerts that were too broad to be useful and county-level warnings that told people almost nothing about the risk on their street." [verified — RTÉ, 12 Apr 2026] This is the exact wedge: localised, street-level, actionable warning + downstream coordination.
• Public localised warning is years away. At the Dáil Public Accounts Committee in March 2026, OPW's head of planning and climate adaptation Robert Mooney said the initial Phase-2 timeline of five years had "run over to seven years"; the PAC summary framed localised warnings as potentially 5–10 years away, and no single agency is clearly in charge. [verified — RTÉ, 19 Mar 2026; Irish Times, 22 Mar 2026]
• Money is moving reactively and at LA level. On 25 May 2026 Minister Moran raised the Minor Works Scheme threshold from €750,000 to €2 million (and the OPW contribution from 90% to 95%), added €3 million for river-conveyance blockage clearance, and confirmed €6.6 million in post-Storm-Chandra interim funding to certain LAs. Since 2009 the scheme has approved ~€70m for ~930 LA projects protecting ~8,000 properties. [verified — gov.ie press release, 25 May 2026; Connaught Telegraph; Cork Safety Alerts]
• The State is being out-built by a volunteer. An Enniscorthy resident launched a national flood-predictor app [verified — RTÉ, 18 May 2026] — a reputationally awkward signal that the official gap is being filled from below.

Net: an acute, recurring, well-documented need for a shared operating picture + localised warning + multi-agency coordination, with the official solution years out and money already in motion.

§3 — Use-case & value (DECLINE-SAFE framing)

Flood Common Operating Picture (COP) + multi-agency evacuation-coordination action loop — the disaster pillar applied to the LCC / Regional / National MEM tiers, mapped to the closed action loop:

• Detect / enrich — ingest Met Éireann FFC catchment-model output, OPW floodinfo.ie CFRAM hazard/AFA layers, OPW/EPA river-gauge + rain-radar feeds, and LA ground reports onto the triple-renderer map over a customer-editable ontology (catchment, gauge, AFA, scheme, refuge, road, property-at-risk, asset).
• Triage — fuse forecast + on-the-ground gauge state into one street-level risk picture, replacing "county-level warnings that tell people almost nothing about their street."
• Human-gated sign-off — every escalation, public message or evacuation order passes a named human approval step (the LA Severe-Weather Coordinator / LCC Controller), with a full provenance/audit ledger — the FMEM chain made auditable.
• Task / execute — write-back adapters task LA resources (crews, pumps, road closures, refuge openings) and coordinate the PRAs (Garda/HSE/LA) inside the LCC.
• Assess / close — after-action timeline + bitemporal history for post-event review and inter-agency reporting.

Explicitly OUT of scope (decline-safe). This is environmental/hydrological situational awareness and resource coordination. It is NOT predictive policing, NOT biometric identification, NOT emotion recognition, NOT social scoring, NOT untargeted scraping, NOT psychometric profiling, and carries no individual risk-scoring. The only "prediction" is hydrological flood-extent from licensed meteorological/hydrological models. The vulnerable-person layer uses consented, already-held LA registers / aggregate census geography — surfacing who registered for help, never inferring who "might" be vulnerable. Everything is human-gated and fully audited — the selling point, not a constraint.

Value levers. Faster, street-level warning lead-time; one shared picture across an LA + Met Éireann + OPW (kills the current fax/email/phone-tree LCC reality); an auditable decision trail for the inevitable post-event reviews; and a near-term operational layer delivering value now while the 5–10-year national system is built — complementary to Met Éireann's FFC, not a replacement forecasting engine.

§4 — Ontology (this buyer's domain)

Entity types (customer-editable; this case's instantiation):

• Catchment — EPA hydrometric area (e.g. Slaney); FloodEvent — one per declared incident, CAP identifier-keyed.
• HydrometricStation / RiverGauge — OPW/EPA gauge (e.g. ENNIS01), recorded_at-only point-in-time level + return-period band (Q50/Q100/Q200).
• InundationPolygon — source ∈ {cfram_q100, ffc_forecast, sar_actual}; CFRAM Q100 AFA envelope (Floods-Directive baseline) vs FFC t+6h forecast crest vs observed extent.
• PropertyAtRisk — Eircode-keyed address ontology (the join target).
• Refuge / CommunitySupportCentre, RoadSegment (closure status), AssetTask (dispatched LA unit), VulnerableSite (consented register entry — aggregate/registered only).
• LocalAuthorityArea — the federation seam; CAPMessage — the audited broadcast artefact.

Relationships: RiverGauge —measures→ Catchment; InundationPolygon —intersects→ PropertyAtRisk (the load-bearing inference — a forecast polygon becomes a street-level warning only when it intersects resolved properties, never a free-floating county polygon); PropertyAtRisk —on-register→ VulnerableSite (consented); FloodEvent —warned-by→ CAPMessage; AssetTask —tasked-to→ RoadSegment|Refuge; LocalAuthorityArea —owns→ AssetTask (per-LA sovereignty).

The inference that earns the platform its keep is intersects: a forecast crest, on its own, is just water that will rise. It becomes a street-level warning only when it joins to Eircode-resolved properties inside the LCC's area — which is precisely the gap the State's county-level warnings leave open.

§5 — Data model (synergy.* with RLS + load-bearing CHECK)

SQL
59 lines
Copy
-- Forecast/observed inundation for an LA's catchments (Met Éireann FFC + OPW CFRAM + SAR).
CREATE TABLE synergy.inundation_polygon (
    id                uuid PRIMARY KEY DEFAULT gen_random_uuid(),
    org_id            uuid NOT NULL,                            -- RLS: app.current_org_id (the LA tenant)
    local_authority_area_id uuid NOT NULL,                     -- federation seam (per-LA sovereignty)
    catchment         text NOT NULL,                           -- 'Slaney' (EPA gazetteer)
    source            text NOT NULL CHECK (source IN ('cfram_q100','ffc_forecast','sar_actual')),
    extent_geom       geometry(MultiPolygon, 4326) NOT NULL,
    valid_from        timestamptz NOT NULL,                    -- forecast issue / SAR pass time
    valid_to          timestamptz,                             -- forecast horizon / next pass
    prov_derived_from text NOT NULL                            -- PROV-O: Met-FFC run_id / Sentinel-1 product ID
);
ALTER TABLE synergy.inundation_polygon ENABLE ROW LEVEL SECURITY;
CREATE POLICY org_isolation ON synergy.inundation_polygon
    USING (org_id = current_setting('app.current_org_id')::uuid);

CREATE TABLE synergy.river_gauge (
    id              uuid PRIMARY KEY DEFAULT gen_random_uuid(),
    org_id          uuid NOT NULL,
    station_code    text NOT NULL,                             -- 'ENNIS01' (OPW/EPA, Fellegi-Sunter resolved)
    catchment       text NOT NULL,
    level_m         numeric(5,2) NOT NULL,                     -- 4.82
    return_period   text,                                      -- 'Q50','Q100','Q200'
    status          text NOT NULL CHECK (status IN ('ok','watch','alarm')),
    recorded_at     timestamptz NOT NULL DEFAULT now()         -- point-in-time, 15-min cadence
);
CREATE INDEX ON synergy.river_gauge (catchment, recorded_at DESC);
ALTER TABLE synergy.river_gauge ENABLE ROW LEVEL SECURITY;
CREATE POLICY org_isolation ON synergy.river_gauge
    USING (org_id = current_setting('app.current_org_id')::uuid);

-- The street-level public warning is a first-class AUDITED entity; broadcast is gated, not a manual export.
CREATE TABLE synergy.cap_message (
    id              uuid PRIMARY KEY DEFAULT gen_random_uuid(),
    org_id          uuid NOT NULL,
    local_authority_area_id uuid NOT NULL,                     -- federation seam
    catchment       text NOT NULL,
    severity        text NOT NULL CHECK (severity IN ('Minor','Moderate','Severe','Extreme')),
    certainty       text NOT NULL CHECK (certainty IN ('Observed','Likely','Possible','Unlikely')),
    urgency         text NOT NULL CHECK (urgency IN ('Immediate','Expected','Future')),
    headline        text NOT NULL,
    instruction     text NOT NULL,
    languages       text[] NOT NULL,                           -- {'ga','en','pl','uk'}
    targets         text[] NOT NULL,                           -- {'eu-alert','rte-radio','lcc-dashboard'}
    source_basis    text NOT NULL,                             -- e.g. 'cfram_q100+ffc+gauge+consented_register'
    art50_watermark boolean NOT NULL DEFAULT true,             -- AI Act Art 50 disclosure
    sign_la_coord   text,                                      -- LA Severe-Weather Coordinator QES, NULL until signed
    sign_lcc_ctrl   text,                                      -- LCC Controller QES, NULL until signed
    broadcast_at    timestamptz,                               -- NULL until fan-out fires
    merkle_leaf     bytea NOT NULL,
    -- LOAD-BEARING INVARIANT: a public warning CANNOT broadcast without 2-of-2 human sign-off.
    -- The DB itself enforces the human gate that §3's decline-safety promise depends on.
    CONSTRAINT human_gate_required CHECK (
        broadcast_at IS NULL OR (sign_la_coord IS NOT NULL AND sign_lcc_ctrl IS NOT NULL)
    )
);
ALTER TABLE synergy.cap_message ENABLE ROW LEVEL SECURITY;
CREATE POLICY org_isolation ON synergy.cap_message
    USING (org_id = current_setting('app.current_org_id')::uuid);

The human_gate_required CHECK is the one invariant that makes the decline-safe promise structural rather than procedural: no code path, fault, or operator can fan a flood warning to the public without two named QES signatures already persisted.

§6 — Action-loop pseudocode (detect → … → close)

Python
46 lines
Copy
def compose_flood_cop(catchment_state, gauges, requesting_org):
    # 1. DETECT — gauge ALARM AND a forecast/observed polygon exceeds the CFRAM Q100 baseline.
    sar_or_ffc_exceeds_q100 = inundation_exceeds(catchment_state, "cfram_q100")        # Slaney t+6h crest
    if not (gauges["ENNIS01"].status == "alarm" and sar_or_ffc_exceeds_q100):
        return Disposition.NO_WARNING

    # 2. ENRICH — join the forecast polygon to Eircode-resolved properties (the load-bearing inference).
    at_risk   = intersect_properties(catchment_state.forecast_polygon)                 # 41 in Q100 envelope
    on_reg    = filter_consented_register(at_risk)                                     # 6 (consented ONLY)
    analogue  = cma_collective_memory.recall_analogue(catchment_state)                 # Storm-Chandra rerun

    # 3. TRIAGE — surface the street-level cluster no single agency tool shows: Q100 inundation ∩ vuln-register.
    cluster = triage_intersection(at_risk, on_reg, roads_flooded(catchment_state))     # Templeshannon/Irish St

    # 4. GATE — human-gated; Art 6(1)(d) vital-interests + 6(1)(e) public-task; Art 50 on AI-drafted text.
    draft = ai_draft_cap(cluster, langs=["ga","en","pl","uk"], model="L3:eurollm-se")
    gate = decision_room(
        proposal  = IssueStreetLevelCAP(cluster, severity="Severe", certainty="Observed"),
        personas  = [OP_TASKING, PROPORTIONALITY, CIVIL_SOCIETY("AlgorithmWatch"),
                     DEVILS_ADVOCATE, DOMAIN_EXPERT("OPW-Hydrology")],
        threshold = P_MIN_TIER2)                                                       # P = 0.91
    if gate.civil_society.flag == "ART50_MISSING":   draft = stamp_art50(draft)        # disclosure catch
    if gate.domain_expert.flag == "GAUGE_DATUM":     draft = caveat_gauge(draft)       # ENNIS01 datum caveat
    if not gate.passed:
        return Disposition.REFUSED(gate.rationale)

    # 5. TASK — Hungarian assignment of LA crews/pumps to priority sectors + refuge openings.
    assignment = hungarian_assign(units=la_crews(requesting_org), demand=lower_slaney_sectors(cluster))
    surface_constraint_failures(assignment)                                            # WTD driving-hours ceiling
    task(assignment)                                                                   # open Town Hall CSC, R744 close

    # 6. EXECUTE — dual-control QES; the DB CHECK also forbids broadcast without both signatures.
    sign_co  = await qes_sign("la.severe_weather_coordinator", draft)
    sign_ctl = await qes_sign("lcc.controller", draft)
    if not (sign_co and sign_ctl):
        audit.append(catchment_state.id, "CAP unsigned -- broadcast withheld", merkle=True)
        return Disposition.WITHHELD
    receipts = cap_fanout(draft, targets=["eu-alert","rte-radio","lcc-dashboard"])
    msg = cap_message(cluster, severity="Severe", certainty="Observed", urgency="Immediate",
                      sign_la_coord=sign_co, sign_lcc_ctrl=sign_ctl, art50_watermark=True)
    write_back("synergy.cap_message", msg, broadcast_at=now(), merkle=True)

    # 7. BDA / CLOSE — delivery confirmation (MNO), observed-vs-forecast inundation, post-event survey.
    register_prospective("flood-forecast-divergence", trigger="|F1_obs - F1_fcast| > 0.05",
                         owner="OPW Senior Hydrologist")
    return Disposition.BROADCAST(receipts)

§7 — nexus-workflows YAML DAG (declarative, blocking human-gate node)

YAML
46 lines
Copy
# nexus-workflows: opw-flood-cop. NO cron — this is the scheduled-task substrate.
# Triggered on Met-FFC advisory ingest for a subscribed LA catchment.
name: opw-flood-cop-slaney
on:
  event: ffc.advisory.ingested
  filter: { catchment: "Slaney", org: "wexford-cc" }
nodes:
  - id: detect
    run: skill/flood-detect          # gauge ALARM ∩ polygon > CFRAM Q100
    out: [catchment_state]
  - id: enrich
    needs: [detect]
    run: skill/property-intersect    # Eircode join + consented-register filter (aggregate only)
    out: [at_risk, on_register]
  - id: triage
    needs: [enrich]
    run: skill/street-level-triage   # Q100 ∩ vuln-register ∩ flooded-roads cluster
    out: [cluster]
  - id: hpc-forecast
    needs: [detect]
    run: skill/hydrology-saint-venant-2d
    dispatch: { cluster: euroHPC-LUMI, gpus: 64 }   # ≤12 min t+6h crest
    out: [forecast_polygon]
  - id: human-gate           # ---- BLOCKING ----
    needs: [triage, hpc-forecast]
    type: human_approval
    blocking: true
    timeout: PT30M
    approvers:
      quorum: 2              # 2-of-2 QES (dual-control)
      roles: [la.severe_weather_coordinator, lcc.controller]
    decision_room:
      personas: [op_tasking, proportionality, civil_society_algowatch,
                 devils_advocate, domain_hydrology]
      threshold: P_MIN_TIER2
    on_reject: { goto: close, disposition: REFUSED }
  - id: task
    needs: [human-gate]
    run: skill/hungarian-assign      # crews/pumps/refuge; surface WTD constraint failures
  - id: execute
    needs: [human-gate, task]
    run: skill/cap-fanout            # EU-Alert + RTE + LCC-dashboard; write-back synergy.cap_message
  - id: close
    needs: [execute]
    run: skill/bda-capture           # MNO delivery + observed-vs-forecast + post-event survey
    out: [prospective_item]

§8 — UI/UX mockups (verbatim generated ASCII)

The two ASCII blocks below are the exact stdout of _build/archetypes/gen_opw-meteireann-flood.py (generated, not hand-typed; _ck() alignment-guarded).

Figure A03.1 — map_ops (PRIMARY): Street-Level Flood COP — Enniscorthy / River Slaney. Components: ShellLayout + TopBar (with PccPill 4⟳ in rightSlot + RendererChip = MapLibre-3D-terrain) + LeftSidebar glyph-rail + LAYERS panel + MapConsole rendering the CFRAM Q100 AFA envelope, Met Éireann FFC t+6h forecast crest, OPW/EPA gauge ENNIS01, the consented vuln-register triage cluster, refuge/CSC and road closures + INCIDENTS ticker + BottomStatusBar + ClassificationBanner. (Bespoke SVG twin: _build/figures/opw-meteireann-flood/uc-map_ops.svg.)

Figure — Operational picture (map_ops · live MapLibre). Production-fidelity React surface (buildable); the faithful ASCII follows.

+------------------------------------------------------------------------------------------------------+
| Street-Level Flood COP - Enniscorthy / Slaney - Storm Chandra replay (MapConsole + MapLibre-3D)      |
+--------------------+---------------------------------------------------------------------------------+
| LAYERS             | MAP  ========================================================================== |
| [x] Met FFC fcast  |   Enniscorthy, Co. Wexford  (Wexford CC Local Co-ordination Centre / LCC)       |
| [x] CFRAM Q100 AFA |   |   ### Met Eireann ORANGE rainfall + FFC fluvial advisory: Slaney ###        |
| [x] River gauges   |   |                                                                             |
| [x] Rain radar     |   ~~~~~~ River Slaney ~~~~~~  gauge ENNIS01 4.82m  Q100 ALARM                   |
| [x] Property@risk  |   |   CFRAM Q100 AFA envelope ====  FFC t+6h forecast crest :::::               |
| [x] Roads/closures |   o TEMPLESHANNON  Irish St / Mill Park Rd  WATER OVER ROAD <!>                 |
| [x] Refuge/CSC     |   |   >> 41 properties in Q100 envelope | 6 on consented vuln list              |
| [~] Vuln register  |   o ABBEY QUAY     quay wall overtop risk at high water 11:48                   |
| [ ] Pump/defence   |   |   N11 Wexford-rd FLOODED at Edermine; R744 closed (LA crews)                |
|                    |   o BLACKSTOOPS    surface-water ponding; 2 homes cut off                       |
| REPLAY             |   |                                                                             |
| Storm Chandra      |   REFUGE: Enniscorthy Town Hall (CSC) STAGING; St Aidan's hall READY            |
| Jan 2026 (rerun)   |                                                                                 |
| [<<] t+04:10 [>>]  |   STREET-LEVEL TRIAGE: Templeshannon = Q100 inundation n 6 vuln-reg             |
|                    |   replaces 'county-level warning that told people nothing re street'            |
| SOURCES            |   Proportionality P=0.91 | HUMAN SIGN-OFF required before any order             |
| Met Eireann FFC    |   [ Open Decision Room ]  [ Hold + re-poll gauge 15m ]  [ Drop pin ]            |
| OPW floodinfo.ie   |                                                                                 |
| OPW/EPA gauges     |                                                                                 |
| LA road + register |                                                                                 |
+--------------------+---------------------------------------------------------------------------------+
| INCIDENTS: 11:12 ENNIS01 4.82m Q100 ALARM | Slaney over Irish St | 41 props AFA | 6 vuln-reg | CSC up|
+------------------------------------------------------------------------------------------------------+

Figure A03.2 — cap_composer: Street-Level Alert + Refuge Activation — Templeshannon. Components: the §3.10 CAP composer surface inside ChatTerminal/write-back context — alert form (Event/Area/Onset/Headline/Instruction/Languages/Expires), the severity×certainty matrix, the Article-50 AI-disclosure watermark toggle, the explicit decline-safe source-basis line, the 2-of-2 dual-control panel, the fan-out targets, and the [ Preview CAP-XML ] [ /dual-control sign ] [ Broadcast ] action bar.

Figure — Alert composer (CAP 1.2 write-back). Production-fidelity React surface (buildable); the faithful ASCII follows.

+----------------------------------------------------------------------------------------------+
| Street-Level Alert + Refuge Activation - Templeshannon (cap_composer write-back)             |
+--------------------------------------------------+-------------------------------------------+
| Event:    Fluvial flood - River Slaney           | SEVERITY x CERTAINTY                      |
| Area:     Templeshannon ED + Irish St (Y21)      |           Obs  Likely Poss                |
| Onset:    Immediate (replay t+04:10, crest ~+2h) |  Extreme   .    .     .                   |
| Headline: Move from ground floor - Templeshannon |  Severe   [X]   .     .                   |
| Instruction:                                     |  Moderate  .    .     .                   |
|   Slaney is over Irish St and rising to the FFC  | Urgency: Immediate                        |
|   forecast crest by ~13:00. Move people and pets |                                           |
|   to a higher floor or to Enniscorthy Town Hall  | TARGETS (fan-out)                         |
|   refuge. If on the vulnerable register with no  |  [x] EU-Alert / 112 cell                  |
|   transport, call the LCC line - crews will call.|  [x] RTE / South-East radio               |
| Languages: [ga] [en] [pl] [uk]                   |  [x] LCC dashboard (PRAs)                 |
| Expires:   11:18 +8h                             |  [x] Wexford CC alerts                    |
|                                                  |  [ ] EU-CECIS (NDFEM only)                |
| Art-50 AI-disclosure watermark: [x] ON           |                                           |
| Source basis: OPW CFRAM Q100 + Met FFC forecast  | DUAL-CONTROL 2/2 QES                      |
|   + OPW/EPA gauge ENNIS01 + consented register   |  sign 1: LA Severe-Wx Coord               |
|   (NO inference, NO individual risk-scoring)     |  sign 2: LCC Controller                   |
+--------------------------------------------------+-------------------------------------------+
|  [ Preview CAP-XML ]   [ /dual-control sign ]   [ Broadcast ]                                |
+----------------------------------------------------------------------------------------------+

§8b — Field-unit (Pixel) surfaces

The same scenario on the Pixel 10 Pro Fold field unit (Nexus Field app), tightly coordinated with the dashboard COP above — command pushes the task, the unit accepts + ACKs, shares position and reports back to the COP. Built on the same synergy.field_unit / field_task / field_report contract; see §9 and the cluster coordination composite.

Figure §8b.1 — Folded cover · tasking glance (ground_glance): the incoming IMMEDIATE task, ACCEPT + ACK, alert chips, bearing-to-objective.

Figure §8b.2 — Unfolded inner display · field COP: two-pane mini-map + task list + teammate roster + air/command coordination + PTT, with the Material-3 NavigationBar + Report FAB.

§9 — UI/UX flow (literal click-path)

The Severe-Weather Coordinator's interaction path through this page's buttons:

MapConsole scrubber [▶▶ t+04:10] → gauge ENNIS01 glyph turns red (Q100 ALARM) → toggle [x] CFRAM Q100 AFA + [x] Met FFC fcast → MapConsole auto-surfaces the Templeshannon triage cluster (Q100 ∩ 6 consented-vuln-register) → click [ Open Decision Room ] → review the five-persona dialectic in the right-docked ChatTerminal → the AlgorithmWatch + OPW-Hydrologist edits flow into the draft → switch to the cap_composer surface → confirm Art-50 watermark: ON and the source-basis line → [ /dual-control sign ] (2-of-2 QES) → [ Broadcast ] → HistoryRail logs the PROV-O entry; scrub back any time to replay who knew what, when.

[MapConsole replay] --gauge ALARM--> [Triage cluster auto-surfaced]
        |                                      |
        v                                      v
[ Open Decision Room ]  --5-persona gate-->  [ cap_composer ]
        |  (edits flow into draft)              |  Art-50 ON
        v                                      v
[ /dual-control sign 2/2 ] ---------------> [ Broadcast ] --> [HistoryRail PROV-O + BDA close]

§10 — Decision-Room transcript (the gated decision)

The Decision Room convenes the moment the FFC t+6h Saint-Venant crest crosses the CFRAM Q100 envelope for the Slaney and the triage classifies Templeshannon above the Severe threshold. Hosted on the right-docked ChatTerminal of the Wexford LCC Coordinator's session.

▸ EU-RESTRICTED · TLP:AMBER · CIVIL-PROTECTION · DEMO (Storm-Chandra replay) ◂

⊟ Op-tasking persona  [L3 EuroLLM]
   Issue Severe/Observed CAP for Templeshannon ED + Irish St; open Town Hall CSC;
   task 2 LA crews to R744 closure + door-knock the 6 consented-register addresses.

⊟ Proportionality persona  [L3 Mistral-Large]   P=0.91 [N:0.96 P:0.90 L:0.88]
   Necessity: imminent fluvial inundation ≥ Q100 proven by gauge ENNIS01 (Observed) +
   FFC crest. Least-intrusive: SMS + EU-Alert cell-broadcast + refuge; NO door-to-door
   evacuation order yet — voluntary relocation guidance first.

⊟ Civil-society persona  [AlgorithmWatch, L3]
   STOP: the draft CAP is AI-assisted but carries no AI Act Article-50 disclosure.
   Add it. Second flag: the instruction says "move to higher ground" — but Irish St
   has ground-floor-only terraces with no upper floor; point those residents to the
   refuge, not "upstairs". REVISE.

⊟ Devil's advocate  [L2 Mistral-7B local]
   Is ENNIS01 reading real or a stuck sensor? Last calibration date? If the gauge is
   the only Observed evidence and rain radar is easing, we risk a false Severe.

⊟ Domain expert  [OPW Senior Hydrologist, L3]
   ENNIS01 calibrated 2025-11; cross-checks against the upstream Scarawalsh gauge
   (also rising). Reading is sound — datum caveat is +/-0.04m, immaterial at 4.82m.
   Hold Severe. Crest confidence good for ~13:00.

GATE VERDICT — ACCEPT (revised):
  • Art-50 disclosure ADDED (AlgorithmWatch).
  • "Higher ground" -> "higher floor OR Town Hall refuge" for Irish St terraces (AlgorithmWatch).
  • Severity HELD at Severe/Observed (OPW Hydrologist confirmed gauge; Devil's advocate satisfied).
  • P=0.91 ≥ P_min(Tier-2)  ·  2-of-2 dual-control required.
[ /dual-control sign 2/2 ]   [ /execute → CAP + LCC-CAD ]   [ Refuse + log ]
▸ EU-RESTRICTED · TLP:AMBER ◂

The dialectic is load-bearing: AlgorithmWatch's two catches (missing Art-50 disclosure; the ground-floor-terrace evacuation-guidance error) both change the executed message before the gate accepts. The civil-society reviewer is seated inside the decision, not consulted afterward.

§11 — Write-back + BDA + PROV-O + deltas-only regulatory traceback

Write-back (three sinks).

1. CAP-message broadcast → CAP-IE-Gateway pattern: CAP 1.2 XML, info/category=Met, info/event=flood, info/severity=Severe, info/urgency=Immediate, info/certainty=Observed, with the Article-50 AI-disclosure boilerplate embedded in info/description. Lawful basis: Decision 1313/2013/EU Art 17 (EU Civil Protection Mechanism) + national FMEM.
2. LCC dispatch instruction → Wexford CC CAD / LCC dashboard (the per-LA endpoint). Lawful basis: Local Government Act 2001 + FMEM.
3. EU-Alert cell-broadcast → EU-Alert/112 gateway (cell-broadcast to handsets in the Templeshannon polygon). Lawful basis: European Electronic Communications Code public-warning obligation.

BDA (loop close). Loop 1 (T+30 min): MNO cell-broadcast delivery-confirmation counts (ObsLvl 4, direct from operator infra). Loop 2 (T+6 hr): observed inundation vs FFC forecast — next gauge/SAR pass is the ground-truth; the model F1 logs back to MLflow for emulator-retraining. Loop 3 (T+72 hr): residual property damage vs PropertyAtRisk forecast — OPW post-event survey. ProspectiveItem flood-forecast-divergence (trigger |F1_obs − F1_fcast| > 0.05, owner OPW Senior Hydrologist) closes the model-lifecycle loop.

PROV-O attribution chain (finding → close).

[entity:Met-FFC-Slaney-advisory-2026Jan]
   ↑ wasDerivedFrom  [entity:Met-Eireann-ECMWF-ensemble]  ↑ wasAttributedTo [agent:Met-Eireann]
   ↓ wasGeneratedBy  [activity:Saint-Venant-solve-LUMI]   ↑ used [entity:OPW-CFRAM-Q100-AFA]
                                                           ↑ wasAttributedTo [agent:OPW]
   ↓ informed         [activity:Decision-Room-Slaney-2026]
   ↑ wasInformedBy   [agents: LCC-Coordinator + Op-tasking + Proportionality
                              + AlgorithmWatch + OPW-Hydrologist + Devils-Advocate]
   ↓ wasGeneratedBy  [entity:Dual-control-signature-set] ↑ wasAttributedTo [agent:LA-Coord + LCC-Controller]
   ↓ wasGeneratedBy  [activity:Hungarian-asset-assignment]
   ↓ wasGeneratedBy  [entity:CAP-message-IE-WX-Slaney-2026]
   ↑ wasAttributedTo [agent:Wexford-CAP-Composer]
   ↓ wasUsedBy       [activity:EU-Alert-broadcast]
   ↓ wasGeneratedBy  [entity:BDA-MNO-delivery-confirmation-T+30min]

Every node carries agent + activity + entity; Merkle-anchored. The Article-50 disclosure surfaced by AlgorithmWatch becomes a discoverable provenance edge — if a resident later challenges the alert, the PROV-O graph proves the disclosure was carried.

Regulatory traceback (deltas only — what differs from the §4.0 defaults). EU AI Act Article 50 transparency applies to the AI-drafted CAP text (disclosure watermark, enforced in-dialectic). The system is not Annex-III high-risk: hydrological flood-extent is not on the Article-5 prohibited list and carries no individual profiling — but the FRIA workflow still runs to evidence that. GDPR: the consented vulnerable-register layer is aggregate/registered only (Art 6(1)(d) vital-interests + 6(1)(e) public-task; no Art-9 special-category processing in this pillar). AI Act Article-5 prohibitions became applicable 2 February 2025 [verified] — none are engaged here, which is the whole point of the decline-safe slice.

§12 — Buyer & stakeholders

• Economic buyer (most likely): OPW (flood capital line + national mandate) and/or DHLGH–NDFEM (owns the FMEM). A national-tier deployment likely needs both. [Named official contact TBD]
• Operational champion (best entry): a repeatedly-flooded LA Severe-Weather Coordinator / Director of Service — Wexford CC (Enniscorthy) is the named beachhead; Kilkenny, Roscommon, Cork, Limerick are alternates. [Named contact TBD]
• Technical authority / partner (not a buyer to displace): Met Éireann FFC — data provider + credibility gate. [Named FFC contact TBD]
• Influencers: CCMA; Regional + National Steering Groups; NDFEM.
• Political sponsor: Minister of State Kevin "Boxer" Moran (OPW) — public face of flood funding. [verified — public role]
• Detractors / friction: Met Éireann may perceive overlap with its Phase-2 plan; OGP/OGP procurement rules; LA budget fragmentation; "we already have a 10–15-year programme" inertia.

§13 — Competition / incumbency + comparator (cited)

• Met Éireann's own FFC / Phase-2 programme — the principal "incumbent," but a 5–10-year build and a partner-shaped gap, not a deployed competitor. Position as the operational layer that delivers now and consumes FFC output. [verified — RTÉ 19 Mar 2026]
• Esri / ArcGIS — heavily embedded across Irish LAs and OPW (floodinfo.ie is Esri-served). Real incumbency for mapping, but Esri is analytics/mapping, not a sovereign closed-action-loop with human-gated tasking, write-back, and an auditable Decision Room. Our moat is the action loop + sovereignty + auditable decision trail, sitting above the GIS layer. [verified — floodinfo.ie / Esri Ireland public deployments]
• Generic EM/GIS vendors — present, but no dominant Irish flood-COP incumbent; the field is open precisely because the State's own solution is years away.
• Comparator (one line): Esri ArcGIS = the embedded mapping substrate (we integrate, don't displace); MapAlerter-style tools = public alerting, not a multi-agency responder COP with a gated action loop. Sovereignty is a genuine edge for critical national infrastructure vs US-headquartered platforms.

§14 — Readiness (honest, pre-pilot)

• Stage: pre-incorporation, pre-revenue, pre-pilot. The disaster pillar is core to the product thesis but is not a deployed, Irish-feed-integrated flood system.
• Real, reusable assets: triple-renderer MapConsole, customer-editable ontology, closed-action-loop architecture, classification-aware AI Provider Router, FRIA + provenance/transparency conformity machinery, the HistoryRail bitemporal playback (the storm-replay timeline + after-action audit), COP entity model + picture API, dual-control sign-off primitives. Genuine and on-thesis.
• Honest gaps: no live integration with Met Éireann FFC models, OPW/floodinfo.ie CFRAM layers, or OPW/EPA gauge feeds; no deployed LCC instance; no Irish entity; no reference customer; the multi-agency write-back adapters for Irish PRA workflows are unproven; the storm-replay demo itself is build-spec, not built.
• Implication: strong narrative + architecture fit, but a flood pilot is a build, not a demo-and-deploy. Discovery + a focused integration sprint precede any credible LOI. (This is the honest reason demonstrability scores 2, not 5, in §18.)

§15 — ENGAGEMENT PLAYBOOK (first-contact → signed contract)

Each stage: trigger / owner / activity / template-or-script / exit criterion / deliverable.

Stage 1 — First contact (warm intro). Trigger: the storm-replay flood lens is demo-ready on Wexford geography. Owner: Founder + Patrick Walsh (warm-intro broker). Activity: a single named ask to a storm-hit LA Severe-Weather Coordinator. Template (adapted from outreach-drafts §1/§3):

"Patrick — one specific ask: an intro to the Wexford CC Severe-Weather Coordinator so I can show a Storm-Chandra street-level flood replay on the Slaney — the picture that answers the 'county-level warning told people nothing about their street' problem. Free discovery, no cost, no obligation. One build opens the whole civil-protection cluster." Exit criterion: a 60-minute discovery slot booked. Deliverable: calendar invite with the lightweight agenda; mutual NDA signed in the founder's own name (s.45-ratifiable).

Stage 2 — Free discovery (60 min). Trigger: slot booked. Owner: Founder. Activity: listening session, no slides — map the real LCC flood workflow against the 8-stage loop. Script (the discovery-playbook §3 agenda, flood-instantiated): 0:00 frame + permission ("discovery, not a pitch"); 0:05 "walk me through the last flood from gauge-alarm to stand-down — who touched it, in what order?"; 0:20 "what's the lawful basis for the vulnerable register? is any of it special-category?"; 0:35 "who owns the LCC budget? is there a Minor-Works/DTIF line this could ride?"; 0:45 sketch their loop on the 8 stages, find where they jump detect→act with no enrichment/gate; 0:55 reflect back top-3 pains, ask for the demo slot. Exit criterion: named sponsor agrees there is a problem worth solving + Declined-List PASS. Deliverable: same-day discovery write-up (sponsor, top-3 pains in their words, lawful basis, action-loop gap, funding vehicle hinted).

Stage 3 — Scoped demo (30 min). Trigger: sponsor asks to see it on their data-shape. Owner: Founder. Activity: replay Storm Chandra on the Slaney/Enniscorthy geography using floodinfo.ie CFRAM layers + a sample FFC-style crest; run the action loop end-to-end through the human-gated sign-off; lead with sovereignty (AI Provider Router refuses out-of-jurisdiction calls), the Article-50 disclosure, the 5-persona Decision Room, and the published Declined List. Script: the storm-replay 5-beat narrative (warning → impact → street-level triage → human-gated decision → write-back + audit). Exit criterion: sponsor asks "could we try this on a real slice?" Deliverable: the 1-page leave-behind (lens screenshot + the Storm-Chandra/Minor-Works mandate it answers).

Stage 4 — Pilot (grant- or Minor-Works-funded, 6–12 wk). Trigger: demo exit ask answered yes. Owner: Founder + Met Éireann/CeADAR partner. Activity: time-boxed operational pilot at one LCC for the Slaney catchment; build the live FFC/OPW/gauge integrations; validate against a real event or a tabletop exercise. Template — 1-page pilot proposal, filled for this buyer:

Title: Slaney Street-Level Flood COP pilot — Wexford CC LCC. Sponsor: Wexford Severe-Weather Coordinator (budget: OPW Minor-Works / DTIF Call-8 consortium). The one thing we will prove: "We can fuse Met-FFC crest + OPW CFRAM + ENNIS01 gauge into one street-level picture and cut warning lead-time for the Templeshannon/Irish-St cluster from [baseline TBD wk1] to [target TBD wk1]." In scope: map_ops + cap_composer + Decision Room + HistoryRail on the Slaney; consented register only. Out: any other catchment; any individual scoring; everything on the Declined List. Data & lawful basis: floodinfo.ie CFRAM (public) + FFC sample + OPW/EPA gauges + consented LA register; EU-hosted; EU-RESTRICTED isolation tier. Success criteria: 2–4 sponsor-agreed metrics (lead-time, % properties correctly in-envelope, audit-completeness). Timeline: 8 weeks, mid-point checkpoint wk4. Commercials: €0 to the LA if grant-funded; production band Tier-1 €120–240k/yr noted only if asked. Funding vehicle: DTIF Call-8 consortium (Nexus + Wexford CC + Met Éireann/CeADAR) or Minor-Works. After: an LOI if criteria met. Exit criterion: success criteria met or credibly trending. Deliverable: pilot results pack + after-action audit replay.

Stage 5 — LOI / pilot MOU (the milestone). Trigger: pilot criteria met. Owner: Founder + EEA-resident director cover (Patrick/Manuel). Activity: capture documented intent. Template — LOI checklist (discovery-playbook §6): parties (LA + founder in own name, NewCo to ratify under CA 2014 s.45); conditional statement of intent; scope carried from the pilot; success criteria referenced; named sponsor; indicative timeline + next step; indicative commercials ("to be scoped under [procurement vehicle]"); conditions (funding award / DPA / accreditation); explicitly non-binding except confidentiality; Irish governing law; Declined-List affirmation; signatures; ⚖️ solicitor review before sending. Exit criterion: signed LOI naming sponsor + next step. Deliverable: the signed LOI (triggers the Patrick check).

Stage 6 — Signed contract. Trigger: LOI + a contracting vehicle exists (Stamp-4 or partner-vehicle) + procurement route clear. Owner: the contracting entity (NewCo / partner) + buyer procurement. Activity: convert via Minor-Works/DTIF grant or OGP framework; multi-LA or national roll-up. Exit criterion: executed contract. Deliverable: signed agreement + production deployment plan.

§16 — PM / timeline

Stage \ Month        M1   M2   M3   M4   M5   M6   M7   M8   M9   M10  M11  M12  M13  M14
1 First contact      ####
2 Free discovery       ####
3 Scoped demo            #####
4 Pilot (grant)            ##############################
5 LOI / MOU                                          ######
6 Contract (paid)                                       *====gated on Stamp-4/partner-vehicle====>
Funding (DTIF C8)    ....::::::::AWARD::::::::........................
Legal gate (V)       V=0.10 ---------------> V=0.45 (partner) -----> V=0.75/1.0 (vehicle/Stamp-4)

Milestones: M2 discovery write-up + Declined-List PASS · M3 scoped demo accepted · M4–M9 funded pilot (mid-point M6) · M10 success criteria signed off · M11 LOI signed (Patrick-check) · M12+ paid contract (gated). Critical path: the Stamp-1G → Stamp-4 / partner-vehicle gate is critical for a PAID pilot or contract — discovery, demo, and even a grant-funded pilot can proceed before it resolves, but no founder-signed paid agreement can. t_resolve ≈ 14 months is dominated by this plus the State/LA cycle and DTIF-Call-8 timing.

RACI.

§17 — Funding / procurement vehicle

• DTIF (Disruptive Technologies Innovation Fund) — €500m fund (DETE/Enterprise Ireland); Call 7 awarded €159m, Dec 2025, climate among themes; Call 8 expected imminently. A consortium (Nexus + Wexford CC + Met Éireann/CeADAR) bidding a localised-flood-warning + multi-agency-COP project is a strong decline-safe fit. [verified — Silicon Republic; DETE] Contact: DTIF@enterprise-ireland.com.
• OPW Minor Flood Mitigation Works & Coastal Protection Scheme — LA-administered, threshold now €2M (95% OPW contribution); the >€6.6m Storm-Chandra tranche flowed through here — a realistic near-term LA-level pilot vehicle. [verified — gov.ie 25 May 2026]
• NDP flood capital — multi-billion-euro flood line via OPW; largely capital-scheme oriented but operational tooling can ride alongside. [verified — gov.ie / Construction Ireland]
• EU civil-protection / climate-adaptation — UCPM + EU Mission on Adaptation funding lines (Minor Works is itself listed on Climate-ADAPT). [verified — climate-adapt.eea.europa.eu]
• Procurement reality: State/LA buying is OGP/eTenders-governed, slow, competitive. A grant-funded pilot that sidesteps full competitive procurement is the fastest path to first money.

§18 — TWO-STAGE FORMULA SCORECARD

Every factor cell is [PRIOR] with a dated one-line rationale (2026-06-05).

Stage-1 (P_LOI), vector {mandate_pull, access_warmth, demonstrability, decline_safety, white_space, cycle_speed, pillar_fit}:

S1 = 3.14 → P_LOI = 0.55 / (1 + exp(−1.15·(3.14 − 2.6))) = 0.358 → 35.8% [PRIOR]. Score100 = S1·20 = 62.8.

Stage-2 (P_raw), vector {contractability, funding_to_pay, procurement_clarity, incumbency_displacement, time_to_value, reference_leverage}:

S2 = 2.64 → P_raw = 0.70 / (1 + exp(−1.1·(2.64 − 2.8))) = 0.319 → 31.9% [PRIOR].

Legal gate G = V·T. T = min(1, max(0, (30 − 14)/30)) = 0.533 (t_resolve = 14 mo).

• V=0.10 (solo Stamp-1G, today): G=0.053 → P(Contract) = P_LOI·G·P_raw = 0.61% [PRIOR]; P(Contract|LOI)=1.7%.
• V=0.45 (Dogpatch-brokered/partner in discussion): G=0.24 → P(Contract) = 2.74% [PRIOR]; P(Contract|LOI)=7.7%.
• V=0.75 (confirmed contracting prime/partner): G=0.40 → P(Contract) = 4.57% [PRIOR]; P(Contract|LOI)=12.8%.
• V=1.00 (Stamp-4 + incorporated & trading): G=0.533 → P(Contract) = 6.09% [PRIOR]; P(Contract|LOI)=17.0%.

Reconciliation to board_anchor. Anchor band: score100 60.6, to-LOI 22–35%, to-buy 13–21%, value high. Computed Score100 = 62.8 — within ~2.2 pts of 60.6 (inside the ±5 tolerance), reconciled. P_LOI 35.8% sits just at/above the top of the 22–35% to-LOI band (acceptable for a [PRIOR]); to-buy is the longer-horizon figure that the V=0.75/1.0 gate + an early civil-protection reference move toward the 13–21% band over the conversion horizon.

§19 — Commercial

• Tier-1 (single-LA LCC operational layer): €120–240k/yr ACV. Terms: annual SaaS + sovereign-hosting; pilot often €0 if grant-funded. Requirements: floodinfo.ie/FFC/gauge data-access, a DPA, EU-RESTRICTED isolation.
• Tier-2 (LA-cluster / regional MEM): ~€500k–€1.2m/yr. Terms: multi-tenant federation across an MEM region; per-LA sovereignty seam.
• Tier-3 (national MEM + Met-/OPW-integrated COP): €2.4–4.8m/yr. Requirements: NDFEM/CCMA standard adoption, national procurement, accreditation; multi-year.
• Value band: high (the card's €500k–€2.4m annual potential), with a national deployment reaching toward very-high over multiple years. Cost advantage: open-source substrate + sovereign HPC + shared conformity file + no forward-deployed-engineer dependency.

§20 — Legal blockers

• X1 — Stamp-1G (founder). Cannot be director/shareholder/self-employed or sign a paid contract until Stamp-4 or a partner vehicle exists. Applied here: discovery + demo + a grant-funded pilot can proceed (no founder paid-contract); a paid pilot/contract is gated. Mitigation: EEA-resident director cover (Patrick/Manuel) or partner contracting vehicle; pursue Stamp-4. ⚖️ CONFIRM — immigration solicitor (irishimmigration.ie). This is the critical-path gate (§16).
• X2 — EU AI Act. Article-5 prohibitions applicable 2 February 2025 [verified] — none engaged (decline-safe slice). Article-50 transparency applies to AI-drafted CAP text (handled in-dialectic). Not Annex-III high-risk (hydrological extent, no profiling), but FRIA still evidences it. ⚖️ CONFIRM per-use-case.
• X3 — GDPR / data residency. The consented vulnerable-register layer = aggregate/registered only, EU-hosted, DPA per buyer; no Art-9 special-category processing in this pillar. [verified posture]
• X7 — Pre-incorporation contracting. Founder personally liable on any agreement until NewCo formed; sign NDAs/MOUs in own name under CA 2014 s.45, solicitor-reviewed. ⚖️ CONFIRM.
• Buyer-specific: OGP multi-body procurement (slow); vulnerable-person data governance (mitigated by consented/registered-only rule, no inference, no individual scoring); Met Éireann partner-or-threat determination is decisive and must be settled in discovery.

§21 — Warm-intro contact + the specific ask

• Primary: Patrick Walsh (Founder/CEO, Dogpatch Labs) — patrick@dogpatchlabs.com [verified]. The specific ask: an introduction to the Wexford County Council Severe-Weather Coordinator (or another storm-hit LA: Kilkenny/Roscommon) for a free discovery + a Storm-Chandra street-level flood replay on the Slaney — explicitly framed as the operational layer answering the "county-level warning told people nothing about their street" gap, complementary to Met Éireann's FFC, not a competitor. Confirm whether Patrick has a direct, reachable OPW/DHLGH/Met/LA contact (this single fact is the §18 access_warmth score-limiter).
• Parallel delivery warm: Ricardo Simón Carbajo (CeADAR/UCD) [verified] — as the academic/delivery partner for a DTIF Call-8 flood consortium and the Innovation-Voucher route.

§22 — Open questions + consolidated Sources

Open questions (drive the score; resolve in discovery):

1. Does Patrick have a direct, reachable contact at OPW / DHLGH-NDFEM / Met Éireann / a specific LA? (Drives access_warmth — currently the binding limiter at 1.)
2. Exact timing + themes of DTIF Call 8 — is a flood/civil-protection theme explicitly eligible? (Verify with DTIF@enterprise-ireland.com on open.)
3. Real licensing/data-access posture of Met Éireann FFC catchment outputs + OPW floodinfo.ie CFRAM layers + OPW/EPA gauges for a third-party COP. (Build dependency — drives demonstrability.)
4. Which single LA is the best beachhead — Wexford (Storm-Chandra funding) vs Roscommon (active scheme)? Confirm LA-tier budget authority.
5. Does Met Éireann view a third-party operational COP as complementary or competitive? (Partner-or-threat — decisive.)
6. Appetite at NDFEM/CCMA for a national multi-LA COP standard vs LA-by-LA adoption? (One high-band account vs a slow 31-LA roll-up.)

Sources (web-verified 2026-06-05):

• RTÉ — street-level warning gap, "5–10 years," Storm Chandra: 12 Apr 2026, 19 Mar 2026, citizen flood app 18 May 2026.
• Irish Times — "who is in charge?" flood-warning editorial: 22 Mar 2026.
• gov.ie (OPW) — Minor-Works €2M threshold + €3m blockage fund + €6.6m post-Chandra: press release, 25 May 2026; Minor-Works scheme page.
• Met Éireann — Flood Forecasting Centre: met.ie FFC; gov.ie FFC briefing.
• OPW CFRAM / floodinfo.ie: gov.ie CFRAM; floodinfo.ie Minor Works.
• FMEM / PRAs: gov.ie FMEM collection; EU civil-protection Ireland.
• DTIF Call 7/8: Silicon Republic (Call 7, €159m, Dec 2025); DETE DTIF.
• EU Mission on Adaptation (Climate-ADAPT, Minor Works listing): climate-adapt.eea.europa.eu.
• EU AI Act Article-5 applicability 2 February 2025; Article-50 transparency: EUR-Lex Regulation (EU) 2024/1689.

---