Nexus Synergy Engagement Package — E03 · EDA / PESCO multinational maritime enablers (CSIP + UMS) — Irish front door via Defence Forces J2 / RTI Unit; MAHI BV (Belgium) consortium edge + contracting vehicle

STANDING BANNER — read first. (1) Status honesty: Nexus Synergy Ltd is pre-incorporation, pre-revenue, pre-pilot. EDA, PESCO, the CSIP and UMS projects, the Irish Defence Forces and MAHI BV are TARGETS / prospective partners, not customers. The ~178-surface UI gallery is a gallery, not traction. Nothing here is a deployment, a signed LOI, or a committed budget. (2) Anti-cookie-cutter: the §8 mockups are generated programmatically by _build/archetypes/gen_eda-pesco-csip-ums.py and filled with this buyer's real entities (CSC-1 Celtic Sea corridor, DAS KP-214, CSIP/UMS membership, EDF-2026 CSBI) — they are this buyer's screens, not a reused template. (3) All probabilities are [PRIOR] — subjective pre-pilot estimates for prioritisation, not forecasts; every factor cell carries a dated rationale and re-scores after the first real conversation.

---

§0 — Header + one-line thesis

EDA / PESCO (CSIP + UMS) — sovereign multinational seabed-infrastructure-protection decision layer.

Thesis. Ireland is already a participant in the two PESCO maritime enablers that matter for seabed-infrastructure protection — Critical Seabed Infrastructure Protection (CSIP) and Upgrade of Maritime Surveillance (UMS). Nexus Synergy is the sovereign, EU-only cross-Member-State decision / common-operating-picture (COP) layer that sits above the sensors and platforms those projects build — fusing AIS + EMODnet bathymetry + DAS acoustic + magnetometer + grid telemetry into one human-gated, fully-audited seabed-protection picture, with raw capture staying inside each Member State's tenancy and only derived products crossing borders under a Decision-Room tri-signature. Framed strictly as defensive civil-security seabed-infrastructure protection — never warfighting.

---

§1 — Entity snapshot (cited)

Important framing. EDA/PESCO is not a single buyer that signs a cheque. The realistic commercial path is: (a) a co-design / exercise contribution to a CSIP or UMS work-strand led by a participating Member State (Ireland), and/or (b) a module in an EDF-2026 consortium bidding the seabed-protection topic. The "purchase" is a consortium share, not a procurement order.

---

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

1. A live, repeated forcing function. The Baltic Sea saw a cluster of subsea-cable incidents: the Estlink 2 Finland–Estonia power cable was severed on 25 December 2024 (anchor-drag, "shadow-fleet" tanker), and two fibre cables (Lithuania–Sweden, Finland–Germany) were cut on 17–18 November 2024. NATO launched Baltic Sentry in January 2025 in response. [verified — npr.org, en.wikipedia.org/wiki/2024_Estlink_2_incident, twz.com]
2. The EU made it a policy obligation. The EU Action Plan on Cable Security was adopted 21 February 2025, followed by a completed risk assessment (October 2025), a Cable Security Toolbox, €347m of CEF Digital funding, and a list of 13 Cable Projects of European Interest over ~15 years. [verified — digital-strategy.ec.europa.eu, blue-economy-observatory.ec.europa.eu]
3. Ireland put it in its own first national strategy. Ireland's first-ever National Maritime Security Strategy (NMSS) was launched 25 February 2026: it commits to protecting subsea cables, gas and electricity interconnectors, and to exploring hosting or partnering a regional EU cable-monitoring hub in the North Atlantic. [verified — rte.ie 2026/0225, navaltoday.com 2026/02/26]
4. The capability gap is fusion + sovereign decision, not more sensors. CSIP/UMS build sensors and platforms (UUVs, surveillance integration). What is consistently missing is a vendor-neutral, sovereign cross-MS decision layer that fuses heterogeneous sensor outputs into one human-gated picture without raw national data leaving its jurisdiction. NATO's JEF Nordic Warden (AI vessel-risk assessment, activated Jan 2025) shows the demand for exactly this kind of fusion layer at a coalition scale. [verified — atlanticcouncil.org]

The pain in one line. Multiple Member States, multiple sensor estates, a live sabotage threat, and a hard EU mandate — but no sovereign, conformity-by-construction decision layer that fuses them while keeping each nation's raw capture inside its own border.

---

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

The use case: a CSIP/UMS co-design seabed-infrastructure-protection COP for the Celtic Sea / North-East Atlantic cable-and-pipeline corridor, fusing AIS + EMODnet bathymetry + IHO S-101 ENC + DAS acoustic (fibre-tap) + magnetometer (anchor-drag) + grid telemetry into one human-gated picture, with a 6-persona Decision Room seating a civil-society reviewer and a warrant authority inside the decision, cross-MS sharing of derived products only, and sealed attribution that cannot be revealed without dual-control + a warrant instrument.

The value: earlier, defensible detection of a vessel-proximity threat to a cable or pipeline; a single auditable picture across Member States; conformity-by-construction (FRIA + provenance ledger + transparency portal) for the EU AI Act and NIS2 conversation that surrounds critical-infrastructure tooling.

DECLINE-SAFE boundary (explicit and load-bearing): this is defensive civil-security seabed-infrastructure protection only. It is NOT warfighting; it is NOT predictive policing, biometric identification, emotion recognition, social scoring, untargeted scraping, or psychometric profiling. The picture is object/vessel-track-centric, human-gated, fully audited; raw stays sovereign per Member State and only derived products cross borders; flag-state attribution stays sealed pending a warrant. Decisions are exercise-tasking in the co-design phase, never live targeting.

---

§4 — Ontology (this buyer's domain entities + relationships)

CableSegment ──route_segment→ BathymetryTile           (EMODnet / GEBCO / S-101 ENC)
CableSegment ──parallel_to→ PipelineSegment            (gas / power interconnector)
CableSegment ──monitored_by→ SensorAsset {DAS, magnetometer, hydrophone}
SensorAsset  ──deploys→ SensorSignature {das_acoustic, em_magnetometer}
SensorSignature ──coincident_with→ VesselOfInterest    (AIS-dark / RF-dark loiter)
VesselOfInterest ──adjacency(km, min)→ CableSegment    (1.2 km / 27-min window)
SurveyAsset {NavalMPA, USV(MAHI), MCM-drone} ──tasked_to→ CableSegment   (exercise)
CodesignInstrument {CSIP, UMS} ──authorises→ SurveyAsset                 (PESCO Art-6)
CrossMSProduct ──derived_from→ SensorSignature ──shared_under→ TriSignature
Attribution ──sealed_by→ WarrantInstrument + DualControl

Entity resolution across Member-State sensor estates uses Fellegi–Sunter match weights (time-correlation, positional cross-track, spectral signature) so an Irish-deployed and a partner-deployed hydrophone observation resolve to one cross-MS event — mirroring the W-15 PESCO co-design worked example (W ≈ 12.1 > T_μ = 5.5). PROV-O records which MS sensor produced which observation.

---

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

Each Member State is its own tenant (org_id = app.current_org_id). The load-bearing safety property: no cross-MS share of raw capture — only derived products, and only once a Decision-Room tri-signature is recorded — enforced as a DB CHECK, not application logic.

SQL
45 lines
Copy
-- Per-segment cable/pipeline asset, scoped to the owning Member-State tenant.
CREATE TABLE synergy.cable_segment (
    id               uuid PRIMARY KEY DEFAULT gen_random_uuid(),
    org_id           uuid NOT NULL,                         -- RLS: app.current_org_id (owning MS)
    segment_uid      text NOT NULL,                         -- e.g. CSC-1 KP-214
    operator         text NOT NULL,                         -- NIS2 essential entity
    asset_kind       text NOT NULL CHECK (asset_kind IN ('cable','pipeline')),
    corridor         geography(LINESTRING,4326) NOT NULL,   -- route on the globe
    depth_m          int,
    pesco_instrument text NOT NULL CHECK (pesco_instrument IN ('CSIP','UMS')),
    civilian_view_ref text NOT NULL,                        -- NIS2 civ-view hash (channel-sever)
    unclos_regime    text NOT NULL DEFAULT 'continental_shelf',  -- UNCLOS Art 113
    UNIQUE (org_id, segment_uid)
);
ALTER TABLE synergy.cable_segment ENABLE ROW LEVEL SECURITY;
CREATE POLICY org_isolation ON synergy.cable_segment
    USING (org_id = current_setting('app.current_org_id')::uuid);

-- Cross-MS shared product; the sovereignty bound (raw stays home, derived crosses) lives here.
CREATE TABLE synergy.cross_ms_product (
    id                 uuid PRIMARY KEY DEFAULT gen_random_uuid(),
    org_id             uuid NOT NULL,
    cable_segment_id   uuid NOT NULL REFERENCES synergy.cable_segment(id),
    origin_ms          text NOT NULL,                       -- producing MS tenancy
    product_kind       text NOT NULL CHECK (product_kind IN
                         ('acoustic_raw','acoustic_derived','em_raw','em_derived','bathy_tile')),
    fs_link_weight     numeric(6,3),                        -- cross-MS Fellegi-Sunter W (~12.1)
    proportionality    numeric(4,3),                        -- N*P*L envelope (~0.85)
    tri_signoff_id     text,                                -- IE + partner + lead MS (3/3); NULL until signed
    warrant_instrument_id text,                             -- NULL unless attribution reveal sought
    shared_cross_ms_at timestamptz,                         -- NULL until tri-signed share
    flag_state_revealed_at timestamptz,                     -- NULL unless dual-control + warrant
    retain_until       date NOT NULL,                       -- 18mo DSR archival (EDRi-derived)
    prov_o             jsonb NOT NULL,
    -- LOAD-BEARING #1: no cross-MS share of raw capture; derived/bathy only, and only tri-signed.
    CHECK (shared_cross_ms_at IS NULL
           OR (product_kind IN ('acoustic_derived','em_derived','bathy_tile')
               AND tri_signoff_id IS NOT NULL)),
    -- LOAD-BEARING #2: no flag-state attribution reveal without BOTH dual-control AND a warrant.
    CHECK (flag_state_revealed_at IS NULL
           OR (tri_signoff_id IS NOT NULL AND warrant_instrument_id IS NOT NULL))
);
ALTER TABLE synergy.cross_ms_product ENABLE ROW LEVEL SECURITY;
CREATE POLICY org_isolation ON synergy.cross_ms_product
    USING (org_id = current_setting('app.current_org_id')::uuid);

The two CHECK invariants make the doctrine physically impossible to violate: a raw cross-MS share is rejected at the database, and an attribution reveal without dual-control + warrant is rejected at the database — independent of any UI or application bug.

---

§6 — Action-loop pseudocode (detect → enrich → triage → gate → task → execute → BDA → close)

Python
41 lines
Copy
def run_seabed_codesign(segment_uid, requesting_org):
    # 1. DETECT — AIS-dark / RF-dark loiter astride a cable+pipeline corridor.
    seg = cable_segment(segment_uid)                              # CSC-1 KP-214
    voi = detect_loiter(seg, radius_km=1.2, window_min=27)        # VOI RF-dark
    if voi is None:
        return Disposition.MONITOR

    # 2. ENRICH — fuse DAS acoustic tap + magnetometer EM anchor-drag (derived only).
    das = das_signature(seg, window_min=27)                      # tap-pattern
    em  = em_signature(seg)                                       # anchor-drag
    xms = fuse_cross_ms_events(seg, inputs="derived_only")        # raw never leaves origin MS
    if xms is None or xms.fs_link_weight < T_MU_TIER4_XMS:        # W < 5.5 -> no cross-MS event
        return Disposition.MONITOR

    # 3. TRIAGE — classify; reject benign explanations before escalation.
    cls = classify(das, em, voi)                                 # anchor_drag .87 vs trawl_snag .09
    if cls.benign_prob > 0.5:
        return Disposition.MONITOR                                # lawful fishing / transit

    # 4. GATE — Art-8-ECHR + PESCO-co-design proportionality; HUMAN sign-off required.
    P = proportionality(necessity=0.94, proportion=0.88, least_intrusive=0.79,
                        scope="exercise_codesign")               # P = 0.85
    decision = decision_room(personas=[
        "op_tasking","proportionality","edri_civil_society",
        "devils_advocate","subsea_expert","warrant_authority"])  # 6 personas
    if not decision.tri_signed():                                # IE + partner + lead MS (3/3)
        return Disposition.HOLD                                   # no share, no task

    # 5. TASK — exercise-task only; attribution stays SEALED.
    task = exercise_task(asset="NavalMPA_covert", note="no live targeting")
    seal_attribution(xms)                                        # reveal-under-warrant only

    # 6. EXECUTE — write-back through nexus-workflows (advisory in co-design).
    job = workflows.submit("monitor_subsea_acoustic", payload=task, dual_control=True)

    # 7. BDA — did the exercise-task validate the cross-MS fusion + sync-ladder?
    bda = assess(job, criteria=["xms_fusion_validated","degraded_comms_sync_ok"])

    # 8. CLOSE — record PROV-O chain; lodge derived product (18mo DSR retention).
    close_case(seg, xms, decision, bda, retain_months=18)
    return Disposition.CLOSED

---

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

YAML
34 lines
Copy
# nexus-workflows job: seabed_codesign_loop  (CSIP/UMS co-design; exercise-only)
name: seabed_codesign_loop
trigger: { on: das_or_em_anomaly, scope: "org=app.current_org_id" }
nodes:
  - id: detect_loiter
    run: nexus_synergy.subsea.detect_loiter        # AIS/RF-dark, 1.2km/27min
  - id: enrich_fuse
    needs: [detect_loiter]
    run: nexus_synergy.subsea.fuse_cross_ms         # DERIVED ONLY; raw stays per-MS
    params: { inputs: derived_only, fs_threshold: 5.5 }
  - id: triage_classify
    needs: [enrich_fuse]
    run: nexus_synergy.subsea.classify              # anchor_drag vs benign
  - id: HUMAN_GATE                                  # <-- BLOCKING node
    needs: [triage_classify]
    type: human_decision
    blocking: true
    quorum: 3                                       # IE + partner + lead MS tri-signature
    personas: [op_tasking, proportionality, edri_civil_society,
               devils_advocate, subsea_expert, warrant_authority]
    refuse_path: hold_and_log                       # dissent -> HOLD, no share/no task
  - id: task_exercise
    needs: [HUMAN_GATE]
    run: nexus_synergy.subsea.exercise_task         # exercise-tasking only, attribution SEALED
  - id: execute_writeback
    needs: [task_exercise]
    run: nexus_synergy.workflows.callback_post      # advisory write-back, dual-control
    params: { targets: [nis2_register, dcmnr_notify] }
  - id: bda_assess
    needs: [execute_writeback]
    run: nexus_synergy.subsea.assess
  - id: close_provo
    needs: [bda_assess]
    run: nexus_synergy.audit.close                  # PROV-O chain, 18mo DSR retention

---

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

Figure 8.1 — globe_rmp (PRIMARY). ShellLayout + TopBar (with RendererChip = CesiumJS, PccPill = CIPC) + ClassificationBanner (EU-RESTRICTED / TLP:AMBER) + LeftSidebar glyph rail + MapConsole rendering the CesiumJS under-water-tilt globe + a right-rail CONTACTS list with the ChatTerminal Decision-Room transcript + BottomStatusBar. Generated by gen_eda-pesco-csip-ums.py.

Figure — Recognised maritime picture (globe_rmp). Production-fidelity React surface (buildable); the faithful ASCII follows.

+--------------------------------------------------------------------------------------------------+
| Celtic Sea CSIP/UMS Co-design RMP - EDA/PESCO multinational enabler (CesiumJS-globe)             |
+-------------------------------------------------------------------+------------------------------+
|         . - '' - .       CELTIC SEA  (IE EEZ <-> approaches)      | CONTACTS (sorted: sub-sea)   |
|      /   o ----._  \   CSC-1 cable + parallel gas interconn.      | VOI vessel  RF-DARK          |
|     |  [!] AIS dark |   EMODnet bathy -1100m :: IHO S-101 ENC     |   AIS gaps, loiter 27m       |
|     |   VOI contact  |  VOI loiter (AIS gaps, RF-dark)            |   1.2km of CSC-1 KP-214      |
|     |  loiter 27 min |   astride cable + pipeline corridor        | DAS acoustic event           |
|      \ __X DAS tap __/   DAS acoustic tap-pattern @ KP-214        |   KP-214  tap-pattern        |
|       \ '. _____ .'/    magnetometer EM anchor-drag (consistent)  |   class: anchor_drag .87     |
|         ' - x__ - '     IE-leg LE-WB-NisBan / DE-leg Type-212     | EM magnetometer              |
|   Camera {lat 51.5 lon -7.0 alt 700km} CesiumJS-globe  L4         |   anchor-drag consistent     |
|   Concurrence: AIS-dark + DAS tap + EM drag, 1.2km/27min          | [#] CSIP/UMS co-design       |
|   -> ANOMALY 0.85  ::  HUMAN GATE :: attribution SEALED           |   IT-lead / EL-lead grid     |
|                                                                   | Share: derived ONLY          |
|                                                                   |   raw stays per-MS sov       |
|                                                                   | gate: NOC alert + MPA        |
|                                                                   |   exercise-task (no live)    |
|                                                                   | Attribution: SEALED          |
|                                                                   |   reveal-under-warrant       |
+-------------------------------------------------------------------+------------------------------+
| EMODnet bathy + IHO S-101 + DAS + magnetometer + AIS :: PESCO co-design, exercise-tasking only   |
+--------------------------------------------------------------------------------------------------+

Figure 8.2 — command_dashboard (SECONDARY). The multinational-programme readiness board: ShellLayout + KPI tiles (CSIP / UMS / EDF-2026 CSBI) + a LIVE ALERT FEED carrying the dated mandate timeline and the decline-safe doctrine. Generated by the same script.

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

+--------------------------------------------------------------------------------------------------+
| CSIP/UMS Multinational Programme Readiness - EDA/PESCO enabler (command_dashboard)               |
+--------------------------------------------------------------------------------------------------+
| CSIP  (IT-lead, 2023-35)       | UMS  (EL-lead)                 | EDF-2026 CSBI topic            |
| Ireland: FULL participant      | Ireland participating          | consortium >=3 MS              |
| since Jul 2024  6+IE MS        | since 2018      7 MS           | closes 29 Sep 2026             |
+--------------------------------------------------------------------------------------------------+
| LIVE ALERT FEED                                                                                  |
|  21 Feb 2025  EU Action Plan on Cable Security adopted (EUR347m CEF Digital)                     |
|  25 Feb 2026  Ireland NMSS: explore EU cable-monitoring hub, North Atlantic                      |
|  co-design  cross-MS hydrophone fusion W=12.1 > T_mu=5.5 (Fellegi-Sunter)                        |
|  decision   6-persona Decision Room incl. EDRi civil-society + warrant auth                      |
|  sharing    raw stays per-MS sovereign; derived products tri-signed only                         |
|  gate       exercise-tasking pre-authorised; NO live targeting; SEALED attr                      |
|  write-back nexus-workflows job -> NIS2 register + DCMNR notify (advisory)                       |
|  decline    civil-security seabed-infra protection; NOT warfighting                              |
+--------------------------------------------------------------------------------------------------+

(Bespoke SVG of the primary screen: _build/figures/eda-pesco-csip-ums/uc-globe_rmp.svg — same globe_rmp archetype, real component names.)

---

§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)

Click-path: Analyst opens MapConsole (CesiumJS, under-water tilt) → AIS-dark VOI contact raises a red pulse astride the CSC-1 / pipeline corridor → click the VOI in the CONTACTS rail → the DAS tap-pattern (KP-214) and EM anchor-drag correlate into one cross-MS event (Fellegi–Sunter W ≈ 12.1) → the anomaly score (0.85) and proportionality envelope (N .94 · P .88 · L .79) populate → the Decision Room opens inside ChatTerminal with 6 personas → the analyst reads the EDRi dissent (derived-only sharing) and the warrant authority verdict (attribution SEALED) → /dual-control sign (2/2) unlocks /execute → exercise-task → the write-back fires a nexus-workflows job; the BottomStatusBar shows the civ NIS2 alert ⊥ CISE T4 envelope channel-sever.

MapConsole(VOI red pulse) ──▶ CONTACTS(select VOI) ──▶ fuse DAS+EM (W=12.1)
        │                                                      │
        ▼                                                      ▼
  anomaly 0.85 + N/P/L envelope ──▶ ChatTerminal Decision Room (6 personas)
                                            │
                  EDRi dissent ──▶ derived-only │ warrant auth ──▶ SEALED
                                            ▼
            /dual-control sign (2/2) ──▶ /execute exercise-task ──▶ nexus-workflows
                                            ▼
                       write-back (NIS2 register + DCMNR notify) ──▶ PROV-O close

---

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

Scenario: A CSIP/UMS co-design exercise in the Celtic Sea cable-and-pipeline corridor. A DAS tap-pattern on CSC-1 (KP-214) + a magnetometer anchor-drag + a UMS-surveillance RF-dark vessel loitering 1.2 km / 27 min. The gate question: escalate to an exercise-task and how much may be shared cross-MS and attributed.

▣ EU-RESTRICTED · TLP:AMBER · PESCO CO-DESIGN (exercise) ▣

OP-TASKING [L4]            DAS tap + EM anchor-drag + UMS RF-dark adjacency,
                          1.2 km / 27 min. Recommend exercise-task: vector
                          Naval MPA covert; alert operator NOC.

PROPORTIONALITY [L4]      Civilian-only acoustic loses ~70% attribution power.
                          Envelope-strict: N 0.94 · P 0.88 · L 0.79 -> P = 0.85.
                          PESCO Art-6 co-design proportionality satisfied;
                          exercise-context, no live target.

EDRi (civil-society) [L4] DISSENT on default sharing. Cross-MS-DSR minimum-
                          necessary: acoustic shared as DERIVED-ATTRIBUTION only
                          (no raw IQ); raw stays in the originating MS tenancy;
                          18-month retention per DSR archival. Channel-sever to
                          the operator NOC: "anomaly, re-route" — no PII, no
                          SIGINT detail.  <-- materially changes the recommendation

DEVIL'S ADVOCATE [L4]     Counter: anchor-drag could be a lawful fishing vessel.
                          Do NOT reveal flag-state on acoustic + EM alone. And
                          cross-MS sensor-fusion at L4 risks a sovereignty
                          paradox — confirm the raw-stays-home protocol.

SUBSEA EXPERT [L4]        Protocol confirmed: raw stays sovereign, only derived
                          crosses, gated by tri-signature. Tap-pattern + anchor-
                          drag over a parallel gas pipeline at -1100 m is not
                          benign loiter; consistent with the post-2022 Baltic
                          profile. ObservationLevel = Direct.

WARRANT AUTHORITY [L4]    VERDICT: flag-state attribution stays SEALED. Reveal
                          requires 2/2 dual-control (CIPC-dir + mar-SIG-sup) AND
                          a warrant instrument. PESCO/CSIP co-design instrument
                          signatures on file for all participating MS; Defence
                          Act 1954 §6 (IE) basis confirmed for the exercise.
                          GATE: ACCEPT exercise-task at P=0.85, tri-signed.
                          Attribution: AWAIT.

[ /dual-control sign — IE-J2 ]  [ /dual-control sign — partner ]
[ /dual-control sign — lead-MS ]  [ /execute -> exercise-task NOC + MPA ]

Decision-changing dissent: without the EDRi persona's intervention the default would have been cross-MS raw-IQ sharing, exposing each MS to a cross-jurisdictional data-protection exposure the co-design instrument explicitly bounds. The recommendation was narrowed to derived-attribution-only, then tri-signed at P = 0.85, with attribution sealed pending a warrant.

---

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

Write-back. On /execute, a nexus-workflows job (monitor_subsea_acoustic) posts an advisory task to (a) the NIS2 register (operator notified of a cable-segment anomaly) and (b) a DCMNR notify (Department with marine remit). In co-design, the write-back is exercise-tasking — no live asset is committed.

BDA (loop close). The exercise validates two things the co-design phase exists to prove: the cross-MS Fellegi–Sunter fusion resolved Irish + partner sensor events into one event (W ≈ 12.1 > T_μ = 5.5), and the hydrophone-array-as-L2-gateway sync-ladder held under emulated DEGRADED-comms (EMCON / Galileo-PRS). Failures (e.g. a partner hydrophone array still AS-PROPOSED) are surfaced as explicit Phase-3 dependencies, not hidden.

PROV-O chain. wasDerivedFrom: cross-MS derived product ← (DAS signature ⊕ EM signature ⊕ VOI track); wasAttributedTo: each observation → the specific MS sensor that generated it; wasAssociatedWith: the exercise-task → the 6-persona Decision Room + the 3/3 tri-signature; wasGeneratedBy: the seabed_codesign_loop workflow run. The chain is merkle-anchored across the CIV/T4 channel-sever boundary.

Deltas-only regulatory traceback. Only what differs from the §4.0 defaults: AI Act — high-risk critical-infrastructure context ⇒ FRIA on file; no Article-5 prohibited practice (no biometric, no social scoring). GDPR/DSR — derived-only cross-MS sharing, 18-month retention, EU-hosted. NIS2 — cable operator is an essential entity; Art-23 incident register updated. UNCLOS Art 113 — continental-shelf regime recorded per segment.

---

§12 — Buyer & stakeholders

---

§13 — Competition / incumbency + comparator (cited)

White space: a sovereign, EU-only, conformity-by-construction cross-MS decision layer that keeps each nation's raw capture inside its border. The primes build sensors and platforms; nobody owns the neutral decision/COP seam between Member States.

---

§14 — Readiness (honest, pre-pilot)

Reuse (real): the globe_rmp seabed surface, the DAS/EM channel-sever pattern, the 6-persona Decision Room (incl. civil-society + warrant authority), the cross-MS derived-only CHECK invariant, and the seabed_codesign_loop workflow are all already specified in the UC-55 / W-15 worked examples and the archetype library. The AI Provider Router (sovereign-EU model routing) and the FRIA / provenance-ledger / transparency-portal conformity components exist as architecture.

Real gaps (honest): (1) no live MS sensor data — DAS/magnetometer/hydrophone feeds are partner-supplied and exercise-only; (2) the cross-MS sync-ladder under DEGRADED comms is AS-DESIGNED, not field-proven; (3) L4 air-gap / EU-SECRET accreditation is unbuilt and would gate any classified strand; (4) the MAHI data-contract spike (open-API / track schema) is unscoped; (5) no EDA/PESCO contact and no consortium yet. This is a co-design / discovery opportunity, not a near-term deployment.

---

§15 — ENGAGEMENT PLAYBOOK

60-min discovery agenda (adapted): 0–5 frame + decline-safe statement; 5–20 "walk me through a cable-anomaly incident from detect to close — how many systems, who decides, how do you share across MS?"; 20–35 lawful basis + AI-Act/NIS2 scope + where does the data and model run (sovereignty); 35–45 sponsor + budget + which vehicle (EUDIS/EDF/CSIP work-strand); 45–55 map their loop onto detect→enrich→triage→gate→task→execute→assess→close; 55–60 reflect pains + agree the demo date. Bring no slides.

1-page pilot/co-design proposal (filled): Title — "Celtic Sea CSIP/UMS sovereign cross-MS seabed-protection COP — co-design exercise." Sponsor — IE Defence Forces J2/RTI (with MAHI prime). The one thing we prove — "we fuse Irish + partner DAS/AIS/EM into one cross-MS event (W>T_μ) and reach a human-gated, derived-only-shared, sealed-attribution decision, with raw never leaving the originating MS." Scope IN — globe_rmp + Decision Room + cross-MS CHECK + workflow write-back. OUT — live tasking, classified strands, any biometric/predictive (Declined-List excluded). Data — representative/exercise DAS/AIS/EM, EU-hosted. Success criteria — cross-MS fusion validated; sync-ladder holds under DEGRADED-comms emulation; 6-persona gate audit complete (baselines set week 1). Timeline — 8–12 wks. Commercials — €0 to sponsor if grant-funded (EUDIS/EDF); production band Tier-1 €120–240k/yr to Tier-3 €2.4–4.8m/yr only if asked. After — MOU + EDF-2026 consortium intent.

LOI checklist (key items): parties (MAHI vehicle pre-incorp / Founder in own name under CA 2014 s.45); non-binding statement of intent; scope from the proposal; success criteria referenced; named sponsor; indicative timeline; "to be scoped under EDF-2026 / PESCO co-design"; conditions (funding award, security accreditation, data-sharing agreement); binding vs non-binding stated; mutual NDA; Irish governing law; Declined-List affirmation; signatures; ⚖️ solicitor review confirmed.

Warm-intro email (adapted draft #2 → MAHI): Subject: "CSIP/UMS — an all-EU Belgian+Irish seabed-protection co-design play." Body: MAHI owns the vessel/sensor edge; Nexus Synergy is the sovereign cross-MS decision/COP layer above it — derived-only cross-MS sharing, human-gated, sealed attribution. Ireland is already in CSIP (full since Jul 2024) and UMS (since 2018); the EDF-2026 CSBI topic (closes 29 Sep 2026) rewards exactly an all-EU consortium. Two asks: (1) a track-schema/open-API technical session; (2) MAHI as the contracting prime for a first co-design exercise.

---

§16 — PM / timeline

                 2026                          2027                  2028
        Q3      Q4      Q1      Q2      Q3      Q4      Q1      Q2
S1 contact/disc  [##]
S2 free discovery   [###]
S3 demo                [##]
S4 pilot/co-design       [#####]
S5 LOI/MOU                     [##]                                       <- Patrick-check
EDF-2026 bid window  [====29 Sep 2026 close====]                          <- HARD external clock
S6 consortium/contract              [#######################]
   (gated by EDF award + MAHI prime + Stamp-4 / partner vehicle)

Milestones: M1 MAHI session + DEC/RTI route (Q3-26); M2 discovery PASS (Q4-26); M3 demo accept (Q1-27); M4 co-design exercise report (Q2-27); M5 MOU (Q2-27); M6 EDF/PESCO award (2028+). Critical path: the Stamp-1G / partner-vehicle gate — a PAID co-design contract or EDF consortium share cannot be signed by the solo founder; MAHI as contracting prime (V: 0.10→0.75) is the gating dependency, alongside the EDF-2026 29 Sep 2026 external clock for the non-dilutive route.

RACI:

---

§17 — Funding / procurement vehicle

• EDF-2026 — €1bn WP2026; topic EDF-2026-LS-RA-SI-UWW-CSBI "Layered critical seabed infrastructure protection"; calls close 29 September 2026; consortia of ≥3 entities in ≥3 Member States (non-dilutive). [verified]
• EUDIS (EU Defence Innovation Scheme) — SME calls up to €4M research / €6M development; non-thematic SME tracks. [verified]
• PESCO co-design instruments — CSIP (Italy-led) / UMS (Greece-led) Member-State-led work-strands Ireland already participates in. [verified]
• EU Cable Security — €347m CEF Digital + 13 Cable Projects of European Interest (adjacent civil funding). [verified]
• Blocked: NATO DIANA — Ireland is non-NATO; ineligible. Use EU vehicles only. [verified — diana.nato.int]

---

§18 — TWO-STAGE FORMULA SCORECARD

Stage-1 {mandate_pull, access_warmth, demonstrability, decline_safety, white_space, cycle_speed, pillar_fit} — all [PRIOR]:

S1 = 3.64 → P_LOI = 0.55/(1+exp(−1.15·(3.64−2.6))) = 0.422 (≈ 42% [PRIOR]). Score100 = S1·20 = 72.8.

Stage-2 {contractability, funding_to_pay, procurement_clarity, incumbency_displacement, time_to_value, reference_leverage} — all [PRIOR]:

S2 = 2.88 → P_raw = 0.70/(1+exp(−1.1·(2.88−2.8))) = 0.365 [PRIOR].

Legal gate G = V·T, with t_resolve = 14 mo, H_conv = 30, so T = 0.533:

Reconciliation: board_anchor is [PRIOR-derive], value high. Score100 = 72.8 lands in the high band, consistent with the other very-strong-mandate/slow-cycle maritime rows (e.g. SFPA 71.6, daa 71.6, naval-MAHI 66.4). The decisive lever, exactly as in the MAHI maritime worked example, is MAHI lifting the legal gate (V 0.10→0.75) — it moves P(Contract|LOI) from ~1.9% to ~14.6%; it does not change Stage-1.

---

§19 — Commercial

Requirements: EU-hosted sovereign infra; L4/EU-SECRET accreditation for any classified strand; MAHI (or partner) as contracting prime; DPA + cross-MS data-sharing agreement; FRIA on file. Cost advantage from open-source substrate + sovereign HPC + shared conformity file + no forward-deployed-engineer dependency.

---

§20 — Legal blockers

---

§21 — Warm-intro contact + the specific ask

• Pieter-Jan Note (MAHI CEO) — warm, founder-to-founder. Ask: (1) a track-schema/open-API technical session to scope the cross-MS data contract; (2) MAHI to act as contracting prime for a first CSIP/UMS co-design exercise and the EDF-2026 CSBI consortium — explicitly to lift the legal gate (V 0.10→0.75). [verified person; email not public]
• Patrick Walsh (Dogpatch) — warm. Ask: an introduction into the Defence Forces RTI Unit via the DEC for a free discovery on the sovereign cross-MS seabed-protection decision-layer gap (Ireland already in CSIP + UMS). [verified — contact-register]

---

§22 — Open questions + consolidated Sources

Open questions: (1) Is there an Irish-led CSIP/UMS work-strand Nexus Synergy could contribute a module to, or is EDF-2026 the only near-term vehicle? (2) Named EDA CapTech-Maritime / PESCO project-office contact [TBD]. (3) MAHI's appetite + capacity to prime an EDF-2026 bid [unverified — confirm in the session]. (4) L4/EU-SECRET accreditation cost + timeline [TBD]. (5) The exact written terms of Patrick's conditional support [unverified]. (6) Whether a CSIP/UMS exercise can run on representative (non-classified) data to stay inside the free-discovery model [TBD].

Sources (dated 2026-06-05):

• PESCO CSIP project page — Italy-led, 5th wave (May 2023), 2023–2035, members IT/FR/DE/PT/ES/SE, observers BG/FI: pesco.europa.eu [verified]
• Ireland joined CSIP (full, Jul 2024) + the two PESCO projects: thejournal.ie ; rte.ie [verified]
• PESCO UMS project — Greece-led; Ireland participating since 2018 (one of Ireland's two original PESCO projects; EL/BG/ES/HR/IT/CY/IE): pesco.europa.eu ; gov.ie [verified]
• EDF 2026 — €1bn, closes 29 Sep 2026, topic EDF-2026-LS-RA-SI-UWW-CSBI "Layered critical seabed infrastructure protection", ≥3 MS consortia: defence-industry-space.ec.europa.eu ; hezelburcht.com [verified]
• EU Action Plan on Cable Security (21 Feb 2025) + Toolbox + €347m + 13 Cable Projects of European Interest: digital-strategy.ec.europa.eu ; eur-lex.europa.eu [verified]
• Ireland NMSS (first-ever, 25 Feb 2026; subsea-cable protection; explore EU cable-monitoring hub, North Atlantic): rte.ie ; navaltoday.com [verified] (NMSS vessel-count claim deliberately NOT relied upon.)
• Baltic cable incidents (Estlink 2, 25 Dec 2024; Nov-2024 fibre cuts) + NATO Baltic Sentry (Jan 2025) + Nordic Warden: en.wikipedia.org ; twz.com ; atlanticcouncil.org [verified]
• SEACURE (Thales-led EDF, demo at sea by 2028): thalesgroup.com [verified]
• EDA CapTech Maritime: eda.europa.eu [verified]
• Internal: discovery-playbook.md, formula-worked-examples.md (LOI formula), legal-blockers-register.md, contact-register.md, outreach-drafts.md; depth pattern mirrored from UC-55 / W-15 (PESCO co-design) in nexus-synergy-ei-sovereign-v2-aw-t03.md.

---