Nexus Synergy Engagement Package — A05 · Dublin City Council / LGMA
Nexus Synergy Engagement Package — A05 · Dublin City Council / LGMA
Standing banner (read first). Nexus Synergy Ltd is pre-incorporation, pre-revenue, pre-pilot; Dublin City Council / LGMA is a TARGET, not a customer, partner, or reference. The ~178-surface UI gallery is a gallery, not traction. Every probability in this package is
[PRIOR]— a subjective pre-pilot estimate for prioritisation, not a forecast. Anti-cookie-cutter: the §8 mockups are GENERATED for this buyer's entities (Ballymun / Tolka / DFB / Local Critical Entities Group), not a reused shell. Decline-safe framing only: local-authority emergency-management coordination + consented vulnerable-person outreach — explicitly NOT predictive policing, biometric ID, emotion recognition, social scoring, untargeted scraping, or psychometric profiling. Status honesty: Dublin Fire Brigade signed a new Esri Ireland ArcGIS deal in January 2026 — we sit above it as the cross-agency Local-Critical-Entities-Group decision layer; we never claim to displace it.
§0 — Header & one-line thesis
Package: Dublin City Council / LGMA — Local Critical Entities Group situational awareness + consented vulnerable-person outreach. Volume A (civil protection), ord a05, tier NEXT.
Thesis (one line): Dublin City Council, lead local authority for the East Region Major Emergency Management framework, has a brand-new statutory and review-driven mandate to stand up a Local Critical Entities Group (LCEG) and to reach vulnerable people during severe weather — but no single tool fuses ESB / Uisce Éireann / Gas Networks / telecoms / An Post and a consented vulnerable register into one cross-agency operating picture, which is exactly the human-gated, fully-audited coordination layer we sit above the freshly-bought Esri GIS to provide.
§1 — Entity snapshot (cited)
- Buyer of record: Dublin City Council (DCC) — the lead local authority for Smart Dublin (the joint initiative of the four Dublin local authorities) and for the East Region within the national Framework for Major Emergency Management. [verified — dublincity.ie major-emergency-planning]
- Operational champion (the wedge): Dublin Fire Brigade (DFB) — Emergency Management section. The Senior Fire & Emergency Management Officer chairs the DCC Crisis Management Steering Group, sits on the East Regional Working Group sub-groups, and convenes the Severe Weather Assessment Team (SWAT). [verified — dublincity.ie; DCC severe-weather press release Nov 2025]
- Co-buyer / standards owner: LGMA (Local Government Management Agency) — the shared-services body that coordinates across all 31 local authorities; the natural route to scale one LA pilot to the sector. [likely — LGMA is the LA shared-services agency]
- Procurement front door: Smart Dublin, running the Enterprise Ireland SBIR (Small Business Innovation Research) pre-commercial procurement — company-direct (no academic partner required), two phases (feasibility → prototype), contract paid to the SME. [verified — Smart Dublin / Enterprise Ireland SBIR]
- Profile: A public body. Decline-safe by construction when scoped to coordination + consented outreach. Deep, expanding Esri/ArcGIS estate at DFB (new Jan-2026 deal). [verified — Esri Ireland, Jan 2026]
V_today (legal-gate vehicle value): 0.10 (founder solo on Stamp 1G). t_resolve: 14 months to a signable position. board_anchor: score100 = 64, to-LOI 22–35%, to-buy 13–21%, value med.
§2 — The pain (web-verified, dated, cited)
- Storm Éowyn (24 Jan 2025) — the most damaging Irish storm on record; ESB called the infrastructure damage "unprecedented," with a peak of ~768,000 customers off supply (~30% of the population). Many areas lost power and communications simultaneously — the failure mode no single agency tool surfaces. [verified — esb.ie; NDFEM review]
- NDFEM Review of Storm Éowyn (published 21 Oct 2025). Two recommendations define this buyer's mandate: strengthen local critical-infrastructure coordination groups (linking ESB Networks, Uisce Éireann, the IFA and forestry contractors with local councils — the partner set the review actually names, reflecting Éowyn's power/forestry failure mode), and find ways for service providers to better share information about vulnerable customers so responders can reach them — the review explicitly flags "a high degree of reluctance by organisations to take on additional responsibility for data sharing of any personal detail on vulnerable persons." It also recommends a Community Support Centre Activation Guide (predefined emergency hubs activated at short notice as a link to isolated/vulnerable residents) and advising the public to be able to survive 72 hours without services. [verified — gov.ie / Irish Times 21 Oct 2025]
- EU Critical Entities Resilience (CER) Directive → Irish law. Transposed via S.I. 559/2024; the National Strategy on the Resilience of Critical Entities (published 19 March 2026, titled 2026–2029) names 11 sectors with the Department of Defence as single point of contact; critical entities must be designated by 17 July 2026, then have ~10 months to comply (~May 2027). The CER Directive covers physical/operational resilience (cyber falls under NIS2). The local critical-infrastructure-coordination concept is the local expression of this national strategy. [verified — gov.ie Dept of Defence / OEP CER regulations]
- The operating-picture gap is genuine. DFB coordinates severe weather today through the SWAT, the Crisis Management Steering Group, and phone-/email-mediated contact with utilities and the NECG; there is no shared cross-agency map on which power, comms, water, gas, flood-gauge and a consented vulnerable register appear together. DCC's own Nov-2025 flood-response release describes SWAT meetings + NECG contact — i.e. meetings and calls, not a common operating picture. [verified — dublincity.ie Nov 2025]
Net: the pain is a review-mandated, statute-reinforced coordination + outreach gap — squarely decline-safe — but the incumbency is real (DFB just doubled down on Esri) and the procurement is slow/SBIR-gated.
§3 — Use-case & value (DECLINE-SAFE framing)
What we propose (the safe slice only): a Local Critical Entities Group common operating picture for the East Region. It fuses, onto one map and one timeline:
- Aggregate / polygon hazard layers: Met Éireann warnings; ESB Networks PowerCheck outage clusters (customers-affected polygons); Uisce Éireann supply status; Gas Networks status; telecoms-degradation notices; DCC river/tide gauges (Tolka, Dodder, Camac); road closures.
- Responder-asset layers: DFB stations & tasked jobs; Community Support Centres (CSCs); An Post delivery routes (as a reach mechanism, route metadata only).
- A consented vulnerable-person outreach layer — built only from the local authority's existing consented/registered vulnerable-customer list (or CSO small-area + GeoDirectory aggregates), surfacing who registered for help, never inferring who "might" be vulnerable.
The value: it surfaces the intersection — power-out ∩ comms-thin ∩ a concentration of registered vulnerable residents — that no single LCEG partner's tool shows today, then runs one human-gated, fully-audited action (open a CSC, dispatch welfare outreach, task An Post check-ins, issue a targeted local notice). This directly answers the Éowyn-review recs (reach vulnerable people; cross-agency situational awareness) and gives DCC a local CER evidence artefact.
Explicitly NOT (Declined List, stated up front in every showing):
- NOT predictive policing — no forecasting of crime or individuals' behaviour.
- NOT biometric identification / facial recognition — the map carries places, assets, and consented register entries, never biometric identity.
- NOT emotion recognition, NOT social scoring, NOT individual risk-scoring — the vulnerable layer is registered/consented membership, never an inferred "vulnerability score."
- NOT untargeted scraping — sources are official feeds + LA-held consented data + aggregate census geography.
- NOT psychometric profiling.
Decline-safe rule (verbatim leave-behind line): "Operational coordination + resilience only; aggregate/registered/consented data; human-gated; fully audited (PROV-O)."
§4 — Ontology (this buyer's domain entities & relationships)
(LocalAuthority: Dublin City Council)
├─ CONVENES ─▶ (LocalCriticalEntitiesGroup "East Region LCEG")
│ ├─ MEMBER ─▶ (Operator: ESB Networks) [electricity]
│ ├─ MEMBER ─▶ (Operator: Uisce Éireann) [water]
│ ├─ MEMBER ─▶ (Operator: Gas Networks Ireland)[gas]
│ ├─ MEMBER ─▶ (Operator: Telecoms MNO) [comms]
│ └─ MEMBER ─▶ (Operator: An Post) [outreach link]
├─ RUNS ─────▶ (SevereWeatherAssessmentTeam) ── ESCALATES_TO ─▶ (CrisisMgmtSteeringGroup)
│ └─ ESCALATES_TO ─▶ (NECG, national)
├─ OWNS ─────▶ (Asset: DFB Station) ── TASKED_ON ─▶ (Job: tree-fall / pump / welfare)
├─ OPERATES ─▶ (CommunitySupportCentre) ── STATUS ∈ {staging, open, gen-backed}
├─ MONITORS ─▶ (Gauge: Tolka@Drumcondra | Dodder | Camac) ── READS ─▶ (level, trend)
└─ HOLDS ────▶ (VulnerableRegisterEntry) ◀── CONSENT_BASIS ── (registration, lawful basis)
(Hazard: Met warning | ESB outage polygon | telecoms-degradation | flood-watch)
── INTERSECTS ─▶ (ElectoralDivision) ◀── CONTAINS ── (VulnerableRegisterEntry, count only)
(Decision: open CSC + outreach + targeted notice)
── GATED_BY ─▶ (HumanSignOff 2/2) ── PRODUCES ─▶ (WriteBack to DFB-CAD + Smart-Dublin LCEG dashboard)
── ATTRIBUTED_BY ─▶ (PROV-O bundle on HistoryRail)
The ontology is deliberately place-and-asset-centric. The only person-shaped node is VulnerableRegisterEntry, and it exists only as a consented membership with a count, never as an inferred individual score — that is the structural line that keeps the whole product off the Declined List.
§5 — Data model (synergy.* tables, RLS + a load-bearing CHECK)
SQL59 lines-- 5.1 Local Critical Entities Group operating picture: hazard/asset entities CREATE TABLE synergy.lceg_entity ( entity_id uuid PRIMARY KEY DEFAULT gen_random_uuid(), org_id text NOT NULL, -- tenant = the local authority kind text NOT NULL CHECK (kind IN ('met_warning','esb_outage','uisce_status','gas_status', 'telecoms_degrade','river_gauge','road_closure', 'dfb_station','community_support_centre','anpost_route')), label text NOT NULL, geom geography(Geometry,4326) NOT NULL, -- polygon or point attrs jsonb NOT NULL DEFAULT '{}'::jsonb, -- customers_off, level_m, etc. valid_from timestamptz NOT NULL DEFAULT now(), valid_to timestamptz, -- bitemporal (HistoryRail) source_feed text NOT NULL, -- 'esb_powercheck','met_eireann',... data_source text NOT NULL DEFAULT 'live' -- live|partial|pending convention CHECK (data_source IN ('live','partial','pending')) ); ALTER TABLE synergy.lceg_entity ENABLE ROW LEVEL SECURITY; CREATE POLICY lceg_entity_rls ON synergy.lceg_entity USING (org_id = current_setting('app.current_org_id', true)); -- 5.2 Consented vulnerable-register membership (COUNT-LEVEL ONLY; the decline-safe core) CREATE TABLE synergy.vuln_register_cell ( cell_id uuid PRIMARY KEY DEFAULT gen_random_uuid(), org_id text NOT NULL, electoral_div text NOT NULL, -- CSO ED / small-area code registered_n integer NOT NULL CHECK (registered_n >= 0), consent_basis text NOT NULL, -- e.g. 'LA welfare register, opt-in' -- LOAD-BEARING INVARIANT #1: this table can NEVER carry an individual identity or score. -- Aggregation floor enforces k-anonymity; an inferred per-person score is impossible by schema. CONSTRAINT vuln_aggregate_only CHECK (registered_n = 0 OR registered_n >= 5) ); ALTER TABLE synergy.vuln_register_cell ENABLE ROW LEVEL SECURITY; CREATE POLICY vuln_rls ON synergy.vuln_register_cell USING (org_id = current_setting('app.current_org_id', true)); -- 5.3 Human-gated LCEG decision (open CSC / outreach / targeted notice) CREATE TABLE synergy.lceg_decision ( decision_id uuid PRIMARY KEY DEFAULT gen_random_uuid(), org_id text NOT NULL, cluster_ed text NOT NULL, -- the triage ED (e.g. Ballymun) action_kind text NOT NULL CHECK (action_kind IN ('open_csc','welfare_outreach','anpost_tasking','targeted_notice','hold')), proportionality numeric(3,2) NOT NULL CHECK (proportionality BETWEEN 0 AND 1), signer_1 text, -- DFB Severe-Weather Coordinator signer_2 text, -- East Regional Working Group rep signed_at timestamptz, executed_at timestamptz, prov_bundle jsonb, -- PROV-O attribution graph -- LOAD-BEARING INVARIANT #2: no execution without a complete TWO-PERSON human gate. CONSTRAINT human_gate_required CHECK ( executed_at IS NULL OR (signer_1 IS NOT NULL AND signer_2 IS NOT NULL AND signer_1 <> signer_2 AND signed_at IS NOT NULL) ) ); ALTER TABLE synergy.lceg_decision ENABLE ROW LEVEL SECURITY; CREATE POLICY lceg_decision_rls ON synergy.lceg_decision USING (org_id = current_setting('app.current_org_id', true));
Why the two CHECKs are load-bearing. vuln_aggregate_only makes individual scoring structurally impossible — the schema cannot store a per-person record, only a registered_n ≥ 5 cell, so "who might be vulnerable" can never be computed (the decline-safe guarantee is in the table, not a policy doc). human_gate_required makes the database physically refuse to mark a decision executed unless two distinct named humans signed — the auditor can prove no autonomous tasking ever occurred.
§6 — Action-loop pseudocode (Python: detect → enrich → triage → gate → task → execute → BDA → close)
Python45 linesdef lceg_action_loop(org_id: str, replay_t: datetime) -> None: set_tenant(org_id) # RLS: app.current_org_id # 1 DETECT — pull aggregate hazard polygons at the replay timestamp outages = feed("esb_powercheck", at=replay_t) # customers-off polygons warnings = feed("met_eireann_warnings", at=replay_t) telecoms = feed("comreg_operator_notices", at=replay_t) # coarse comms-degrade gauges = feed("dcc_river_gauges", at=replay_t) # Tolka / Dodder / Camac # 2 ENRICH — overlay with consented vulnerable-register COUNTS by electoral division eds = electoral_divisions_touched(outages, telecoms, warnings) for ed in eds: ed.power_out = polygon_overlap(ed, outages) ed.comms_thin = polygon_overlap(ed, telecoms) ed.vuln_n = vuln_register_count(ed) # >=5 or 0, never per-person # 3 TRIAGE — the cross-LCEG intersection no single partner tool surfaces cluster = max( (ed for ed in eds if ed.power_out and ed.comms_thin and ed.vuln_n >= 5), key=lambda e: e.vuln_n, default=None) if cluster is None: return hold_and_repoll(minutes=15) # nothing actionable yet P = proportionality_score(cluster) # 0..1, considerations only # 4 GATE — MANDATORY two-person human sign-off (DB CHECK enforces it too) rec = recommend(action="open_csc + welfare_outreach + anpost_tasking", ed=cluster.electoral_div, P=P) verdict = decision_room(rec, personas=[ "DFB Severe-Weather Coordinator", "East Regional Working Group rep", "Data-protection / civil-society reviewer", "Met Éireann duty forecaster"]) if not verdict.signed_2of2: return log_refusal(rec, reason=verdict.dissent) # refuse + audit, no task # 5 TASK + 6 EXECUTE — write the gated action back to the real coordination systems d = persist_decision(cluster, action=rec.action, P=P, s1=verdict.signer_1, s2=verdict.signer_2) writeback("dfb_cad", open_csc=cluster.csc, welfare=cluster.vuln_n) writeback("smartdublin_lceg_dashboard", d) issue_targeted_notice(area=cluster.electoral_div, # CAP, Art-50 watermark basis="consented register + aggregate outage polygons") # 7 BDA — battle-damage / outcome assessment: did the outreach close? bda = assess(d, metrics=["vuln_contacted_pct", "csc_checkins", "notice_receipts"]) # 8 CLOSE — write the full PROV-O bundle to HistoryRail, close the UNO loop close_loop(d, bda=bda, prov=build_prov_o(d))
§7 — nexus-workflows YAML DAG (same loop, declarative, blocking human-gate node)
YAML38 lines# nexus-workflows: dcc-lceg-storm-replay (NO cron — workflows is the scheduler) name: dcc-lceg-storm-replay tenant: dcc-east-region trigger: type: feed_event # Met-warning escalation OR replay-scrubber step match: { severity: ["orange","red"], region: "east" } nodes: - id: detect run: feeds.pull with: { sources: [esb_powercheck, met_eireann, comreg_notices, dcc_gauges] } - id: enrich needs: [detect] run: lceg.overlay_vuln_counts # aggregate-only; >=5 floor - id: triage needs: [enrich] run: lceg.intersection_cluster # power_out ∩ comms_thin ∩ vuln_n emits: { cluster_ed, proportionality } - id: human_gate needs: [triage] type: BLOCKING_HUMAN_GATE # DAG halts here until 2/2 sign-off approvers: quorum: 2 roles: [dfb_severe_weather_coordinator, east_regional_working_group] reviewers: [data_protection_civil_society] # seated inside the room on_timeout: { after: 30m, action: hold_and_repoll } on_refuse: { action: log_refusal, halt: true } - id: task_execute needs: [human_gate] when: "${human_gate.signed_2of2 == true}" run: lceg.writeback with: { targets: [dfb_cad, smartdublin_lceg_dashboard, targeted_notice] } - id: bda needs: [task_execute] run: lceg.assess with: { metrics: [vuln_contacted_pct, csc_checkins, notice_receipts] } - id: close needs: [bda] run: history.write_prov_o # PROV-O bundle -> HistoryRail; close UNO loop
The human_gate node is blocking: the DAG cannot reach task_execute until two distinct approvers sign, and the civil-society reviewer is a seated reviewer inside the gate, not consulted afterwards.
§8 — UI/UX mockups (VERBATIM generated ASCII)
Generated by
_build/archetypes/gen_dcc-lgma-urban-ops.py(importingarchetypes.py). Pasted exactly as printed; alignment guarded by_ck(). SVG twin of the primary screen:_build/figures/dcc-lgma-urban-ops/uc-map_ops.svg.
Figure a05.1 — map_ops (PRIMARY). Components: ShellLayout › TopBar (with PccPill "East Region" + RendererChip MapLibre-2D) › ClassificationBanner (OFFICIAL, decline-safe line) › LeftSidebar (LAYERS + HistoryRail replay scrubber + SOURCES) › MapConsole (the triple renderer in 2D) with the Inspector triage panel › BottomStatusBar INCIDENTS ticker.
Figure — Operational picture (map_ops · live MapLibre). Production-fidelity React surface (buildable); the faithful ASCII follows.
+------------------------------------------------------------------------------------------------------+
| Dublin City Local Critical Entities Group COP - Storm-Eowyn lens (MapConsole + MapLibre-2D) |
+--------------------+---------------------------------------------------------------------------------+
| LAYERS | MAP ========================================================================== |
| [x] Met warnings | Dublin City + East Region (DCC Crisis Mgmt Steering Group AOR) |
| [x] ESB outage | | ## MET ORANGE wind 05:00-11:00 ## gusts 130 km/h logged Phoenix Pk |
| [x] Uisce Eireann | | |
| [x] Gas Networks | o CABRA / NAVAN RD ESB out 6,300 cust | 4G DEGRADED | water OK |
| [x] Telecoms down | | DFB-Phibsborough tasked: 4 tree-fall jobs on NCR / Cabra Rd |
| [x] River gauges | o BALLYMUN ESB out 9,100 | mast loaded -> COMMS THIN <!> |
| [x] DFB stations | | >> power-out AND comms-thin AND 52 registered vuln. residents |
| [x] CSC status | ~ TOLKA @ Drumcondra gauge 2.41m RISING | flood-watch (not warning) |
| [~] Vuln. register | o EAST WALL / N.STRAND ESB out 3,800 | Camac/Tolka tidal-lock watch |
| [ ] An Post routes | o RINGSEND / IRISHTOWN pumping-stn on backup gen | Dodder gauge OK |
| | | |
| REPLAY | o FINGLAS ESB out 7,200 | CSC-F (Finglas LC) STAGING |
| Storm Eowyn lens | |
| DCC/LGMA East Reg | TRIAGE CLUSTER: Ballymun = power-out n comms-thin n vuln-register(52) |
| [<<] t+05:40 [>>] | the cross-LCEG intersection no single partner tool surfaces today |
| | Proportionality P=0.89 | HUMAN SIGN-OFF required before any tasking |
| SOURCES | [ Open Decision Room ] [ Hold + re-poll 15m ] [ Drop CSC pin ] |
| Met Eireann WX | |
| ESB PowerCheck | |
| consented register | |
+--------------------+---------------------------------------------------------------------------------+
| INCIDENTS: 05:38 Ballymun mast loaded | DFB 11 jobs queued | Tolka rising | CSC-Finglas staging |
+------------------------------------------------------------------------------------------------------+
Figure a05.2 — command_dashboard (SECONDARY). Components: ShellLayout › TopBar › KPI tiles row (CUSTOMERS OFF SUPPLY / LCEG PARTNERS LIVE / CSC + VULN OUTREACH) › LIVE ALERT FEED (the East Regional Working Group / SWAT coordination log, write-back receipts surfaced from HistoryRail).
Figure — Command dashboard (KPI + live feed). Production-fidelity React surface (buildable); the faithful ASCII follows.
+--------------------------------------------------------------------------------------------------+
| East Regional Working Group - Severe Weather Assessment Team (command_dashboard) |
+--------------------------------------------------------------------------------------------------+
| CUSTOMERS OFF SUPPLY | LCEG PARTNERS LIVE | CSC + VULN OUTREACH |
| 31,400 across East Reg | 5/6 reporting | 3 open / 4 staging |
| ESB feeders: 7 affected | An Post route-data pending | 52 register flagged Ballymun |
+--------------------------------------------------------------------------------------------------+
| LIVE ALERT FEED |
| 05:38 Ballymun mast loaded -> comms-thin; 52 vuln-register residents flagged for outreach |
| 05:40 Decision Room: CSC-Ballymun open + welfare outreach + An Post tasking - SIGNED 2/2 |
| 05:44 Write-back OK: DFB CAD + Smart Dublin LCEG dashboard receipts on HistoryRail |
| 05:51 ESB ETR Cabra feeder 09:15; Uisce Eireann confirms Ringsend pump on backup gen |
| 06:03 Tolka @ Drumcondra 2.46m - below action level; flood-watch held, no CAP issued |
| 06:18 Rec: reach vulnerable people (consented register) -> 52 contacted or visited |
| 06:30 BDA: outreach 52/52 closed; CSC-Ballymun 38 check-ins; UNO action loop closed |
+--------------------------------------------------------------------------------------------------+
§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 + screen-flow arrow chain)
Click-path (the actual interaction line through these surfaces' buttons):
On MapConsole, the operator drags the HistoryRail scrubber to t+05:40; the Met-orange, ESB-outage, telecoms-down and [~] Vuln. register layers paint; the auto-surfaced TRIAGE CLUSTER (Ballymun) badge appears with P = 0.89; the operator clicks [ Open Decision Room ] → the right-docked ChatTerminal opens the gated deliberation → after dissent is heard, the operator clicks [ /dual-control sign ] twice (two distinct approvers) → [ /execute ] → write-back receipts post to the command_dashboard LIVE ALERT FEED and the PROV-O bundle lands on HistoryRail; the operator can scrub back to replay exactly who knew what, when, and who authorised what.
Screen-flow arrow chain:
MapConsole(map_ops) ──[HistoryRail t+05:40]──▶ TRIAGE CLUSTER badge (Ballymun, P=0.89)
│ click [Open Decision Room]
▼
ChatTerminal(decision_room) ──[/dual-control sign × 2 + civil-society review]──▶ [/execute]
│ write-back
▼
command_dashboard(LIVE ALERT FEED) ──▶ HistoryRail (PROV-O audit) ──▶ [scrub-back replay]
§10 — Decision-Room transcript (the gated decision; dissent + a civil-society reviewer + the gate verdict)
Surface:
ChatTerminalright-dock as the Decision Room. The personas are bubble roles inside the chat, not a separate "ActionDock."
DECISION ROOM — East Region LCEG · Ballymun cluster · replay t+05:40
─────────────────────────────────────────────────────────────────────────────
[DFB Severe-Weather Coordinator] Triage surfaced Ballymun ED: ESB out 9,100,
mast loaded so comms are thin, and the consented register shows 52 people in
that ED. Recommendation: open CSC-Ballymun, welfare outreach, task An Post
check-ins on tomorrow's routes. Proportionality 0.89.
[Met Éireann duty forecaster] Concur on timing — orange wind holds to 11:00,
gusts 130 km/h at Phoenix Park. No flood warning; Tolka is a watch only, so
don't bundle a flood action in. Keep it to power+comms+outreach.
[Data-protection / civil-society reviewer] DISSENT on the mechanism, not the aim.
Confirm the 52 is a *consented-register count for the ED*, not an inferred
list — I want it on record that we are NOT scoring individuals and NOT
matching any biometric or behavioural data. And the targeted notice must be
area-level (Eircode routing key), not addressed to named register members.
[DFB Severe-Weather Coordinator] Confirmed: 52 = registered_n for the ED, schema
floor ≥5, no per-person record exists. Notice is area-level, Art-50 watermark
on. An Post tasking is "call to anyone on your round who looks cut off,"
not a name list.
[East Regional Working Group rep] Then I'm content. One condition: log that the
register data stays inside the DCC tenant — it does not fan out to the MNO or
to ESB. Write-back to DFB-CAD and the Smart Dublin LCEG dashboard only.
[Data-protection / civil-society reviewer] With those conditions, I withdraw the
dissent. Approve.
─────────────────────────────────────────────────────────────────────────────
GATE VERDICT: open_csc + welfare_outreach + anpost_tasking + targeted_notice
sign 1/2 DFB Severe-Weather Coordinator ✓ QES
sign 2/2 East Regional Working Group rep ✓ QES
reviewer Data-protection / civil-society ✓ approve (conditions logged)
proportionality 0.89 · register stays in-tenant · area-level notice
→ [ /execute ] (DB CHECK human_gate_required satisfied: 2 distinct signers)
§11 — Write-back + BDA + PROV-O chain + deltas-only regulatory traceback
Write-back (the action leaves the COP):
dfb_cad←open_csc(CSC-Ballymun)+welfare_outreach(n=52)(DFB Computer-Aided Dispatch).smartdublin_lceg_dashboard← the decision record (so all LCEG partners see one truth).targeted_notice← area-level CAP message (Eircode routing key), Art-50 AI-disclosure watermark ON.- In-tenant guarantee: the vulnerable-register count never fans out to the MNO/ESB; only the decision does.
BDA (loop close): vuln_contacted_pct = 52/52 (100%), csc_checkins = 38, notice_receipts confirmed at T+6m (MNO delivery receipt). The UNO loop is marked closed on HistoryRail.
PROV-O attribution chain:
prov:Entity triage-cluster-ballymun-t0540
prov:wasDerivedFrom esb-powercheck-snapshot-t0540
prov:wasDerivedFrom comreg-telecoms-notice-t0540
prov:wasDerivedFrom vuln-register-cell-ED-ballymun (count=52, basis=consented)
prov:qualifiedDerivation [ prov:hadRole intersection-power∩comms∩vuln ]
prov:Entity lceg-decision-open-csc-ballymun
prov:wasGeneratedBy decision-room-session-t0540
prov:wasAttributedTo dfb-severe-weather-coordinator
prov:qualifiedAssociation [ prov:hadPlan dual-control-2of2 ;
prov:value "P=0.89 ; register in-tenant ; area-level notice" ]
prov:wasInformedBy civil-society-reviewer-approval-t0540
prov:Entity writeback-dfb-cad + smartdublin-lceg-dashboard
prov:wasGeneratedBy lceg-decision-open-csc-ballymun
ObservationLevel(triage-cluster) = ASSERTED (model-derived, human-reviewable; never OBSERVED)
Deltas-only regulatory traceback (only what differs from the §4.0 defaults):
- EU AI Act Art-50 (transparency): the auto-generated public notice carries an AI-disclosure watermark — delta: ON for outbound CAP. (Art-5 prohibitions are applicable from 2 February 2025; this use case sits outside them by construction.)
- GDPR Art-6/Art-9: lawful basis is the consented LA welfare register + public-task; delta: the §5.2
vuln_aggregate_onlyCHECK enforces the count-only, k≥5 minimisation that the Éowyn review's data-sharing concern demands. - CER (S.I. 559/2024) / National Strategy 2026–2029 (published 19 March 2026; physical/operational resilience, cyber under NIS2): the
HistoryRailPROV-O bundle is the local CER evidence artefact; delta: export profile = "Local Critical Entities Group after-action record."
§12 — Buyer & stakeholders
| Role | Who | Status |
|---|---|---|
| Economic / lead buyer | Dublin City Council (lead LA, Smart Dublin + East Region MEM) | verified institution; [Named contact TBD] |
| Operational champion | DFB Emergency Management — Senior Fire & Emergency Management Officer (chairs Crisis Mgmt Steering Group + SWAT) | verified role; [Named contact TBD] |
| Procurement front door | Smart Dublin programme team (info@smartdublin.ie) via EI SBIR | verified channel |
| Sector-scale owner | LGMA (31-LA shared services) | the expansion path; [Named contact TBD] |
| LCEG partners (users, not buyers) | ESB Networks, Uisce Éireann, Gas Networks Ireland, telecoms MNO, An Post | our proposed COP partner set; the Éowyn review itself names ESBN / Uisce Éireann / IFA / forestry contractors |
| Warm-intro sponsor | Patrick Walsh (CEO, Dogpatch Labs) — docklands cluster overlaps Smart Docklands/Smart Dublin | warm-but-unproven; patrick@dogpatchlabs.com [verified — contact register] |
§13 — Competition / incumbency + comparator (cited)
- Esri / ArcGIS (the live, expanding incumbent). DFB signed a new Esri Ireland ArcGIS deal in January 2026 to map vulnerable buildings, optimise station/appliance siting, and fuse operational + census/health data; DFB runs an Organisational Intelligence Unit on ArcGIS (Survey123, ArcGIS Online). [verified — Irish Times 12 Jan 2026; Esri Ireland customer story] Position: integrate above it, never displace it — Esri is the LA's authoritative GIS layer; we are the cross-agency LCEG decision + audit layer that no GIS owns.
- D4H — emergency incident-management software used by Irish responders; adjacent, single-agency, not the cross-LCEG fusion layer. [likely]
- MapAlerter — entrenched LA public-alerting tool across 20+ Irish LAs; its own blog concedes it does not provide a responder common operating picture or cross-agency fusion. [verified — mapalerter.ie] Position: a target of our fan-out, not a competitor for the decision layer.
Comparator (fold-in): Palantir Foundry / Esri ArcGIS Mission could each assemble a picture, but the decline-safe, count-only consented-register model + the structural two-person DB gate + the published Declined List are the differentiators; the white-space is the cross-agency IICG/LCEG coordination + audit layer, not the LA's own GIS.
§14 — Readiness (honest, pre-pilot)
Reuse (already exists, on /synergy-console): MapConsole triple renderer; the COP entity model + /api/v1/cop/picture (117 live entities on the demo tenant, e.g. DOLPHIN-21); HistoryRail bitemporal playback + audit (SC-MAP-HIST); map objects / dropped pins + elevation (SC-MAP-OBJ / SC-MAP-PIN — for CSC/generator/geofence pins); ChatTerminal Decision Room; the EM/COP routes already merged.
Real gaps (do not overstate):
- No live Irish storm adapters yet — Met Éireann / ESB PowerCheck / ComReg / DCC-gauge ingest is build work (the storm-replay demo is a build-spec, not yet built).
- Consented vulnerable-register data is not in hand — depends on the LA agreeing a data-sharing basis (the exact thing the Éowyn review flags as hard); demo runs on aggregate CSO/GeoDirectory until then.
- Incumbency-fit work — we must demonstrate the LCEG layer consumes Esri/DFB feeds, not competes; that integration is unbuilt.
- Contracting blocked — founder solo on Stamp 1G; SBIR/any contract needs an incorporated Irish company.
Honest demo maturity: discovery-ready storm-replay COP (recorded data, real past event) → not a deployed operational system; no live tasking against any real agency.
§15 — ENGAGEMENT PLAYBOOK (first-contact → free discovery → demo → pilot → LOI → signed contract)
Stage 1 — First contact
- Trigger: Patrick-warm-intro into Smart Dublin / Smart Docklands, OR a direct note to
info@smartdublin.iereferencing the Éowyn review + the CER Local-Critical-Entities-Group mandate. - Owner: Founder.
- Activity: Send the warm-intro email (template below). Ask for a 20-minute discovery slot. No paid ask.
- Template (warm-intro email, adapted for THIS buyer):
Subject: A no-cost Local-Critical-Entities-Group operating-picture session for the East Region [Name] — [Patrick-intro context]. The Storm-Éowyn review asked every council to stand up a Local Critical Entities Group and to find a way to reach vulnerable people during severe weather. We build an EU-sovereign common operating picture that fuses ESB / Uisce Éireann / Gas / telecoms / flood-gauge feeds and a council's own consented vulnerable register onto one map and one audited timeline — sitting above your existing ArcGIS, not replacing it. We run a free discovery (we listen, no cost, no obligation). We publicly refuse predictive policing, biometric ID and individual risk-scoring — this is coordination + consented outreach, human-gated and fully audited. Could I show you 20 minutes? — [Founder]
- Exit criterion: A discovery slot booked. Deliverable: calendar invite + lightweight agenda.
Stage 2 — Free discovery (60-min agenda, adapted)
- Trigger: slot booked. Owner: Founder. Activity: run the 60-min discovery (listen, no slides).
- 0:00–0:05 Frame + permission ("discovery, not a sales pitch").
- 0:05–0:20 Current operating picture: "Walk me through the last severe-weather activation from SWAT stand-up to stand-down — how many systems do you look at to get one picture? When you need to reach vulnerable people, how does that happen today?"
- 0:20–0:35 Governance/lawful basis: "What's the lawful basis and consent state of your vulnerable register? Who are the LCEG partners and what do they currently share? Are you in scope for CER designation by 17 July 2026?"
- 0:35–0:45 Stakeholders/budget/timing: "Who owns the LCEG operationally? Is this an SBIR challenge, a Smart Dublin pilot, or a DCC capital line? Where does Esri sit?"
- 0:45–0:55 Map their loop onto detect→enrich→triage→gate→task→execute→assess→close; find where they jump detect→act with no shared picture.
- 0:55–1:00 Reflect top-3 pains; ask for a scoped-demo date. Do not ask for money/LOI.
- Exit criterion: named sponsor agrees the cross-agency picture is a problem worth solving + asks "could we see this on our kind of data?" Deliverable: same-day discovery write-up (sponsor, budget owner, top-3 pains, lawful basis, Declined-List PASS, funding vehicle hinted).
Stage 3 — Scoped demo
- Trigger: discovery exit met. Owner: Founder. Activity: show the storm-replay #4 (DCC/LGMA lens) on
/synergy-consoleagainst East-Region geography: replay Éowyn, surface the power∩comms∩consented-vuln cluster, run ONE human-gated Decision-Room action, show the PROV-O audit + Esri-consume framing. Lead with the decline-safe line and "above your ArcGIS." - Exit criterion: sponsor asks "could we try this on a narrow real slice?" Deliverable: the one-page pilot proposal (below).
Stage 4 — Pilot (1-page proposal, filled for THIS buyer)
- Title & sponsor: "East Region LCEG Operating-Picture Pilot" — sponsor: DFB Senior Fire & Emergency Management Officer; budget owner: Smart Dublin / DCC.
- Problem (their words): "We have no shared cross-agency picture during severe weather and no reliable way to reach the people who registered for help."
- The one thing we'll prove: "We can fuse the LCEG partner feeds + a consented vulnerable register into one human-gated, audited picture and reduce time-to-reach-the-right-cluster from [baseline TBD wk1] to [target TBD]."
- Scope in/out: IN — East Region, recorded-storm replay + one live severe-weather window, LCEG layers, consented register (or CSO aggregate). OUT — any individual scoring, biometrics, predictive policing (Declined-List explicitly excluded), TMS/GIS replacement.
- Data & lawful basis: consented LA register + aggregate CSO/GeoDirectory; EU-hosted; DPA per partner; classification OFFICIAL.
- Success criteria: 2–4 sponsor-agreed metrics (cluster-detection time; % consented-vuln reached; audit completeness; partner-satisfaction). Baselines measured wk1.
- Timeline: 8–12 weeks, mid-point checkpoint; target one winter-2026/27 severe-weather window.
- Commercials: €0 to DCC if SBIR-funded; else TBD. Internal indicative production band only if asked —
[PRIOR], our own indicative pricing, not committed and not a published rate (Tier-1 €120–240k → Tier-3 €2.4–4.8m/yr). - Roles: founder + (contracting vehicle) on our side; DFB EM + Smart Dublin on theirs.
- After: an LOI if criteria met.
- Funding vehicle: EI SBIR via Smart Dublin (company-direct, two-phase) — the cleanest route.
- Exit criterion: pilot success criteria met or credibly trending. Deliverable: pilot result memo.
Stage 5 — LOI (checklist, the milestone / Patrick-check trigger)
- Trigger: pilot criteria met. Owner: Founder + solicitor. Activity: capture documented intent.
- LOI checklist: parties (DCC + Nexus Synergy Ltd — or founder in own name, NewCo to ratify under CA 2014 s.45); statement of intent; scope (from pilot); success-criteria referenced; named sponsor; indicative timeline + next step; indicative commercials ("to be scoped under SBIR/OGP"); conditions (funding, procurement, DPA); binding/non-binding stated (default non-binding except confidentiality); confidentiality (mutual NDA); Irish governing law; Declined-List affirmation; signatures + dates; solicitor review confirmed before sending.
- Exit criterion: signed LOI naming a sponsor + next step. Deliverable: executed LOI.
Stage 6 — Signed contract
- Trigger: LOI + funded route. Owner: contracting vehicle + DCC procurement. Activity: SBIR Phase-2 / OGP contract. Critical dependency: an incorporated Irish entity (Stamp-4 founder or a partner/Dogpatch-brokered vehicle). Exit criterion: signed contract. Deliverable: contract + project kickoff.
§16 — PM / timeline (Gantt + milestones + critical path + RACI)
2026 2027
Jul Aug Sep Oct Nov Dec | Jan Feb Mar Apr May Jun
First contact ## |
Free discovery ### |
Scoped demo ### |
Pilot (SBIR P1) ###### |
└ winter severe-wx window ####### #|#### (the real test season)
LOI ## | ##
Incorporation / vehicle ····· GATE ···|···· (critical, blocks PAID work)
Signed contract (SBIR P2) | ######
Milestones: M1 discovery booked (Q3-26); M2 scoped demo accepted; M3 SBIR Phase-1 award; M4 winter severe-weather window exercised; M5 signed LOI; M6 contracting vehicle in place (the gate); M7 SBIR Phase-2 contract.
Critical path: the Stamp-1G → partner/incorporation gate is critical for any PAID pilot. A free discovery + scoped demo + a non-binding LOI can proceed in the founder's own name; an SBIR Phase-2 (paid) contract cannot be signed until an incorporated Irish vehicle exists (Stamp-4 founder, or a Dogpatch-brokered/partner entity). This gate, not the buyer's interest, is the binding constraint on revenue.
RACI:
| Activity | Founder | Warm-intro sponsor (Patrick) | Partner/contracting vehicle | Buyer champion (DFB EM) | Buyer procurement (Smart Dublin/OGP) |
|---|---|---|---|---|---|
| First contact / warm intro | R | A | I | C | I |
| Free discovery | R | C | I | A | I |
| Scoped demo | R | I | I | A | C |
| Pilot delivery | R | I | C | A | C |
| LOI | R | C | C | A | C |
| Incorporation / vehicle (gate) | R | C | A | I | I |
| Signed contract | C | I | A | C | R |
§17 — Funding / procurement vehicle
- Primary: EI SBIR via Smart Dublin — pre-commercial procurement, company-direct (no academic partner), two phases (feasibility → prototype), contract paid to the SME; historically funded per-challenge envelopes (Smart Dublin/EI SBIR rounds ~€700k–€800k across multiple challenges). [verified — Smart Dublin / EI SBIR] Requires an incorporated Irish company → Stamp-1G-gated.
- Backstop: DCC / Smart Dublin own innovation/capital budget for a direct sub-OJEU pilot.
- Non-dilutive top-ups (post-incorporation only): 35% R&D Tax Credit (refundable even if loss-making); EI Agile Innovation Fund (≤€150k, fast-track, EI-client-gated). Not solo-accessible pre-incorporation.
- Honesty flags: NATO DIANA excludes Ireland; EUDIS/EDF are consortium-only (not a solo LA pilot route); Research-Ireland Defence Challenge is academic-routed — none apply here.
§18 — Two-stage formula scorecard
All factor cells are
[PRIOR]with a dated one-line rationale (2026-06-05).
Stage-1 vector {mandate_pull, access_warmth, demonstrability, decline_safety, white_space, cycle_speed, pillar_fit}:
| Factor | Score | Dated rationale [PRIOR] |
|---|---|---|
| mandate_pull | 4 | 2026-06-05: Éowyn review (21-Oct-2025) mandates LCEG + vulnerable-outreach; CER strategy 19-Mar-2026, designation 17-Jul-2026 — strong, but the local CER line isn't a named funded budget. |
| access_warmth | 3 | 2026-06-05: Patrick/docklands overlaps Smart Dublin (plausible warm) but no named DCC/DFB contact in hand. |
| demonstrability | 4 | 2026-06-05: storm-replay #4 (DCC/LGMA lens) reuses the COP/HistoryRail; demo-ready on East-Region geography (data adapters still to build). |
| decline_safety | 5 | 2026-06-05: coordination + consented outreach only; count-only ≥5 register CHECK; no scoring/biometrics possible. |
| white_space | 3 | 2026-06-05: the cross-agency LCEG decision layer is unoccupied — but DFB's new Esri deal raises "isn't this GIS?" inertia. |
| cycle_speed | 3 | 2026-06-05: SBIR is a genuine company-direct sub-OJEU route (faster than central gov), but still a structured multi-round cycle. |
| pillar_fit | 5 | 2026-06-05: dead-centre of the action-loop COP core. |
S1 = (4·.22)+(3·.22)+(4·.18)+(5·.14)+(3·.10)+(3·.08)+(5·.06) = 0.88+0.66+0.72+0.70+0.30+0.24+0.30 = 3.80. P_LOI = 0.55 / (1 + exp(−1.15·(3.80 − 2.6))) = 0.55 / (1 + exp(−1.38)) = 0.55 / 1.2516 ≈ 0.44 → band ~33–44% [PRIOR].
Stage-2 vector {contractability, funding_to_pay, procurement_clarity, incumbency_displacement, time_to_value, reference_leverage}:
| Factor | Score | Dated rationale [PRIOR] |
|---|---|---|
| contractability | 1 | 2026-06-05: founder solo on Stamp 1G — no signable vehicle today. |
| funding_to_pay | 3 | 2026-06-05: SBIR is real & company-direct, but no named uncommitted 2026/27 LCEG envelope confirmed. |
| procurement_clarity | 3 | 2026-06-05: SBIR/Smart-Dublin gives a clearer sub-OJEU route than most LAs. |
| incumbency_displacement | 3 | 2026-06-05: we sit above Esri (integrate), but the fresh Jan-2026 deal sharpens the "already covered" reflex. |
| time_to_value | 3 | 2026-06-05: a winter-window pilot can show value inside the CER ~May-2027 compliance horizon. |
| reference_leverage | 2 | 2026-06-05: no delivered decline-safe reference yet; this would be an early logo. |
S2 = (1·.24)+(3·.22)+(3·.18)+(3·.16)+(3·.12)+(2·.08) = 0.24+0.66+0.54+0.48+0.36+0.16 = 2.44. P_raw = 0.70 / (1 + exp(−1.1·(2.44 − 2.8))) = 0.70 / (1 + exp(0.396)) = 0.70 / 2.486 ≈ 0.28 [PRIOR].
Legal gate G = V·T. V_today = 0.10 (solo Stamp 1G); t_resolve = 14mo, H_conv = 30 → T = (30−14)/30 = 0.533. G_today = 0.10·0.533 = 0.053.
- P(Contract|LOI) today = G·P_raw = 0.053·0.28 ≈ 1.5%.
- At V=0.45 (Dogpatch-brokered vehicle): G=0.24 → P(Contract|LOI) ≈ 6.7%.
- At V=0.75 (confirmed partner prime): G=0.40 → ≈ 11.2%.
- At V=1.0 (Stamp-4 + incorporated): G=0.533 → ≈ 14.9%.
P(Contract) = P_LOI · G · P_raw ≈ 0.44 · 0.053 · 0.28 ≈ 0.65% today; ≈ 2.9% (V=0.45); ≈ 4.9% (V=0.75); ≈ 6.6% (V=1.0). [PRIOR]
Score100 = S1·20 = 3.80·20 = 76. Reconciliation: the board_anchor for this row is score100 = 64 (to-LOI 22–35%, to-buy 13–21%, value med). The raw formula (76) runs ~12 pts hot versus the board, driven by mandate_pull/white_space being credited above the board's read — the board down-weighted both for the fresh Esri incumbency (the "already covered" reflex) and the absence of a named DCC contact. Honouring the board's adversarial correction, I trim mandate_pull 4→3 (the local CER line is not a named funded budget) and white_space 3→2 (Jan-2026 Esri deal): revised S1 = 3.80 − 0.22 − 0.10 = 3.48 → Score100 = 69.6, still ~5pts above 64. The residual gap is the board's harder discount on access_warmth realism; I defer to the board_anchor band and report Score100 = 64 for portfolio consistency, with the formula's 70-ish as the optimistic edge. to-LOI band 22–35% [PRIOR] (my P_LOI 0.44 sits at the top of that band — consistent with "if we get a named contact this converts well; the band's width is the access-warmth uncertainty").
§19 — Commercial
All tier bands below are
[PRIOR]internal indicative pricing — our own pre-pilot estimates for prioritisation, not committed, not published, and not a market rate. Source:user_fed. Quote nothing externally without sign-off.
| Tier | Annual band | Fit for DCC | Notes |
|---|---|---|---|
| Tier-1 | €120–240k/yr | a single-region East LCEG COP (the realistic first production scope) | likely entry tier |
| Tier-2 | €600k–1.2m/yr | DCC-wide + multi-hazard + CER evidence pack | expansion |
| Tier-3 | €2.4–4.8m/yr | LGMA sector roll-out across the 31 local authorities | the expansion thesis |
- ACV (first production): Tier-1 mid ~€180k/yr [PRIOR].
- Pilot: often €0 to DCC if SBIR-funded (else TBD).
- Terms: annual SaaS on EU-sovereign infra; DPA per LCEG partner; Declined-List affirmation in-contract.
- Requirements: incorporated Irish vehicle (Stamp-4/partner); DPA + data-sharing agreement for the consented register; Esri-consume integration; OGP/SBIR procurement compliance.
- Cost advantage: open-source substrate + sovereign HPC + shared conformity file + no forward-deployed-engineer dependency.
§20 — Legal blockers
- X1 Stamp 1G (the binding one). Stamp 1G explicitly bars directorship, self-employment and operating a business, so the founder cannot be a company director or sign a paid contract until Stamp 4 (passive/non-active shareholding is not explicitly prohibited, but founding-and-running a NewCo is — ⚖️ CONFIRM the exact shareholding line with an immigration solicitor). Mitigation: free-discovery + scoped-demo + non-binding LOI in the founder's own name (CA 2014 s.45 ratification); a Dogpatch-brokered/partner contracting vehicle or EEA-resident director (Patrick/Manuel) for the SBIR contract. ⚖️ CONFIRM (immigration solicitor). [verified regime; per-case confirm]
- Buyer-specific: consented vulnerable-register data governance. The Éowyn review itself flags organisational reluctance to share vulnerable-person data. Mitigation: consented/registered data only, count-level, k≥5 (the §5.2 CHECK); DPA + data-sharing agreement; register stays in-tenant. ⚖️ CONFIRM (DPO + solicitor). [verified pain — NDFEM review]
- EU AI Act. Art-5 prohibitions are applicable from 2 February 2025 — this use case sits outside them by construction (no biometric/predictive/scoring). Art-50 transparency watermark on outbound notices. FRIA if any layer is later read as high-risk. [verified regime]
- GDPR / residency. EU-hosted; consented + public-task basis; aggregate fallback. [verified]
- Procurement. SBIR/OGP/eTenders; below-threshold pilot route via Smart Dublin reduces friction; full contract is OGP-governed. [verified]
- Pre-incorporation contracting (X7). Founder personally liable until NewCo; sign NDAs/MOUs in own name. ⚖️ CONFIRM.
§21 — Warm-intro contact + the specific ask
- Contact: Patrick Walsh (CEO, Dogpatch Labs) —
patrick@dogpatchlabs.com[verified — contact register]. Dogpatch sits in the Dublin Docklands cluster alongside Smart Docklands / Smart Dublin; the SBIR pre-commercial procurement is run by Enterprise Ireland with Smart Dublin (not Dogpatch), so the value here is a warm intro into the Smart Dublin programme team + DCC innovation/CIO function, plausible via the shared docklands cluster. - The specific ask: "Patrick — can you warm-introduce me to the Smart Dublin programme team (or DCC's innovation/CIO function) for a free 20-minute discovery on a Local-Critical-Entities-Group operating picture? It answers the Storm-Éowyn review directly — stand up the LCEG, reach vulnerable people — and sits above DFB's new ArcGIS, not against it. Object/place + consented-register data only, explicitly no biometrics or scoring."
- Fallback (cold-warm): direct note to
info@smartdublin.ieframed on the Éowyn review + CER LCEG mandate + a free Éowyn-replay demo.
§22 — Open questions + consolidated Sources
Open questions (do not assert until resolved):
- [Named DCC/DFB contact — TBD] — the single biggest unknown; the to-LOI band's width is mostly this.
- [Consented vulnerable-register lawful basis & format — TBD] — does DCC hold an opt-in register today, and on what basis can it be surfaced count-level?
- [SBIR challenge timing — TBD] — is there a live/upcoming Smart Dublin SBIR round this fits, or is it a direct DCC pilot?
- [CER local designation status — TBD] — is DCC/the East Region formally inside the 17-Jul-2026 designation process, and who owns the LCEG locally?
- [Esri-consume integration scope — TBD] — exactly which DFB ArcGIS feeds we'd consume.
Sources (dated 2026-06-05):
- NDFEM Review of Storm Éowyn, published 21 Oct 2025 — local critical-infrastructure coordination groups (ESB Networks / Uisce Éireann / IFA / forestry contractors + councils); vulnerable-person data-sharing reluctance; Community Support Centre Activation Guide; 72-hours-without-services advice. gov.ie / Irish Times (2025-10-21). [verified]
- Storm Éowyn impact — ESB "unprecedented," ~768,000 peak off supply (~30%). esb.ie / NDFEM review. [verified]
- Dublin Fire Brigade — new Esri Ireland ArcGIS deal, Jan 2026 (vulnerable-buildings mapping, station siting, census/health fusion). Irish Times (2026-01-12); Esri Ireland customer story; Smart Dublin; techbuzzireland (2026-01-08). [verified]
- DCC severe-weather response (SWAT meetings + NECG contact, Nov 2025). dublincity.ie. [verified]
- DCC / DFB Major Emergency Management; Crisis Management Steering Group; East Regional Working Group. dublincity.ie. [verified]
- CER: S.I. 559/2024 + National Strategy on the Resilience of Critical Entities (published 19 March 2026, 2026–2029; DoD single point of contact; designation by 17 July 2026; covers physical/operational resilience, cyber under NIS2). gov.ie Dept of Defence / OEP CER regulations. [verified]
- Smart Dublin + Enterprise Ireland SBIR — company-direct, two-phase pre-commercial procurement to SMEs. smartdublin.ie; enterprise-ireland.com. [verified]
- MapAlerter concedes it is public-alerting, not a responder COP / cross-agency fusion. mapalerter.ie. [verified]
- EU AI Act Art-5 prohibitions applicable 2 February 2025. [verified regime]
- Source card:
03-gtm/target-packages/_master-loi-detail-01-12.mdrow #8 (local-gov-smartcity, score 64). [internal] - Storm-replay COP demo spec:
03-gtm/demos/storm-replay-cop-demo.md(lens #4 DCC/LGMA). [internal]