Nexus Synergy Engagement Package — C01 · daa plc (Dublin Airport) / Irish Aviation Authority (IAA)

STATUS HONESTY. Nexus Synergy Ltd is pre-incorporation, pre-revenue, pre-pilot. daa and the IAA are a TARGET, not a customer; nothing here is deployed. The ~178 product UI surfaces exist as a gallery, not a live system; the counter-UAS action loop over a live Dedrone/ADS-B feed is not yet built or proven. ANTI-COOKIE-CUTTER. The three mockups in §8 are programmatically generated ASCII (_build/archetypes/gen_daa-iaa-counter-uas.py, alignment-guarded by _ck()), filled with Dublin Airport's real airspace, runways, feeds, agencies and the synthetic incursion decision — not a reused shell. PROBABILITIES. Every probability in this file is a [PRIOR] — a subjective pre-pilot estimate for prioritisation, not a forecast. Re-score after every real conversation.

---

§0 — Header & one-line thesis

Nexus Synergy for Dublin Airport: a sovereign counter-UAS airspace operating picture + evidence spine that sits above daa's existing Dedrone detection and ComReg-licensed mitigation — turning a working-but-siloed "the alert fired, now what?" into one fused, human-gated, fully-audited decision loop that coordinates daa ops, airport Gardaí, ATC and the IAA, and produces the tamper-evident evidence pack the new €500 fixed-charge enforcement regime needs.

Wedge: a counter-UAS airspace coordination + evidence-spine COP above Dedrone (object-tracking in airspace — explicitly NOT passenger biometric ID). Durable expansion: national C-UAS + CER airport-resilience COP. Intro: a test of Patrick Walsh's state/semi-state network into daa Group Security & Resilience. Demo: a synthetic Dublin-airspace C-UAS COP replaying an incursion end-to-end.

---

§1 — Entity snapshot (cited from the target card)

• daa plc — Irish state-owned commercial airports authority; operates Dublin Airport (Ireland's largest, ~33–35m pax/yr) and Cork Airport plus international businesses (ARI travel retail, daa International). 100% owned by the Irish State. The licensed aerodrome operator that physically deploys airport counter-UAS equipment under ComReg licence — it owns the asset, the operational risk and the procurement budget. (target card §1) [verified]
• Irish Aviation Authority (IAA) — national competent authority for civil aviation safety and the national regulator for civil drones / UAS: operator registration, remote-pilot certification, operational authorisations, airspace restrictions, oversight and enforcement; runs a "Just Culture" enforcement model and an inter-agency mechanism with An Garda Síochána and the Data Protection Commission. (iaa.ie/general-aviation/drones; iaa.ie media 2025-11-04) [verified]
• Why two entities in one package: daa owns the asset + budget (faster cycle); the IAA owns the regulatory framework, national UAS policy, detection/enforcement data and inter-agency convening power. A counter-UAS operating picture (vs. a single sensor) is bought and consumed across both. We sell to daa first, IAA as the regulatory/credibility anchor. (target card §1) [verified]
• Adjacent mandatory stakeholders: An Garda Síochána (airport policing + enforcement, holds operational primacy on C-UAS response), the Defence Forces / Air Corps (air-domain awareness; QRA at Casement Aerodrome; developing Ireland's first C-UAS programme), ComReg (RF spectrum licensing for any jamming), the Department of Transport (policy + capital). Counter-UAS at a national hub is inherently multi-agency — precisely the seam we target. (target card §1) [verified]

---

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

Three converging drivers make this a buying situation.

(a) Acute — recurring runway closures from drone incursions.

• In early February 2023 Dublin Airport suspended operations multiple times after confirmed drone sightings — "airport traffic had to be suspended six times in six weeks" per Ryanair, with hundreds of passengers diverted on consecutive days; disruptions recurred through 2023 and again in March 2024 (drone seized; north runway suspended, ops switched to south runway). (Irish Times 2023-02-03/04/06, 2024-03-24; RTÉ 2023-02-04) [verified]

(b) Detection works — but it surfaces violations, not a coordinated response.

• Dublin Airport runs a Dedrone detection system; in Nov 2025 the IAA concluded an investigation finding Wills Bros Ltd. flew drones without an Operational Authorisation or UAS Operator Registration inside the Dublin Control Zone (the "Red Zone", <2 km from the perimeter), detected by Dedrone. The IAA framed it as proof "of the effectiveness of detection systems" and resolved it under Just Culture (training + procedures, no prosecution). (iaa.ie 2025-11-04; rte.ie 2025-11-04; irishexaminer.com; thejournal.ie 2025-11) [verified] Detection working ≠ a coordinated decision-and-response loop with an evidence trail.
• daa has procured and operationalised non-kinetic counter-drone equipment (RF jamming / take-control-and-land) under a 2023 legislative amendment + a ComReg licence — but it is reactive, single-site, and not fused into a shared, audited, multi-agency operating picture. (siliconrepublic.com; RTÉ 2023-09-07) [verified]

(c) Regulatory + EU motion is creating budget pull.

• Ireland's August 2025 National UAS Policy Framework introduced fixed-charge offences (on-the-spot fines from €500), a National Working Group on geographical (no-fly) zones, and a U-space Steering Group; the Regulation of Drones Bill 2025 (Bill 61/2025) is progressing, addressing planning and noise aspects of drone operation. (Garda/IAA enforcement arrangements were already formalised separately by the IAA Unmanned Aircraft Systems (Drones) Order 2023.) (oireachtas.ie/bills/bill/2025/61; ts2.tech 2025; RTÉ 2025-10-01) [verified] A fixed-charge regime needs tamper-evident evidence — exactly what an audited COP produces.
• Sept–Oct 2025 saw major closures at Copenhagen (~4h, 100+ cancellations), Munich (twice in 24h, Oktoberfest period), Oslo and Aalborg, prompting the EU's European Drone Defence Initiative ("drone wall") within the Defence Readiness Roadmap; the acknowledged gap is "no coordinated ability to detect, identify, or neutralise hostile drones over airports." (cnn.com 2025-10-03/04; euronews.com 2025-11-20; dronelife.com 2025-10-17) [verified] This reframes the problem from nuisance to hybrid-threat resilience — the cross-agency, cross-sensor fusion+decision layer we build.

The gap our software fills: the detector and the jammer already exist. What's missing is the coordinated, audited decision layer between the Dedrone alert and a safe, defensible, multi-agency response — and the evidence spine the new enforcement regime requires.

---

§3 — Use-case & value (decline-safe framing)

What we sell: a sovereign counter-UAS airspace operating picture + evidence-spine decision layer — the coordination, decision, and task-and-assess loop that sits on top of daa's existing Dedrone detection and ComReg-licensed mitigation, not a replacement sensor or jammer.

Concretely:

• Fused airspace COP over the triple-renderer map: ingest Dedrone (and any future radar/RF/EO sensor) tracks, ADS-B/cooperative traffic, IAA no-fly geozones, the Dublin Control Zone ("Red Zone") boundary, runway state and ground assets (airport Garda units) into one ontology-backed common operating picture. Sovereign, EU-hosted, classification-aware.
• Closed action loop for an incursion: detect → enrich (correlate sensor tracks, classify track, check the IAA UAS registry, pull geozone/airspace context) → triage (risk band + proportionality) → human-gated sign-off (named operators authorise — this is the audited decision, not an autonomous kill-chain) → task (hold the runway, alert airport Gardaí, notify ATC/IAA, place Air Corps QRA on-call) → execute via write-back adapters → assess (BDA) → close, with a full FRIA + provenance ledger of who decided what, when, and why.
• Multi-agency shared picture + tamper-evident evidence pack: daa ops, airport Gardaí, IAA and (where authorised) the Air Corps see a consistent, access-controlled picture; every incursion produces an IAA Just-Culture / fixed-charge evidence pack with a Merkle-anchored PROV-O chain.

DECLINE-SAFE — the cleanest hook on the board, and we hold the line:

• This is object / airspace situational awareness and infrastructure protection, NOT people-surveillance. We do not propose, and will refuse: passenger biometric ID / real-time remote biometric identification at the terminal, facial recognition, emotion recognition, psychometric profiling, social scoring, predictive policing, untargeted scraping — all on our published Declined List.
• We track aircraft/UAS objects and authorised responder assets, not crowd identities. EO/IR frames are object-track boxes only; bystanders are auto-blurred at ingest (DPC rule). Any RF/operator-locating data is consumed as IAA/ComReg-governed enforcement evidence under their legal basis — we are the audited decision-and-record layer, not a covert collection tool.
• The human-in-the-loop sign-off is the product, not a disclaimer: no autonomous mitigation. Mitigation remains daa/ComReg-licensed and human-authorised; we record and coordinate it.

Value: turns a working-but-siloed detector + a reactive jammer into an auditable, multi-agency, decision-grade resilience capability, and gives the IAA an operational evidence/coordination spine for the new enforcement regime. Annual-contract potential high at a national hub with multi-agency scope; upside to very-high on Cork + national-airspace scope — scored conservatively given pre-pilot status.

---

§4 — Ontology (counter-UAS airspace)

The airspace instance the COP renders and the Decision Room reasons over (one shared ontology — the entities the map draws are the entities the incursion decision references):

• AirspaceVolume — the Dublin Control Zone / EIDW CTR (the IAA "Red Zone"); attributes: class, ceiling/floor, restriction.
• UasGeozone — an IAA no-fly / restricted geozone (from the National UAS Policy Framework); polygon + validity.
• SensorTrack — a Dedrone RF/radar detection (raw observation); attributes: source band, RCS, bearing, altitude AGL, velocity.
• FusedContact — the multi-sensor fused object (e.g. uXXX); classification ∈ {unknown, friendly, hostile-unknown}; carries the fusion log-likelihood W. (mirrors the W-16 Fellegi-Sunter fusion pattern)
• CooperativeTraffic — an ADS-B aircraft (e.g. EI-DEB on short final 28R) — context, never a track to mitigate.
• Runway — 10L/28R (north), 10R/28L (south); state ∈ {active, hold, closed}; carries the hold/closure decision.
• ResponderAsset — Garda Airport Unit G-04, ComReg RF mitigation asset, Air Corps QRA element; status + ETA.
• UasRegistryRecord — the IAA UAS operator/operation registry (enrichment: the no-match that makes a contact an incursion).
• IncursionDecision — the human-gated action (hold runway / coordinate response / mitigate); references the FusedContact + Runway, carries proportionality + sign-off + conditions.
• EvidencePack — the sealed, redacted (bystander-blurred), Merkle-anchored bundle disclosed to the IAA / Gardaí under the fixed-charge legal basis.

FusedContact, the geozone/airspace polygons and IncursionDecision are first-class entities; a runway-hold or any mitigation cannot be recorded as enacted without a complete dual-control human sign-off (the §5 CHECK). SensorTrack and Runway state are bitemporal so the post-event audit replays exactly what was known at the moment of the call.

---

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

Three tables. RLS isolates every tenant by app.current_org_id; the load-bearing CHECK forbids ever recording a runway-hold or RF-mitigation as enacted without a complete 2-of-2 human sign-off AND an airspace-clear precondition — the human gate is a database invariant, not just UI. (Pattern mirrors the W-16 cuas_engagement_order invariant.)

SQL
61 lines
Copy
-- 1. Fused airspace contact (the object of record; bitemporal; NO personal data)
CREATE TABLE synergy.fused_contact (
    contact_id      text PRIMARY KEY,                 -- 'uXXX'
    org_id          uuid NOT NULL,
    classification  text NOT NULL CHECK (classification IN ('unknown','friendly','hostile_unknown')),
    fusion_w        numeric,                          -- Fellegi-Sunter log-likelihood (e.g. +8.6)
    bearing_deg     numeric,
    alt_agl_m       numeric,
    velocity_ms     numeric,
    in_red_zone     boolean NOT NULL DEFAULT false,   -- Dublin Control Zone breach
    iaa_registry    text NOT NULL CHECK (iaa_registry IN ('match','no_match','pending')),
    valid_from      timestamptz NOT NULL DEFAULT now(),
    valid_to        timestamptz,                      -- bitemporal: NULL = current
    recorded_at     timestamptz NOT NULL DEFAULT now()
);
ALTER TABLE synergy.fused_contact ENABLE ROW LEVEL SECURITY;
CREATE POLICY rls_fused_contact ON synergy.fused_contact
    USING (org_id = current_setting('app.current_org_id')::uuid);

-- 2. Raw sensor detections feeding the fusion (Dedrone RF/radar; recorded_at-only)
CREATE TABLE synergy.sensor_track (
    track_id        bigserial PRIMARY KEY,
    org_id          uuid NOT NULL,
    contact_id      text REFERENCES synergy.fused_contact(contact_id),
    source          text NOT NULL CHECK (source IN ('dedrone_rf','dedrone_radar','eo_ir','ads_b')),
    band            text,                             -- '5.8GHz', 'X-band', 'Mode-S'
    rcs_m2          numeric,
    observed_at     timestamptz NOT NULL,
    prov_derived_from text NOT NULL,                  -- PROV-O: Dedrone/Aireon product id
    recorded_at     timestamptz NOT NULL DEFAULT now()
);
ALTER TABLE synergy.sensor_track ENABLE ROW LEVEL SECURITY;
CREATE POLICY rls_sensor_track ON synergy.sensor_track
    USING (org_id = current_setting('app.current_org_id')::uuid);

-- 3. The human-gated incursion decision (the action of record)
CREATE TABLE synergy.incursion_decision (
    decision_id     uuid PRIMARY KEY DEFAULT gen_random_uuid(),
    org_id          uuid NOT NULL,
    contact_id      text NOT NULL REFERENCES synergy.fused_contact(contact_id),
    disposition     text NOT NULL CHECK (disposition IN ('observe','hold_runway','coordinate','rf_mitigate')),
    runway          text,                             -- '28R' (NULL for observe/coordinate)
    proportionality numeric NOT NULL CHECK (proportionality BETWEEN 0 AND 1),
    airspace_clear  boolean NOT NULL DEFAULT false,   -- runway/QRA-clear precondition
    conditions      jsonb NOT NULL DEFAULT '[]',
    sign_daa_aoc    text,                             -- daa AOC duty manager QES
    sign_garda_ap   text,                             -- Garda Airport supt QES (2nd control)
    enacted_at      timestamptz,                      -- when the action actually took effect
    prov_room_id    text NOT NULL,                    -- PROV-O: the Decision Room activity id
    created_at      timestamptz NOT NULL DEFAULT now(),
    -- LOAD-BEARING INVARIANT: no enacted hold/mitigation without 2-of-2 human sign-off
    -- AND an airspace-clear precondition. 'observe'/'coordinate' need no enactment gate.
    CHECK (
        disposition IN ('observe','coordinate')
        OR enacted_at IS NULL
        OR (sign_daa_aoc IS NOT NULL AND sign_garda_ap IS NOT NULL AND airspace_clear IS TRUE)
    )
);
ALTER TABLE synergy.incursion_decision ENABLE ROW LEVEL SECURITY;
CREATE POLICY rls_incursion_decision ON synergy.incursion_decision
    USING (org_id = current_setting('app.current_org_id')::uuid);

The CHECK is the structural guarantee that "AI proposed, a human decided." A row can never reach enacted_at IS NOT NULL for a hold_runway/rf_mitigate unless both QES signatures and the airspace-clear precondition are present — the same rule the Decision-Room gate (§10) and the IAA/Garda evidence pack (§11) rely on. No table carries personal data — the wedge is object-tracking only.

---

§6 — Action-loop pseudocode (Python)

Python
47 lines
Copy
# Dublin-airspace counter-UAS action loop. AI proposes; a human gates; the DB CHECK enforces it.
# Object-tracking ONLY: no faces, no plates, no passenger identities anywhere in this loop.
def cuas_incursion_loop(org_id, ctr="EIDW"):
    # 1. DETECT — Dedrone RF downlink + radar paint inside the Dublin Control Zone.
    rf  = dedrone.rf_detection()                        # 5.8GHz Mavic-class downlink, bearing 092
    rdr = dedrone.radar_paint()                         # RCS 0.014 m2 @1.7km, 142m AGL, 14 m/s
    if not (rf and rdr):
        return  # nothing to decide yet

    # 2. ENRICH — fuse the streams (Fellegi-Sunter), check IAA registry + geozone + coop traffic.
    contact = fuse(rf, rdr, eo=dedrone.eo_ir())         # FusedContact uXXX, W=+8.6
    contact.iaa_registry = iaa.uas_registry_lookup(contact)   # -> no_match  == incursion
    contact.in_red_zone  = geozone.breaches(contact, "dublin_red_zone")
    coop = ads_b.cooperative_traffic(ctr)               # EI-DEB A320 short final 28R (context)

    # 3. TRIAGE — score severity + proportionality; nothing predictive about people.
    sev = triage(contact, coop, runway_conflict="28R")  # band HIGH, P = 0.88

    # 4. GATE — open the Decision Room; AI may ONLY recommend. Human sign-off is mandatory.
    gate = decision_room(
        title="Dublin-airspace incursion sign-off",
        personas=["op_tasking", "proportionality", "civil_society_iccl",
                  "devils_advocate", "domain_aviation_cuas"],
        recommendation="hold 28R departures + coordinate Garda/QRA (NO RF-mitig.)",
        proportionality=sev.P)                          # P = 0.88
    if not gate.accepted:
        write_decision(org_id, contact, disposition="observe", P=sev.P)   # logged, not enacted
        return

    # 5. PRECONDITION + TASK + EXECUTE — only after 2-of-2 QES AND airspace-clear.
    airspace_clear = atc.airspace_clear("28R") and air_corps.qra_deconflicted()
    if gate.disposition in ("hold_runway", "rf_mitigate") and not (
            gate.qes_daa and gate.qes_garda and airspace_clear):
        audit.append(contact.id, "hold/mitig unsigned or airspace-unclear -- withheld", merkle=True)
        return                                          # the DB CHECK would refuse it anyway
    decision = write_decision(org_id, contact, disposition=gate.disposition, runway="28R",
                              P=sev.P, airspace_clear=airspace_clear, conditions=gate.conditions,
                              sign_daa_aoc=gate.qes_daa, sign_garda_ap=gate.qes_garda,
                              enacted_at=now(), prov_room_id=gate.room_id)
    hold_runway("28R"); alert_garda_unit("G-04"); notify(["ATC", "IAA"]); place_qra_oncall()

    # 6. ASSESS (BDA) — did the contact retreat? was traffic safe? when to release the hold?
    bda = assess(contact, observed=dedrone.track, runway_state=atc.runway("28R"))   # track lost N of M50

    # 7. CLOSE — write BDA + PROV-O chain + the redacted, Merkle-anchored IAA evidence pack.
    seal_evidence_pack(contact, redact="bystander_blur", disclose=["IAA", "Garda"])
    close_loop(decision, bda, merkle=True)

---

§7 — nexus-workflows YAML DAG

The same loop as a declarative DAG. No cron anywhere — this is a nexus-workflows job triggered by the Dedrone fusion event. The human_gate node is blocking: the DAG cannot advance to task_execute until a 2-of-2 sign-off event arrives and the airspace-clear precondition is satisfied.

YAML
47 lines
Copy
workflow: dublin_cuas_incursion
trigger:
  on_event: dedrone.fused_contact_in_red_zone          # RF+radar fused inside the Control Zone
  tenant: "{{ org_id }}"
nodes:
  - id: detect
    run: dedrone_rf_radar_check
    out: [rf, radar]
  - id: enrich
    needs: [detect]
    run: fuse_and_classify                              # Fellegi-Sunter + IAA registry + geozone
    args: { registry: iaa_uas, geozone: dublin_red_zone, coop_feed: ads_b }
    out: [fused_contact, registry_match, coop_traffic]
  - id: triage
    needs: [enrich]
    run: severity_proportionality
    args: { runway_conflict: "28R" }
    out: [proportionality]
  - id: human_gate                                      # <-- BLOCKING human node
    type: human_gate
    needs: [triage]
    decision_room:
      personas: [op_tasking, proportionality, civil_society_iccl,
                 devils_advocate, domain_aviation_cuas]
      recommend: "hold 28R + coordinate Garda/QRA (no RF-mitigation)"
    precondition: { airspace_clear: true }              # ATC 28R clear + QRA deconflicted
    require: { signoff: 2_of_2, signers: [daa_aoc_duty, garda_airport_supt] }
    on_refuse: { goto: log_observe }                    # logged, never enacted
  - id: task_execute
    needs: [human_gate]                                 # only reachable after 2/2 QES + airspace-clear
    run: enact_incursion_response
    args:
      tasks: [hold_runway_28R, alert_garda_g04, notify_atc_iaa, place_qra_oncall]
  - id: bda
    needs: [task_execute]
    run: assess_and_release
    args: { release_when: [contact_retreated, runway_survey_clear] }
  - id: evidence
    needs: [bda]
    run: seal_evidence_pack
    args: { redact: bystander_blur, disclose: [IAA, Garda], legal_basis: drones_act_fixed_charge }
  - id: close
    needs: [evidence]
    run: write_audit_ledger
    args: { prov_o: true, merkle: true, regime: [IAA_just_culture, CER] }
  - id: log_observe
    run: write_decision_observe                         # the refuse branch, fully audited

---

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

Generated by _build/archetypes/gen_daa-iaa-counter-uas.py (guarded by _ck() — equal-length, pure-ASCII, no overflow). Pasted verbatim below. An SVG of the primary surface lives at _build/figures/daa-iaa-counter-uas/uc-map_ops.svg.

Figure c01.1 — map_ops (PRIMARY) — Dublin Airspace Counter-UAS COP. Components: ShellLayout + TopBar (PccPill + RendererChip) + ClassificationBanner (object-tracking only) + LeftSidebar glyph-rail + MapConsole (MapLibre 2D) rendering the Dublin Control Zone "Red Zone", IAA geozones, the fused uXXX UAS track + heading vector, cooperative ADS-B traffic, runway state and Garda assets + right-docked Inspector (FusedContact) + BottomStatusBar INCIDENTS ticker.

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

+------------------------------------------------------------------------------------------------------+
| Dublin Airspace Counter-UAS COP - EIDW Red Zone (MapConsole + MapLibre-2D)                           |
+--------------------+---------------------------------------------------------------------------------+
| LAYERS             | MAP  ========================================================================== |
| [x] Dedrone track  |   N  Dublin CTR / EIDW  (Dublin Control Zone = IAA 'Red Zone', <5km)            |
| [x] ADS-B coop     |   |   ====== NORTH RWY 10L/28R (active, departures) ======= HOLD?               |
| [x] IAA geozones   |   |                                                                             |
| [x] Red Zone bdy   |   |   uXXX  UAS track  bearing 092 / 142m AGL / 14 m/s closing                  |
| [x] Runway state   |   |     \   RF 5.8GHz downlink (Mavic-class sig) + radar 0.014m2                |
| [ ] EO/IR pod FoV  |   o------\------[ Dublin Red Zone boundary ]----------------------              |
| [x] Garda AP units |   |       \  cooperative ADS-B: EI-DEB A320 short final 28R                     |
| [ ] ComReg RF mitig|   |   ===== SOUTH RWY 10R/28L (active, arrivals) ===== TRAFFIC ON               |
|                    |   |   <!> uXXX NOT in IAA registry / no authorisation / no remote-ID            |
| REPLAY (synth)     |   |                                                                             |
| Incursion uXXX     |   +  Garda Airport Unit G-04 staged @ Pier 1 apron (2 min)                      |
| Object-track ONLY  |   +  daa AOC duty + ATC tower notified  | ComReg RF asset: STANDBY              |
| [<<] t-90s [>>]    |                                                                                 |
|                    |   INCURSION CANDIDATE: uXXX inside Red Zone, RWY-28R conflict                   |
| SOURCES            |   Proportionality P=0.88 | human sign-off REQUIRED (no auto-mitig.)             |
| Dedrone feed       |   [ Open Decision Room ] [ Hold 28R departures ] [ Annotate track ]             |
| Aireon/IE ADS-B    |                                                                                 |
| IAA geozone API    |                                                                                 |
+--------------------+---------------------------------------------------------------------------------+
| INCIDENTS: 03:47 uXXX RF+radar fused | 28R short-final EI-DEB | Garda G-04 staged | QRA on-call      |
+------------------------------------------------------------------------------------------------------+

Figure c01.2 — command_dashboard — daa Group Security & Resilience C-UAS Readiness Board. Components: ShellLayout + KPI tile row (PccPill-fed) + LIVE ALERT FEED (the second-by-second incursion timeline) + BottomStatusBar. This is the economic buyer's board — incursions in the last 30 days, open contacts, runway/passenger exposure, and IAA-ready evidence-pack completeness.

Figure — Command dashboard (KPI + live feed). Production-fidelity React surface (buildable); the faithful ASCII follows.

+--------------------------------------------------------------------------------------------------+
| daa Group Security & Resilience - C-UAS Readiness Board (BottomStatusBar live)                   |
+--------------------------------------------------------------------------------------------------+
| INCURSIONS 30d        | OPEN NOW              | RWY IMPACT            | EVIDENCE PACKS           |
|   7 confirmed         |   1 (uXXX)            |   28R hold req        |  7/7 complete            |
|   +2 vs prior         |   P=0.88 HIGH         | >40k pax exposed      |  IAA-ready               |
+--------------------------------------------------------------------------------------------------+
| LIVE ALERT FEED                                                                                  |
|  03:47:09  Dedrone RF 5.8GHz downlink, Mavic-class sig @ bearing 092                             |
|  03:47:18  Radar paint RCS 0.014m2 @1.7km, 142m AGL, closing 14 m/s                              |
|  03:47:25  FUSE -> FusedContact uXXX (W=+8.6); not in IAA UAS registry                           |
|  03:47:31  ATC: EI-DEB A320 short final 28R - runway conflict flagged                            |
|  03:47:40  TRIAGE band HIGH (P=0.88); Decision Room auto-convened                                |
|  03:47:55  Garda Airport Unit G-04 staged; Air Corps QRA placed on-call                          |
|  03:48:30  GATE: hold 28R departures - 2/2 sign-off (daa AOC + Garda)                            |
|  03:51:10  BDA: uXXX track lost N of M50; evidence pack -> IAA Just-Culture                      |
+--------------------------------------------------------------------------------------------------+

Figure c01.3 — video_studio — UAS Incursion Evidence Pack. Components: ChatTerminal-adjacent Inspector evidence-studio + EO/IR frame viewer + the redaction/disclosure timeline + the [ Export IAA pack ] [ /dual-control seal ] [ Disclose to Garda ] action bar. The frame is an object-track box only — no faces / no plates, bystanders auto-blurred at ingest — the structural proof of the decline-safe line.

Figure — Evidence / redaction studio. Production-fidelity React surface (buildable); the faithful ASCII follows.

+------------------------------------------------------------------------------------------------+
| UAS Incursion Evidence Pack - uXXX (Inspector + redaction)   [ EO/IR | RF | Audit ]            |
+----------------------------------------------+-------------------------------------------------+
| +------------------------------------------+ | EVIDENCE PACK  uXXX  (IAA Just-Culture)         |
| |  EO/IR POD  PTZ-2   03:47:33  142m AGL   | | -------------------------------------------     |
| |                                          | | t-00:90  RF 5.8GHz downlink  [sealed]           |
| |        .--.        <- UAS object         | | t-00:81  radar RCS 0.014m2   [sealed]           |
| |      _/    \_   (quad airframe, no ID)   | | t-00:75  EO/IR confirm frame [redacted]         |
| |     (  o  o  )   bearing 092 / 1.4km     | | t-00:60  IAA registry check: NO MATCH           |
| |      \______/                            | | t-00:30  geozone breach: Dublin Red Zone        |
| |   ## NO FACES / NO PLATES IN FRAME ##    | | t+00:00  human gate 2/2 QES sign-off            |
| |   object-track box only; bystanders      | | t+03:40  track lost / BDA close                 |
| |   auto-blurred at ingest (DPC rule)      | |                                                 |
| +------------------------------------------+ | Redaction: bystander auto-blur ON               |
|                                              | Disclosure: IAA + Garda (lawful basis           |
|                                              |  = Reg. of Drones Act / fixed-charge)           |
|                                              | Merkle-anchored | PROV-O chain attached         |
+----------------------------------------------+-------------------------------------------------+
|   [ Export IAA pack ]   [ /dual-control seal ]   [ Disclose to Garda ]                         |
+------------------------------------------------------------------------------------------------+

---

§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

Figure §9.0 — Dashboard ↔ field-unit coordination loop (cluster C): the command COP, the Pixel field unit, and the wire between them annotated with the real synergy-server endpoints — LIVE (/api/v1/cop/picture, /viewport/state) vs PENDING-for-demo (/api/v1/field/{tasks,reports}).

Literal click-path. On the map_ops COP, the daa AOC duty manager scrubs the synthetic incursion replay to t-90s, sees the Dedrone RF + radar fuse into uXXX inside the Red Zone with no IAA-registry match and a 28R short-final conflict (cooperative EI-DEB), selects the contact and clicks [ Open Decision Room ] → in the ChatTerminal Decision Room the five persona bubbles run; the ICCL civil-society persona pins the no-RF-mitigation / bystander-blur condition, the aviation-CUAS domain persona refutes a "contracted survey drone" hypothesis on schedule + entry-vector; the AOC manager clicks [ /dual-control sign ] (control 1) → the Garda Airport supt adds control 2 → with 28R airspace-clear confirmed, [ /execute ] enacts the hold 28R + coordination, which writes back to ATC / airport Gardaí / IAA and drops the redacted, Merkle-anchored evidence pack into the ledger. An [ Observe ] or [ Refuse + log ] path is equally first-class and fully audited. The command_dashboard updates the readiness board; the video_studio produces the IAA-disclosable pack.

  map_ops (airspace COP)            decision_room (incursion sign-off)        write-back + evidence
  +------------------+   [Open      +-----------------------------+   [/exec  +-------------------+
  | scrub replay     |    Decision  | 5 persona bubbles           |   after   | hold 28R / ATC    |
  | uXXX FUSE in     |--- Room ]--->| ICCL pins no-RF-mitig +     |-- 2/2 --->| Garda G-04 / IAA  |
  | Red Zone, no reg |              | bystander-blur condition    |   QES +   | redacted evidence |
  | [Open Dec.Room]  |<- [Observe]--| [/dual-control sign x2]      |  airspc-  | PROV-O + Merkle   |
  +------------------+   re-poll    +-----------------------------+   clear   +-------------------+

---

§10 — Decision-Room transcript (the incursion dialectic)

Convened the moment Dedrone RF + radar fuse into uXXX (W = +8.6) inside the Dublin Control Zone with no IAA-registry match and a 28R short-final conflict. Hosted in the right-docked ChatTerminal. Personas dispatched per the AI Provider Router L-tier; all model calls are EU-sovereign (no US hyperscaler/LLM for this tenant's restricted operational data).

• Op-tasking (L3 EuroLLM-EU): "Recommend hold 28R departures and coordinate the airport Garda unit + place Air Corps QRA on-call. uXXX is unregistered, inside the Red Zone, on a converging bearing with EI-DEB on short final. Passive/coordinated response — explicitly NOT RF-mitigation unless the Garda/Defence-Forces ROE precondition is met and authorised."
• Proportionality (L3 Mistral-Large-EU): "Weigh a 28R departure hold (minutes of delay) against a runway-incursion safety event on a live arrival. Asset + flight-safety risk outweighs throughput. P = 0.88 [N 0.93 / P 0.88 / L 0.84]. Proportionate. Release the hold only on contact-retreat + a runway survey."
• Civil-society / rights (ICCL persona): "Confirm this stays object-tracking only: no facial recognition, no passenger biometrics, no bystander identification. The EO/IR pod must record an object-track box only; bystanders auto-blurred at ingest (DPC rule). Condition: no RF-mitigation under this gate; any operator-locating RF data is handled only as IAA/ComReg enforcement evidence under their legal basis." → conditions carried into the gate.
• Devil's advocate (L2 Mistral-7B, local-to-tenant): "Could uXXX be a contracted survey drone mis-tagged? — entry vector 092° is not the published survey corridor, there's no scheduled authorisation in the IAA registry, and the airframe class doesn't match the contracted platform. False-hold cost (minutes) ≪ a live runway-incursion. Observe-only = NO." (the concession is itself recorded as a prov:Entity)
• Domain expert (Aviation + C-UAS doctrine, L3 EuroLLM-EU): "Concur. The fused contact is unregistered, inside the Control Zone, converging on an active arrival. Standing inter-agency arrangement: An Garda Síochána holds operational primacy; the Air Corps provides deconfliction/QRA on request. Recommend the coordinated hold + Garda tasking, mitigation only under DF-authorised ROE."
• GATE VERDICT — ACCEPT (hold 28R + coordinate; REFUSE RF-mitigation under this gate). Proportionality 0.88 ≥ P_min; conditions {object-track-only, bystander-blur, no-RF-mitig under this gate, release on retreat+survey} carried; 2-of-2 dual-control (daa AOC duty manager + Garda Airport supt) + 28R airspace-clear required. The §5 DB CHECK will refuse to record enacted_at until both QES signatures and the airspace-clear precondition are present.

---

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

Write-back (three sinks). On /execute: (1) ATC / runway — hold 28R departures; (2) multi-agency tasking — alert Garda Airport Unit G-04, notify the IAA, place Air Corps QRA on-call; (3) the synergy.incursion_decision row reaches enacted_at carrying both QES signatures, the airspace-clear precondition, and the carried conditions.

BDA (loop close), three observations. (a) t+0–3 min — hold enacted + Garda staged confirmed (ObservationLevel 4, direct). (b) t+3:40 — contact behaviour: uXXX track lost north of the M50; runway-survey clearance to release the hold (ObsLvl 4). (c) post-event — fused-contact classification vs the eventual ground truth (was it the Wills-Bros-class unauthorised-but-benign operator, or hostile?), logged back to tune the fusion threshold (ObsLvl 3). Each BDA result registers a ProspectiveItem if the call diverged from observation.

PROV-O chain (finding → close):

[entity: Dedrone RF 5.8GHz + radar RCS 0.014m2]
        │ wasDerivedFrom (Dedrone / Aireon product ids)
        ▼
[activity: fellegiSunterFusion v1.4.2]  → [entity: FusedContact uXXX  W=+8.6]
        │ used → [entity: IAA-registry NO_MATCH] + [entity: Red-Zone breach]
        ▼
[activity: Decision-Room dublin-cuas-incursion]  (5 personas)
        │ wasAttributedTo → [agent: daa AOC duty mgr + Garda Airport supt (2/2 QES)]
        ▼
[entity: incursion_decision  hold_runway 28R  P=0.88  airspace_clear=true]
        │ wasGeneratedBy → write-back (ATC hold / Garda G-04 / IAA / QRA)
        ▼
[entity: BDA  track-lost N-of-M50]  → [activity: UNO close + EvidencePack seal]
        │ wasGeneratedBy → [entity: redacted Merkle-anchored IAA evidence pack]

Every node carries prov:wasAttributedTo (agent), prov:wasGeneratedBy (activity); the chain is Merkle-anchored at interval τ. The ICCL object-track-only / bystander-blur condition becomes a discoverable provenance edge — if a data-subject or the DPC later challenges the EO/IR capture, the graph proves the redaction condition was carried before execution.

Regulatory traceback (deltas only, vs §4.0 civil-protection defaults). The evidence pack is the IAA Just-Culture / fixed-charge evidence artefact (sealed, redacted, disclosable under the Regulation of Drones Act fixed-charge legal basis), exported as deltas since the last submission; the same ledger supplies CER airport-resilience incident evidence on the expansion. AI Act: an AI system used in emergency-response dispatch can fall under Annex III §5(d) — but the wedge processes no personal data (object-tracking only, bystanders blurred at ingest), so the high-risk/biometric surface is avoided by design; Art-5 prohibitions on real-time remote biometric ID do not attach because we do not do biometric ID. (Note for accuracy: EU AI Act Article 5 prohibitions applied from 2 February 2025.) (needs solicitor + DPO confirmation at pilot scoping)

---

§12 — Buyer & stakeholders

• Economic buyer (asset side): daa — most likely Group Security & Resilience and/or Head of Airport Operations (the owner of "what happens between the Dedrone alert and a safe, defensible response"), with daa Group CTO/CIO for the platform; daa Procurement runs the formal process. (named contact TBD — first ask of Patrick)
• Champion hypothesis: an operations/resilience leader who lived the 2023 closures and now owns the alert-to-response gap. (not verified — do not invent)
• Regulatory anchor / credibility buyer: the IAA — Director of Safety Regulation / UAS lead running the National UAS Policy Framework + the Garda/DPC inter-agency mechanism. Unlikely to be the paying customer for an airport COP, but the gatekeeper to operational authorisation, data-sharing legitimacy and reference value.
• Mandatory co-stakeholders: An Garda Síochána (airport policing + enforcement, operational primacy on C-UAS response), ComReg (any RF/mitigation interaction), Defence Forces / Air Corps (QRA deconfliction; hybrid-threat framing if scope widens), Department of Transport (policy + capital).
• Bridge: Patrick Walsh (Dogpatch) — a test of whether his state/semi-state network reaches daa Group Security & Resilience (§21).

---

§13 — Competition / incumbency + comparator

• Detection incumbent: Dedrone (now Axon) is already deployed at Dublin Airport. We do not position against it — we sit above it and ingest it. Trying to displace the sensor loses; integrating it wins. [verified deployment]
• Mitigation incumbent: a ComReg-licensed non-kinetic counter-drone system is already operational at daa. We orchestrate and audit the human-gated response; we don't supply the jammer. [verified]
• C-UAS platform competitors (global): Dedrone/Axon, DroneShield, D-Fend, Fortem, plus primes (Leonardo, Thales) for "drone-wall"-scale programmes. Most are sensor/effector-led; the decision-loop + editable-ontology COP + multi-agency audit + sovereignty-by-construction niche is comparatively open, especially for an Irish/EU-sovereign buyer wary of US/non-EU data control. [likely]
• Comparator (fold AS-status into the sentence): the nearest disclosed analogue is a prime-led C-UAS deployment for high-value-site protection — e.g. Leonardo's Falcon Shield C-UAS and its disclosed counter-UAS contracts for the Italian Army and Air Force (and the Leonardo/MBDA laser-based counter-drone programme announced Dec 2024); Italian state forces also operate tactical anti-drone systems around Vatican sites under a Public Security Inspectorate procurement [unverified as a Leonardo press disclosure]. These are sensor-and-effector-led. Nexus Synergy wins on: the human-gated closed action loop (detect→gate→execute→BDA) with a proportionality-scored Decision Room (incl. an ICCL civil-society persona seated inside the decision), per-action PROV-O bundles, dissent-as-record, and a sovereign multi-tenant federation with the IAA/Gardaí. Loses on: we do not ship the effector itself (Leonardo/DroneShield do) — we are the C2/evidence spine, not the kinetic; and a pre-pilot maturity gap. Ties on: the underlying sensor-fusion accuracy and map rendering.
• Incumbency reality: because detection + mitigation already exist, the question isn't "who detects" but "who owns the coordinated, audited decision layer" — a less-crowded, defensible position; the headwind is that the buyer may believe the problem is "solved," which lengthens the sale. Net: moderate.

---

§14 — Readiness (honest)

• Status: pre-incorporation, pre-revenue, pre-pilot. The ~178 UI surfaces are a gallery; the closed C-UAS action loop over a live Dedrone/ADS-B feed is not built or proven. The triple-renderer map, classification-aware AI Provider Router, FRIA + provenance ledger are architected and partially built. [verified — self-assessment]
• Strong reuse: the W-16 / W-18 counter-UAS fusion + RAP pattern (Fellegi-Sunter sensor fusion, Decision-Room dialectic with an aviation + civil-society persona, MapLibre airspace overlay, PROV-O evidence chain) overlaps heavily — this demo is cheap to assemble relative to a cold use case.
• Real gaps to close before a credible pilot: (a) data access — a sandboxed/replayed Dedrone feed + ADS-B + the IAA UAS-registry / geozone API (availability, format, governance — an integration seam, and the slow part); (b) a counter-UAS airspace ontology instance (§4); (c) a defensible incursion decision workflow + evidence-pack demo (§§5–11) with the bystander-blur redaction proven. None require anything on the Declined List.
• Strongest ready asset: the sovereignty + audit + decline-safe story maps cleanly onto an Irish state body's data-residency and accountability requirements and the EU drone-wall narrative.

---

§15 — ENGAGEMENT PLAYBOOK (ready-to-go sequence)

The repeatable motion: first-contact → free discovery → demo → pilot → LOI → signed contract. Each stage = trigger / owner / activity / template-or-script / exit criterion / deliverable.

Stage 1 — First contact (test the warm bridge)

• Trigger: Patrick confirms whether his state/semi-state network reaches daa Group Security & Resilience (or the Dept of Transport aviation team). Owner: Founder (+ Patrick). Exit: a scheduled discovery call with a named sponsor. Deliverable: the intro email (§21) sent + a calendar hold.
• Activity: ask Patrick who specifically — daa Group Security & Resilience vs Airport Operations vs daa Innovation vs the Dept of Transport. Frame the meeting around the alert-to-response gap + the fixed-charge evidence spine (concrete, recurring, multi-agency), holding national-C-UAS + CER as the durable expansion. If Patrick's network does not reach daa, fall back to a Research-Ireland / EUDIS sovereign hybrid-threat resilience framing.

Stage 2 — Free discovery (~45–60 min, listening session, no slides)

• Trigger: discovery call booked. Owner: Founder. Exit: named sponsor agrees the alert-to-response gap is worth solving + names a budget owner. Deliverable: a same-day write-up (sponsor, top-3 pains in their words, lawful basis, action-loop gap, Declined-List PASS, funding-vehicle hint, agreed next step).
• Script (adapted 60-min agenda):
  • 0:00–0:05 Frame: "Irish-built, EU-sovereign decision-intelligence platform — the Palantir for the EU with sovereignty in the architecture. This is discovery, not a pitch. We track objects in airspace — explicitly not passengers."
  • 0:05–0:20 Current picture: "Walk me through the last drone incursion from the Dedrone alert to the moment it closed. Who touched the call — daa ops, airport Gardaí, ATC, the IAA — in what order? How many systems did you look at? How did you evidence it afterwards for the IAA?"
  • 0:20–0:35 Governance: "What's the lawful basis for the Dedrone/RF data into a coordination layer? Any personal data — and how do you keep it object-only? Are you in scope for CER airport resilience, and how do you evidence the new fixed-charge regime today?"
  • 0:35–0:45 Path: "Who owns the C-UAS / resilience software line — Group Security & Resilience, Airport Ops, or the Dept of Transport? Is material spend OJEU/eTenders? Is there a programme (the UAS Policy Framework implementation, EU drone-wall, EUDIS, Research-Ireland Defence Innovation) this could sit under?"
  • 0:45–0:55 Map their loop: sketch detect→enrich→triage→gate→task→execute→assess→close; mark where they jump from Dedrone-alert straight to a phone-tree response with no fused picture, no proportionality gate, no evidence pack (the wedge).
  • 0:55–1:00 Earn the demo: "If I came back with a 30-min walkthrough replaying a Dublin-airspace incursion in our platform — your kind of data, not generic — would that be worth your time?"

Stage 3 — Scoped demo (their loop replayed, not a feature tour)

• Trigger: sponsor agrees to a walkthrough. Owner: Founder. Exit: "Could we try this on a real (sandboxed) slice of our data?" Deliverable: the synthetic Dublin-airspace C-UAS COP demo (§8 surfaces) + the one-page pilot proposal (Stage 4).
• Activity: drive the synthetic incursion replay end-to-end on the map_ops COP: scrub to RF+radar fuse → no IAA-registry match + Red-Zone breach + 28R conflict → open Decision Room → show the proportionality score + the ICCL civil-society persona pinning the object-track-only / bystander-blur / no-RF-mitigation conditions + the aviation domain persona refuting the contracted-survey hypothesis → 2/2 sign-off + airspace-clear → write-back (hold 28R / Garda / IAA) → the redacted, Merkle-anchored evidence pack (video_studio). Lead with sovereignty + audit + the decline-safe line; explicitly position above Dedrone. Be honest about maturity.

Stage 4 — Pilot (time-boxed, sandboxed feed, agreed success criteria)

• Trigger: demo exit-ask answered yes. Owner: Founder + daa champion. Exit: success criteria met or credibly trending. Deliverable: signed one-page pilot proposal + pilot run.
• One-page pilot proposal (filled for daa):
  1. Title & sponsor: "Dublin-Airspace Counter-UAS Coordination & Evidence-Spine — pilot." Sponsor: [daa Group Security & Resilience lead, TBD]; budget owner: [daa Ops / Group Security, TBD].
  2. Problem (their words): "When Dedrone fires, the response runs on phone calls across daa ops, airport Gardaí, ATC and the IAA, and we can't easily produce a tamper-evident evidence pack afterwards." (to confirm in discovery)
  3. The one thing we'll prove: "We can fuse Dedrone + ADS-B + IAA geozones into one operating picture and shorten the time from Dedrone-alert to a defensible, signed-off coordinated response from X to Y, with a complete IAA-disclosable evidence pack." (X/Y baseline TBD, measured pilot week 1.)
  4. Scope IN / OUT: IN — a sandboxed/replayed Dedrone + ADS-B feed for the Dublin Control Zone, IAA geozones, the incursion decision loop + evidence pack. OUT — Cork/national, live mitigation control, any personal data / passenger biometrics, any Declined-List capability.
  5. Data & lawful basis: Dedrone + ADS-B + IAA geozone/registry (object data only, no personal data; lawful basis = airport security/resilience + IAA enforcement). Runs EU-sovereign; isolation tier set to feed sensitivity.
  6. Success criteria (2–4, sponsor-agreed): alert-to-coordinated-response Δ; evidence-pack completeness for an IAA submission; multi-agency picture consistency; sponsor confidence in the gate. (baselines TBD week 1)
  7. Timeline: 6–12 weeks (exact TBD), with a mid-point checkpoint + an incursion-replay validation run.
  8. Commercials: €0 to daa if innovation-grant-funded; otherwise a scoped sub-threshold pilot (indicative production band Tier-1 €120–240k/yr — §19, only if asked).
  9. Roles: Founder/partner-vehicle delivers; daa champion supplies the sandboxed feed + a duty officer for a parallel run; IAA named as a stakeholder for data-sharing legitimacy; named POCs both sides.
  10. After: an LOI if criteria are met.
  11. Funding vehicle: daa security capex / Dept of Transport policy budget / Research-Ireland Defence Innovation / EUDIS — confirm in discovery.

Stage 5 — LOI (the milestone, triggers the Patrick check)

• Trigger: pilot success criteria met. Owner: Founder + sponsor. Exit: signed LOI naming a sponsor + next step. Deliverable: signed (non-binding) LOI.
• LOI checklist (key items): parties (daa + Nexus Synergy Ltd, or founder-in-own-name pre-incorporation, NewCo to ratify under Companies Act 2014 s.45) · statement of intent (proceed to next phase, conditional on funding/procurement) · scope carried from the pilot · success criteria referenced · named sponsor + budget owner · indicative timeline + next step · indicative commercials ("to be scoped under [vehicle]") · conditions (funding award, OJEU/eTenders process, IAA data-sharing legitimacy, ComReg interaction if any, security accreditation) · binding vs non-binding (default non-binding except confidentiality) · governing law: Irish · Declined-List affirmation (object-tracking only; no passenger biometrics) · signatures + dates · solicitor review confirmed before sending (flag, do not assume).

Stage 6 — Signed contract

• Trigger: LOI + a procurement route. Owner: partner-vehicle + daa Procurement. Exit: executed contract / framework call-off. Deliverable: the signed contract — gated on a partner-vehicle / Stamp-4 path (§16, §18, §20) and daa's formal (likely OJEU/eTenders) procurement.

---

§16 — PM / timeline

Gantt (indicative; bars = active stages; all durations [PRIOR], TBD with sponsor):

Stage \ month         M1   M2   M3   M4   M5   M6   M7   M8 .. M12 .. M30
1 First contact       ####
2 Discovery (free)     ######
3 Scoped demo            ####
4 Pilot (sandbox feed)      ##########
5 LOI                                ####                 <-- Patrick-check
6 Contract / OJEU                        ............>>>>>>>> .. >>>>>>>>>
* Partner-vehicle gate  [.....resolve Stamp-4 / partner-vehicle.....]^ critical for PAID pilot/contract

• Milestones: M1 intro test (does Patrick reach daa) · M3 sponsor agrees the alert-to-response gap (discovery exit) · M4 demo "try it on sandboxed data" · M6 pilot start · M8 pilot success read-out · ~M9–12 LOI (Patrick check) · M18+ contract / OJEU framework.
• Critical path: the Stamp-1G → Stamp-4 / partner-vehicle gate is the binding constraint for a PAID pilot or any signed contract — a free discovery + demo + grant-funded pilot can run before it, but the paid contract cannot close until the vehicle resolves (§18, §20). daa's OJEU/eTenders procurement is the second long pole; the IAA data-sharing legitimacy sign-off is the third.

RACI:

---

§17 — Funding / procurement vehicle

• daa capital / operational security budget. daa is a commercial state company that already self-funded the Dedrone system and the ComReg-licensed counter-drone equipment — it has, and spends, a critical-infra security budget; a COP/software follow-on is a credible line item. Public procurement rules apply (likely OJEU/eTenders for material spend) → slower, more formal cycle. [verified buyer self-funds C-UAS]
• Aviation-security / Dept of Transport policy budget. The 2025 UAS Policy Framework + the Regulation of Drones Bill 2025 (planning/noise) on top of the existing IAA Drones Order 2023 enforcement regime create programmatic appetite; national airspace-picture work could be funded as policy implementation. [likely]
• EU sovereign-defence vehicles (strategically aligned): the European Drone Defence Initiative / "drone wall" + EUDIS / EDF 2026 lines are explicitly about layered detection–decision–interception over European skies — purpose-built for our sovereign, classification-aware positioning; most EDF 2026 calls close 29 Sep 2026 (consortium-only), though the expedited multi-domain operations cloud call closed earlier on 28 Apr 2026. Research-Ireland Defence Innovation Challenge could fund a dual-use airspace-awareness pilot (academic-routed). [verified vehicles; specific fit TBD]
• Procurement-vehicle correction (verified): CER/CRU regulates energy & water, not aviation — the original "CER transport-air" seed is a misroute; aviation economic regulation sits with the IAA's Commission for Aviation Regulation functions. The real money is daa capex + Dept of Transport + EU defence-innovation. (target card §6) [verified — discount the CER route]

---

§18 — TWO-STAGE FORMULA SCORECARD

Anchored to board #3 (daa): Score 71.6, to-LOI 30–42%, to-buy 21–30% — and to the formula worked-example (C). All factor cells [PRIOR] with a dated rationale.

Stage-1 — P(LOI), H = 12–18 mo. Vector = {mandate_pull, access_warmth, demonstrability, decline_safety, white_space, cycle_speed, pillar_fit}; weights {.22,.22,.18,.14,.10,.08,.06}.

S1 = .22·5 + .22·2 + .18·4 + .14·5 + .10·3 + .08·2 + .06·5 = 3.72. P_LOI = 0.55 / (1 + exp(−1.15·(3.72 − 2.6))) = ≈ 0.41 (band 33–46%). Score100 = S1·20 = 74 (board anchor 71.6 ✓, within ~3 pts).

Stage-2 — P(Contract | LOI), H = 24–36 mo. Vector = {contractability, funding_to_pay, procurement_clarity, incumbency_displacement, time_to_value, reference_leverage}; weights {.24,.22,.18,.16,.12,.08}.

S2 = .24·1 + .22·4 + .18·2 + .16·4 + .12·2 + .08·3 = 2.60. P_raw = 0.70 / (1 + exp(−1.1·(2.60 − 2.8))) = ≈ 0.31.

Legal gate G = V·T (T ≈ 1 here, H_conv = 30 mo, t_resolve ≈ Stamp-4 in ~3 mo):

Reconciliation to board anchor. P_LOI ≈ 41% sits inside the board's to-LOI 30–42%. The board's to-buy 21–30% is the post-vehicle figure (V→1.0 → P(Contract|LOI) ≈ 31%, top of band ✓); today, solo on Stamp-1G, the unconditional to-buy is ~3.1% — the vehicle is the lever, not Stage-1 or Stage-2. Score100 = 74 ≈ board 71.6 (within ~3 pts). Worked-example (C) gave S1 ≈ 3.72 / P_LOI ≈ 0.41 / V=1 → 31% — this scorecard matches it.

---

§19 — Commercial

• Pilot: Tier-1 €120–240k band (often €0 to daa if innovation-grant-funded; a paid pilot needs the partner-vehicle).
• Expansion: high-value — Cork + national-airspace C-UAS + CER airport-resilience framework; could reach very-high at full national-airspace scope (target card: €500k–2.4m annual at a national hub; upside to very-high on Cork + national expansion).
• Contract terms (indicative): annual subscription on the open-component substrate (no per-seat lock-in); cost advantage from open-source substrate + sovereign HPC + shared conformity file + no forward-deployed-engineer dependency; sit-above-Dedrone integration (no sensor rip-and-replace).
• Buyer requirements to satisfy: ISO-27001, EU data-residency / sovereignty (model calls stay in-jurisdiction via the classification-aware AI Provider Router), a data-sharing agreement for Dedrone/ADS-B/IAA feeds with IAA legitimacy, the bystander-blur redaction guarantee, and (for the CER expansion) the resilience-evidence export. [verified as standard public-body requirements; specific accreditation TBD]

---

§20 — Legal blockers

• Stamp-1G cap (founder): Stamp 1G bars self-employment, operating/establishing a business, and being a company director — the founder cannot be a director, incorporate, or trade until Stamp 4 (applied for, ~3 mo out). (Passive shareholding is not explicitly barred by Stamp 1G, but active founder/operating roles are — confirm with an immigration solicitor before relying on any equity structure.) A paid daa pilot/contract therefore needs a partner-vehicle path (MAHI or a Dogpatch-brokered entity) or to wait for Stamp 4. (immigration-solicitor confirmation required) [⚖️ CONFIRM]
• OJEU/eTenders procurement (daa): material spend at a state commercial body is formal tender-bound — anticipate a negotiated/exempt or sub-threshold pilot route first; security-sensitive elements may qualify for Defence Procurement Dir. 2009/81/EC / Art-346 TFEU exemption (helps or excludes). [verified regime; route TBD]
• Data-governance legitimacy: the legal basis for sharing Dedrone RF / operator-locating enforcement data into a third-party COP must be confirmed with the IAA / ComReg / DPC — our "audited decision layer, not collector" framing depends on it being acceptable; bystander auto-blur at ingest + object-track-only must be DPO-validated. (needs IAA + DPO confirmation) [⚖️ CONFIRM]
• GDPR / personal data: the wedge processes no personal data (object-tracking only; bystanders blurred), so the GDPR + AI-Act high-risk surface is minimised by design; any future terminal/perimeter extension touching personal data must be re-assessed (DPO + solicitor). [flag]
• AI Act: an emergency-response/dispatch AI can attach Annex III §5(d), but the biometric-ID prohibition (Art-5, applicable 2 February 2025) does not apply because we do not do biometric ID; high-risk classification is avoided for the object-only wedge. (solicitor + DPO confirmation) [flag]
• Dual-use export Reg. (EU) 2021/821: the Regulation controls RF-monitoring equipment among its cyber-surveillance items, so an RF-monitoring component could attract export controls — export classification per configuration + end-use due diligence. (counsel) [⚖️ CONFIRM]
• Pre-incorporation signing: until NewCo is formed the founder signs LOIs in their own name (personal liability), NewCo to ratify under Companies Act 2014 s.45; prefer non-binding wording; protect discovery under a mutual NDA. [flag]

---

§21 — Warm-intro contact + the specific ask

• Contact: Patrick Walsh (Dogpatch Labs) — patrick@dogpatchlabs.com. This is a test of whether his state/semi-state network reaches daa (the card and contact register both rate this weak-to-moderate until confirmed — the package's strength is pull, not intro).
• The specific ask (from the drafted outreach): "a test of whether your state/semi-state network reaches daa Group Security & Resilience, for a counter-UAS coordination layer above their existing detection (object-tracking only — explicitly not passenger biometrics)." First sub-ask: who exactly — Group Security & Resilience vs Airport Operations vs daa Innovation vs the Dept of Transport aviation team. Fallback if no daa path: a Research-Ireland / EUDIS sovereign-hybrid-threat framing.
• Intro email (template, ready to adapt — from outreach-drafts.md ask #3):

  Subject: A counter-UAS coordination layer above Dublin Airport's detection — quick test?

  Hi Patrick — one of the three named asks from my note. We've built an EU-sovereign decision-intelligence platform ("Palantir for the EU, with sovereignty in the architecture"). The wedge for daa is a counter-UAS airspace operating picture + evidence spine that sits above their existing Dedrone detection — fusing detection + ADS-B + IAA geozones so the call between "the Dedrone alert fired" and "a safe, signed-off, multi-agency response" becomes one fused, human-gated, audit-evidenced decision that also produces the tamper-evident evidence pack the new €500 fixed-charge regime needs. Object-tracking in airspace only — explicitly not passenger biometrics (it's on our published Declined List). We replay a synthetic Dublin-airspace incursion end-to-end.

  Could you test whether your state/semi-state network reaches daa Group Security & Resilience (or the right Dept of Transport aviation contact)? Free discovery, no cost to them. Happy to walk you through the demo first so you're comfortable putting your name to it. Thank you — [Founder]

---

§22 — Open questions + Sources

Open questions (do not assert until resolved):

• Intro reality: does Patrick's / Dogpatch's network actually reach daa Group Security & Resilience, daa Innovation, or the Dept of Transport aviation team? Without a warm path, access_warmth stays at 2.
• Budget owner & route: who in daa owns the C-UAS / resilience software line, and is material spend OJEU/eTenders-procured?
• Incumbent posture: is Dedrone (now Axon) extending into the decision/coordination layer? If so, integration-vs-displacement strategy must adapt.
• Data-governance legitimacy: the legal basis governing sharing RF/operator-locating enforcement data into a third-party COP (IAA/ComReg/DPC) — confirms the "audited decision layer, not collector" framing.
• EU drone-wall capture: is there an Irish national thread of the European Drone Defence Initiative we can attach a sovereign-COP pilot to, and what 2026 EUDIS/EDF calls fit (most EDF 2026 calls close 29 Sep 2026; the multi-domain operations cloud call closed earlier, 28 Apr 2026)?
• Names/contacts: all stakeholder roles here are hypotheses — no individuals verified. Do not represent any named contact until confirmed.

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

• Dublin Airport drone disruptions (2023 six-in-six-weeks closures; 2024 seizure / north-runway suspension) — Irish Times 2023-02-03/04/06, 2024-03-24; RTÉ 2023-02-04.
• Dedrone deployment + ComReg-licensed non-kinetic counter-drone equipment operational — siliconrepublic.com; RTÉ 2023-09-07; Irish Examiner.
• IAA Wills Bros Ltd. investigation / Dublin Control Zone "Red Zone" / Dedrone detection / Just-Culture resolution — iaa.ie/media 2025-11-04; rte.ie 2025-11-04; irishexaminer.com (arid-41736396); thejournal.ie 2025-11; unmannedairspace.info; travelextra.ie.
• Aug-2025 National UAS Policy Framework (€500 fixed-charge offences, no-fly working group, U-space) + Regulation of Drones Bill 2025 (Bill 61/2025) — oireachtas.ie/bills/bill/2025/61; ts2.tech 2025; RTÉ 2025-10-01.
• European airport closures (Copenhagen ~4h / Munich twice in 24h, Sept–Oct 2025) + European Drone Defence Initiative / "drone wall" within the Defence Readiness Roadmap — cnn.com 2025-10-03/04; washingtontimes.com 2025-10-03; euronews.com 2025-11-20; dronelife.com 2025-10-17; en.wikipedia.org/wiki/2025_European_drone_sightings.
• EU AI Act Article 5 prohibitions applicable 2 February 2025 — official EU AI Act timeline.
• Comparator: prime-led C-UAS for high-value-site protection — Leonardo Falcon Shield + disclosed Italian Army/Air Force counter-UAS contracts + Leonardo/MBDA laser counter-drone programme (announced Dec 2024); Italian state forces operate tactical anti-drone systems around Vatican sites under a Public Security Inspectorate procurement (no specific Leonardo Vatican press disclosure verified).
• Internal: target card 03-gtm/target-packages/daa-iaa-aviation-cuas.md; formula 03-gtm/strategy-paper/formula-worked-examples.md (worked example C); discovery motion 03-gtm/discovery-playbook.md; outreach 03-gtm/strategy-paper/outreach-drafts.md (ask #3); legal 03-gtm/strategy-paper/legal-blockers-register.md (row daa #3); contacts 03-gtm/strategy-paper/contact-register.md (Patrick Walsh); AW depth pattern nexus-synergy-ei-sovereign-v2-aw-t04.md (W-16 C-UAS fusion + Decision Room).
• Flagged unverified: the specific daa Group Security & Resilience contact and whether Patrick's network reaches it; the exact OJEU threshold below which a scoped pilot runs without full tender; the IAA/ComReg/DPC legal basis for COP data-sharing.

---