STANDING BANNER — read before using this package. (1) Status honesty. Nexus Synergy Ltd is pre-incorporation, pre-revenue, pre-pilot. The Netherlands Coastguard / Royal Netherlands Navy / COMMIT is a TARGET, not a customer; nothing here is a deployment, a contract, or traction. The ~178-surface UI gallery is a gallery, not a fielded system. MAHI and Damen are ecosystem relationships, not signed partners. (2) Anti-cookie-cutter. The §8 mockups are generated programmatically for this buyer (Dutch North Sea, Borssele wind cluster, NorNed/TenneT, JRCC Den Helder, A-18 AUV + Inspector-125M USV, Dash-8 MSA) and look like this buyer's screens — not a reused shell. (3) Every probability is [PRIOR]. All scores are subjective pre-pilot estimates with dated rationales, re-scored after each real conversation. Framing is strictly CIVIL-SECURITY / SAR / critical-infrastructure-resilience / MDA, never warfighting, mine-clearance targeting, or migrant biometric profiling.

§0 — Header + one-line thesis

Nexus Synergy as the sovereign, human-gated decision/operating-picture layer that turns the Netherlands Coastguard's new Maritime Operations Centre at Den Helder — and the surge of uncrewed-systems sensing arriving from the Royal Netherlands Navy / rMCM toolbox and the Damen-led autonomy programme — into one auditable autonomous coast-guard COP fusing AIS + Sat-AIS + Dash-8 maritime-surveillance radar/EO + USV/AUV sonar + TenneT grid telemetry into a single anomaly-and-SAR picture over the Dutch North Sea's wind clusters, interconnectors and fibre routes, with a 5-persona Decision Room (including a civil-society reviewer) seated inside every escalation.

One line: the autonomous vessels sense the North Sea; Nexus Synergy decides — lawfully, sovereignly, and on the record, with the Kustwacht's civil hand on the gate.

§1 — Entity snapshot (cited)

Netherlands Coastguard (Kustwacht / KCG) — a civilian, multi-agency coast guard under a cooperation between six ministries (the civil-authority character is what makes procurement easier than a pure-military buy). The Coastguard Centre at Den Helder is the Netherlands Joint Rescue Coordination Centre (JRCC Den Helder, call "DEN HELDER RESCUE"), coordinating both sea rescue (MRCC) and air rescue (ARCC), with a front-office / back-office split into the partner authorities' databases. [verified] (kustwacht.nl; noordzeeloket.nl).
Maritime Operations Centre (MOC) + Fallback/Training/Test (FTT), Den Helder — for the first time the Coastguard gets its own purpose-built HQ; designed by cepezed, tendered by the Rijksvastgoedbedrijf (Central Government Real Estate Agency), completion 2026; "new ICT facilities … the Coastguard will have an even clearer picture of the North Sea." [verified] (cepezed.nl; kustwacht.nl).
Maritime-surveillance edge — since 2022 the KCG operates two Dash-8 Maritime Surveillance Aircraft under a long-term partnership with PAL Aerospace; the Dash-8 sensors increased the North Sea picture by 80%. [verified] (palaerospace.com).
Royal Netherlands Navy (RNLN) / COMMIT (Materiel & IT Command, ex-DMO) Maritime Systems Division — the Dutch MoD's maritime engineering + procurement office; leads a 12 m ASW USV ("Dutch Naval Design" team: Damen Naval + MARIN + DEMCON; prototype aspiration end-2025) and two Multifunction Support Ships to deploy UUVs and intercept/escort hostile vessels for critical-underwater-infrastructure protection. [verified] (navalnews.com; en.wikipedia.org Future-of-RNLN; navylookout.com).
Nov-2024 maritime-autonomy trials — a consortium of AVR Maritime, Damen Naval, DEMCON, Fugro, MARIN, RH Marine, SkyDec ran sensor/situational-awareness trials (off Scheveningen) with the Dutch MoD to feed autonomous decision-making fused with remote-operator inputs. [verified] (seasec.org).
Belgian-Dutch rMCM programme — 12 City-class MCM vessels (6 BE + 6 NL); first NL hull Vlissingen received March 2026; the "Toolbox" = Inspector-125M USVs, A-18 AUVs (UMISAS-120 sonar), T-18 towed sonar, UMS Skeldar V-200 UAV; toolbox operational qualification began early 2025. [verified] (naval-technology.com; thedefensepost.com 2026-03; navalnews.com).
MAHI (Mechelen, Belgium) — maritime-autonomy company; Alpha-8 USV unveiled 2 March 2026; open/modular MAHI Sense autonomy stack; flown at NATO REPMUS 2025; CEO Pieter-Jan Note is the founder's direct warm-intro counterpart and the contracting gate-resolver. [verified] (tectonicdefense.com; maritime-executive.com).
Nexus Synergy Ltd — pre-incorporation Irish EU-sovereign decision-intelligence / COP platform; the sovereign decision layer above the autonomous-vessel edge. [status: pre-incorporation].

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

The Netherlands has an acute, named, dated, funded North-Sea-infrastructure-protection gap, and a fusion/decision layer over an arriving autonomy surge is precisely the missing piece:

A funded national programme with a permanent Defence task. The North Sea Infrastructure Protection Programme (PBNI — Programma Bescherming Noordzee Infrastructuur), established 2023, IenW-led with Defence, EZK, JenV, BZ (six entities), carries €16.8 M (2024) + €24.6 M (2025); the Ministry of Defence has been given a permanent task to protect North Sea infrastructure and to "increase Situational Awareness and Understanding." Minister Harbers submitted the programme letter to Parliament 11 June 2024 (debate 30 May 2024). [verified] (nedzero.nl; noordzeeloket.nl PBNI; both accessed 2026-06-05).
The forcing function is live and political. After the Nord Stream sabotage and the November 2024 Baltic cable-damage incidents, "protection of North Sea infrastructure is high on the cabinet's agenda"; the PBNI funds tracking systems on drilling rigs and wind farms, enhanced satellite capacity, small crewed monitoring vessels, scaled sensor capacity, and a response system. [verified] (nedzero.nl; hcss.nl Dec-2025 subsea-resilience report).
A sensing surge with no fused civil brain. The Dash-8 MSA (+80% picture), the rMCM A-18/Inspector toolbox (qualification from early 2025), the Damen-led 12 m USV (prototype end-2025), and the Nov-2024 autonomy trials all mean a flood of new uncrewed/sensor data is arriving — but multi-source anomaly fusion + an auditable human-gated escalation across the KCG's six partner authorities (and out to TenneT / cable operators) is not a coherent product. [verified] (navalnews.com; seasec.org).
A modernisation moment with the ICT door open. The KCG's new MOC (2026) explicitly promises "new ICT facilities" and "an even clearer picture of the North Sea" — a once-in-a-generation window to add the decision-intelligence layer the building was justified by. [verified] (kustwacht.nl; cepezed.nl).

The detect→fuse→triage→gate→task→assess→close chain is broken at fuse/triage/gate: today the KCG detects (rich sensors, Dash-8, AIS) and acts (radio/CAD/phone) but multi-source anomaly fusion and an auditable human-gated escalation across agencies — for both infrastructure-anomaly and SAR — is manual. That gap is the wedge.

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

Use case. A sovereign, human-gated autonomous coast-guard COP for the Dutch North Sea: fuse AIS + Sat-AIS (Copernicus/EMSA) + Dash-8 MSA radar/EO + USV/AUV sonar (rMCM toolbox / Damen autonomy / MAHI Sense) + TenneT grid telemetry + IHO S-101 ENC + EMODnet bathymetry into one picture over the Borssele / Hollandse Kust wind clusters, the NorNed / COBRAcable / BritNed interconnectors and the fibre routes; surface a single concurrence-scored anomaly (or SAR distress); and seat a 5-persona Decision Room (op-coordination, proportionality, civil-society reviewer, devil's advocate, maritime domain expert) inside every escalation before any KCG VHF challenge, SAR launch, or scheduled inspection is tasked.

Value.

Faster, defensible detection of seabed/cable interference (loiter + AIS-gap + sonar-scour concurrence) and earlier SAR triage, instead of single-sensor false-positive noise — directly serving the PBNI "situational awareness + response system" mandate.
One auditable picture across the KCG's six partner authorities (plus TenneT / cable operators) with CISE-aligned sharing (EU CISE operational since 1 July 2024), replacing manual cross-agency coordination.
Conformity-by-construction (FRIA, PROV-O provenance ledger, transparency portal) for an EU AI Act / NIS2 / CER environment.
Sovereign AI at the model boundary — EU-incorporated LLMs (EuroLLM/Mistral) or on-device, never US-hyperscaler model calls for restricted data.

DECLINE-SAFE perimeter (explicit). This package is resilience, safety and coordination only. It is NOT and will never be: predictive policing; real-time or post-hoc biometric identification of crews or migrants; emotion recognition; social scoring; untargeted scraping; psychometric profiling; weapons cueing; or mine-neutralisation / clearance targeting. Vessel telemetry, seabed sonar and SAR distress are object/asset/safety data, not person-profiling data. Any drift toward identity-targeting requires a separate lawful basis and is gated behind the proportionality + civil-society personas; the published Declined List is affirmed in every MOU. The KCG's civil character keeps this slice naturally clean.

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

Entities.

Vessel — MMSI, flag-state, IMO, owner-chain, declared cargo/transit.
AIS-Contact — per-ping LatLon + heading + speed + AIS-gap-duration + receive-station.
SatAIS-Contact — Copernicus/EMSA pass-geometry + confidence (cross-check of self-report).
Dash8-Detection — MSA radar/EO track or imagery fix (PAL Aerospace sensor); confidence; classification.
USV-Sonar-Event / AUV-Sonar-Event — sensor (rMCM A-18 / Inspector-125M / Damen autonomy / MAHI Sense); seabed-object centroid; object length; scour width; classification (anchor_drag / trawl_snag / debris / unknown).
Cable-Segment / Pipeline-Segment — corridor id (NorNed), KP marker, operator (TenneT), criticality weight.
WindCluster — Borssele / Hollandse Kust array; turbine/cable footprint.
GridTelemetry — TenneT interconnector power-flow (MW), nominal vs dip.
ProtectionZone — 1 nm polygon around a cable/pipeline/wind asset.
SAR-Incident — distress fix, PIW/vessel-in-distress, JRCC case id, on-scene assets.
Asset — Zr.Ms. patrol vessel, Dash-8 MSA, A-18 AUV, Inspector-125M USV, KNRM lifeboat, NH90/rescue helo.
DecisionGate — proportionality score, persona transcript, dual-control signatures.

Relationships. Vessel —ais_telemetry→ AIS-Contact; AIS-Contact —contradicted_by→ {SatAIS-Contact, Dash8-Detection, USV-Sonar-Event}; AIS-Contact —loiters_in→ ProtectionZone; USV-Sonar-Event —proximal_to→ Cable-Segment; Cable-Segment —connected_to→ {WindCluster, GridTelemetry}; SAR-Incident —coordinated_by→ JRCC; DecisionGate —authorises→ Asset (task); Asset —surveys→ USV-Sonar-Event / Asset —rescues→ SAR-Incident (BDA loop-back).

The hard entity-resolution problem: deciding whether a fresh seabed scour at KP-31 is attributable to the loitering AIS contact — a multi-source concurrence (loiter + AIS-gap + sonar + Dash-8 EO) scored before any escalation, never an identity claim about a person.

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

Tables are org_id-scoped for the app.current_org_id RLS predicate (per-tenant: Netherlands Coastguard, RNLN/COMMIT, TenneT/cable operator). The load-bearing safety property is the civil-resilience→intrusive-action boundary: a contact cannot record an inspection/boarding authorisation, nor an asset tasking beyond a voice challenge, without a recorded human dual-control gate, enforced as a DB CHECK, not application logic.


SQL
47 lines
-- AUV/USV sonar event from an uncrewed asset (rMCM A-18 / Inspector-125M / Damen / MAHI Sense), org-scoped + RLS.
CREATE TABLE synergy.auv_sonar_event (
    id              uuid PRIMARY KEY DEFAULT gen_random_uuid(),
    org_id          uuid NOT NULL,                       -- RLS: app.current_org_id
    asset_id        text NOT NULL,                       -- 'RMCM-A18-2' | 'INSPECTOR-125M-1' | 'MAHI-ALPHA8-01'
    event_at        timestamptz NOT NULL,                -- 14:11:06Z
    cable_segment   text,                                -- 'NorNed' (KP-31)
    object_len_m    numeric(6,1),                        -- 1.8
    scour_width_m   numeric(6,1),                        -- 1.8
    classification  text NOT NULL
                    CHECK (classification IN ('anchor_drag','trawl_snag','debris','biologic','unknown')),
    obs_level       text NOT NULL DEFAULT 'inferred'
                    CHECK (obs_level IN ('asserted','reported','inferred','direct','confirmed')),
    prov_o          jsonb NOT NULL                       -- RmcmToolboxIngest-v1.0 / MahiSenseIngest attribution
);
ALTER TABLE synergy.auv_sonar_event ENABLE ROW LEVEL SECURITY;
CREATE POLICY org_isolation ON synergy.auv_sonar_event
    USING (org_id = current_setting('app.current_org_id')::uuid);

-- Coast-guard contact = the cross-agency MDA/SAR alert entity; the resilience->action boundary lives here.
CREATE TABLE synergy.kcg_contact (
    id                  uuid PRIMARY KEY DEFAULT gen_random_uuid(),
    org_id              uuid NOT NULL,
    cable_segment       text,                            -- 'NorNed' (NULL for a pure SAR case)
    sar_case_id         text,                            -- JRCC Den Helder case ref (NULL for an MDA-only case)
    vessel_mmsi         text,                            -- anonymised in the shared picture
    flag_state          text,                            -- 'LBR'
    sonar_event_id      uuid REFERENCES synergy.auv_sonar_event(id),
    dash8_confirmed     boolean NOT NULL DEFAULT false,  -- Dash-8 MSA EO pass corroboration
    ais_gap_minutes     numeric(6,1) NOT NULL DEFAULT 0, -- 18.0
    loiter_hours        numeric(6,1) NOT NULL DEFAULT 0, -- 9.0 inside the 1nm zone
    in_protection_zone  boolean NOT NULL DEFAULT false,  -- 1nm polygon test
    grid_dip_observed   boolean NOT NULL DEFAULT false,  -- TenneT telemetry dip y/n
    anomaly_score       numeric(4,3) NOT NULL,           -- 0.86 (multi-source concurrence)
    proportionality     numeric(4,3) NOT NULL,           -- P = 0.89 (CER/NIS2 resilience necessity)
    disposition         text NOT NULL DEFAULT 'monitor'
                        CHECK (disposition IN ('monitor','vhf_query','sar_launch',
                                               'scheduled_inspection','board_request')),
    gate_id             uuid,                            -- FK to the dual-control DecisionGate; NULL until gated
    prov_o              jsonb NOT NULL,
    -- LOAD-BEARING INVARIANT: no intrusive action (inspection / boarding) without a recorded human gate.
    -- monitor + vhf_query are pre-gate civil acts; a SAR launch is itself life-safety and gated separately.
    CHECK (disposition IN ('monitor','vhf_query') OR gate_id IS NOT NULL)
);
ALTER TABLE synergy.kcg_contact ENABLE ROW LEVEL SECURITY;
CREATE POLICY org_isolation ON synergy.kcg_contact
    USING (org_id = current_setting('app.current_org_id')::uuid);

The CHECK (disposition IN ('monitor','vhf_query') OR gate_id IS NOT NULL) makes it physically impossible to record a scheduled-inspection, boarding-request, or SAR-launch disposition without a human dual-control gate row — the decline-safety invariant is in the schema, not in a code path that can be bypassed.

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


Python
42 lines
def assess_kcg_contact(sonar_event, mmsi, requesting_org):
    # 1. DETECT + ENRICH — correlate sonar scour -> loitering AIS contact (multi-source).
    contact = correlate_sonar_to_vessel(sonar_event, mmsi)          # LBR flag, loiter 9h
    contact.satais = sat_ais_crosscheck(mmsi)                       # Copernicus/EMSA self-report check
    contact.dash8 = dash8_eo_corroborate(sonar_event.location)      # PAL Aerospace MSA EO pass
    contact.grid_dip = tennet_telemetry_dip(sonar_event.cable_segment)  # advisory resilience signal

    # 2. TRIAGE — concurrence score; only escalate on multi-signal agreement.
    score = anomaly_concurrence(loiter=contact.loiter_hours >= 8,
                                ais_gap=contact.ais_gap_minutes >= 15,
                                in_zone=contact.in_protection_zone,
                                sonar=sonar_event.classification == 'anchor_drag',
                                dash8=contact.dash8.confirmed)
    if score < 0.80:
        return Disposition.MONITOR                                  # show on globe, no escalation

    # 3. GATE — proportionality (CER/NIS2 resilience necessity); 5 personas incl. civil-society reviewer.
    P = proportionality(necessity=0.93, proport=0.89, lawful=0.95)  # P = 0.89
    gate = decision_room(
        proposal  = SurfaceResponse(contact, sonar_event),
        personas  = [OP_COORDINATION, PROPORTIONALITY, CIVIL_SOCIETY,
                     DEVILS_ADVOCATE, MARITIME_DOMAIN_EXPERT],
        threshold = P_MIN_TIER3)
    if gate.requests_boarding and gate.identity_unconfirmed:
        gate = gate.narrow_to('scheduled_inspection')              # civil-society + DB CHECK forbid pre-ID boarding
    if not gate.passed:
        return Disposition.REFUSED(gate.rationale)                 # logged refusal, no action

    # 4. TASK + EXECUTE + WRITE-BACK — KCG civil challenge + Dash-8 EO + USV re-survey; no weapons cue.
    write_back("kcg_moc_cop", requesting_org,
               PatrolTask(asset="Zr.Ms.-patrol", task="vhf_query+ais_identity_request"))
    write_back("dash8_tasking", "pal_aerospace",
               EoPassOrder(asset="Dash-8", target="NorNed/KP-31", mode="eo-confirm"))
    write_back("rmcm_tasking", "rnln_commit",
               UsvSurveyOrder(asset="Inspector-125M", target="NorNed/KP-31", mode="re-survey"))
    write_back("nis2.cable_incident.lodge", "tennet",              # NIS2 Art 23 significant-incident
               Nis2Lodgement(cable="NorNed", event=sonar_event, P=P))
    register_prospective(contact, trigger="flag_state_loiter_AISgap_near_cable")
    audit.append(contact.id, boundary_state="civil-security", merkle=True)
    return Disposition.EXECUTED

    # 5. BDA + CLOSE — patrol on-station + Dash-8 EO + Inspector re-survey confirm/deny scour cause; UNO close.

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


YAML
46 lines
workflow: netherlands_coastguard_autonomy_loop
trigger:
  on_event: auv_sonar_event.created   # rMCM A-18 / Inspector-125M / Damen autonomy / MAHI Sense
tenant_scope: app.current_org_id
nodes:
  - id: enrich_correlate
    skill: correlate_sonar_to_ais
    inputs: { sonar_event: $trigger.event, sat_ais: copernicus_emsa,
              dash8: pal_aerospace_msa, grid: tennet_telemetry }
  - id: triage_concurrence
    skill: anomaly_concurrence_score
    inputs: { contact: $enrich_correlate.contact }
    branch:
      - when: "$.anomaly_score < 0.80"
        goto: monitor_only
  - id: decision_room_gate
    type: human_gate            # <-- BLOCKING: workflow halts here until dual-control signs
    blocking: true
    quorum: 2                   # KCG MOC duty officer + RNLN watch officer
    personas: [op_coordination, proportionality, civil_society_reviewer,
               devils_advocate, maritime_domain_expert]
    proportionality_min: 0.85
    decline_guard:             # enforced civil-security perimeter
      forbid: [weapons_cue, mine_neutralisation, biometric_id, migrant_profiling, predictive_policing]
    on_refuse: { goto: log_refusal }
  - id: task_patrol
    skill: write_back_kcg_moc_cop
    inputs: { asset: "Zr.Ms.-patrol", task: "vhf_query+ais_identity_request" }
    depends_on: decision_room_gate
  - id: task_dash8
    skill: write_back_dash8_tasking
    inputs: { asset: Dash-8, target: "NorNed/KP-31", mode: eo-confirm }
    depends_on: decision_room_gate
  - id: task_usv_resurvey
    skill: write_back_rmcm_tasking
    inputs: { asset: Inspector-125M, target: "NorNed/KP-31", mode: re-survey }
    depends_on: decision_room_gate
  - id: lodge_nis2
    skill: nis2_cable_incident_lodge
    inputs: { cable: NorNed, operator: tennet, proportionality: $decision_room_gate.P }
    depends_on: decision_room_gate
  - id: bda_close
    skill: capture_bda_register_prospective
    inputs: { trigger: "flag_state_loiter_AISgap_near_cable" }
    depends_on: [task_patrol, task_dash8, task_usv_resurvey]
audit: { provo: true, merkle_anchor: rekor, retention: 7y }

The decision_room_gate node is blocking: true with quorum: 2 — the DAG cannot advance to any tasking node until two named humans (a KCG MOC duty officer + an RNLN watch officer) dual-control sign; the decline_guard block is a hard refusal list (note the migrant_profiling entry, specific to a coast-guard buyer) independent of any persona's recommendation.

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

Generated by _build/archetypes/gen_netherlands-coastguard-autonomy.py (imports archetypes.py; _ck() alignment-guarded; pure single-cell ASCII). These are this buyer's screens, not a reused shell.

Figure E06.1 — globe_rmp (primary). ShellLayout + TopBar (with PccPill + RendererChip: CesiumJS-globe) + LeftSidebar glyph-rail + MapConsole rendering the CesiumJS-globe over the Dutch North Sea (EMODnet bathy, IHO S-101 ENC, Borssele wind cluster, NorNed cable with the KP-31 scour break, the M/V loiter track, A-18 AUV + Inspector-125M USV + Dash-8 MSA glyphs) + a right-rail Inspector/TRACKS list feeding the ChatTerminal Decision Room + BottomStatusBar (L3 EuroLLM sovereign) + ClassificationBanner top/bottom mirror.

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

+--------------------------------------------------------------------------------------------------+
| Dutch North Sea Coast-Guard RMP - Kustwacht / JRCC Den Helder (CesiumJS-globe)                   |
+-------------------------------------------------------------------+------------------------------+
|        . - '' - .      DUTCH NORTH SEA  (PBNI corridor: Borssele) | TRACKS (sorted: anomaly)     |
|     /   o ----._  \   wind cluster + NorNed cable + fibre route   | M/V contact  LBR flag        |
|    |  [!] AIS gap  |   EMODnet bathy -28m :: IHO S-101 ENC tiles  |   AIS gaps 18m, loiter 9h    |
|    |   M/V contact |   M/V contact (LBR flag, AIS gaps 18min)     |   over NorNed + Borssele     |
|    |  speed 2kn 9h |   loiter 9h astride NorNed cable corridor    | AUV sonar event (A-18)       |
|     \ __X NorNed _/    A-18 AUV side-scan: seabed scour @ KP-31   |   KP-31  seabed scour 1.8m   |
|      \ '. ____ .' /    Inspector-125M USV: object 1.8m fresh drag |   class: anchor_drag .82     |
|        ' - x__ - '     TenneT telemetry: nominal (no MW dip yet)  | GRID telemetry (TenneT)      |
|   Camera {lat 51.70 lon 3.05 alt 12km} CesiumJS-globe             |   interconnector nominal     |
|   Concurrence: AIS gap + AUV sonar scour + loiter-in-zone         |   watch: NorNed segment      |
|   -> ANOMALY 0.86  ::  HUMAN GATE before any KCG tasking          | [#] CISE share: EMSA node    |
|                                                                   | gate: KCG VHF challenge      |
|                                                                   |   not weapons cue (civil)    |
+-------------------------------------------------------------------+------------------------------+
| EMODnet bathy + IHO S-101 + AIS mux + Sat-AIS Copernicus + rMCM A-18 AUV sonar :: KCG MOC fusion |
+--------------------------------------------------------------------------------------------------+

Figure E06.2 — map_ops (secondary). The 2D SAR + surface-response picture once a KCG challenge / scheduled inspection / SAR pass is gated: ShellLayout + a LAYERS panel (NorNed cable, 1nm zone, Borssele wind, AIS, Sat-AIS, AUV sonar, Dash-8 MSA, Inspector USV) + MapConsole + an INCIDENTS ticker. Note the explicit ROE line — no weapons cueing, no mine-neutralisation tasking in this COP, and the SAR co-pillar at JRCC Den Helder.

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

+------------------------------------------------------------------------------------------------------+
| Dutch North Sea SAR + Surface-Response Picture  (Kustwacht / JRCC Den Helder)                        |
+--------------------+---------------------------------------------------------------------------------+
| LAYERS             | MAP  ========================================================================== |
| [x] NorNed cable   | Dutch North Sea  51.70N 3.05E  ::  NorNed @ KP-31, Borssele wind edge           |
| [x] 1nm zone       |   M/V contact [!] loiter 9h inside 1nm protection zone, AIS gaps 18 min         |
| [x] Borssele wind  |   A-18 AUV side-scan: fresh seabed scour 1.8m -> attributed to loiter track     |
| [x] AIS tracks     |   TenneT interconnector telemetry nominal (no power dip) -> resilience watch    |
| [x] Sat-AIS        |   NorNed ===?=== scour @ KP-31   1nm zone polygon   Borssele wind cluster       |
| [x] AUV sonar      |   > Zr.Ms. patrol VHF Ch16 query + AIS-identity request (KCG civil)             |
| [x] Dash-8 MSA     |   > Dash-8 MSA re-routed overhead for EO confirmation pass                      |
| [ ] Inspector USV  |   > Inspector-125M USV launched for KP-31 re-survey (rMCM toolbox)              |
| ETA panel:         |   > SAR co-pillar: JRCC Den Helder on watch (no distress yet)                   |
| Zr.Ms 40m query    |   ROE: civil-security, voice challenge first, scheduled inspection              |
| Dash-8 overhead    |   NO weapons cueing :: NO mine-neutralisation tasking in this COP               |
| USV re-survey      |                                                                                 |
+--------------------+---------------------------------------------------------------------------------+
| INCIDENTS: M/V loiter+scour :: Zr.Ms VHF query :: Dash-8 EO pass :: Inspector re-survey :: CISE EMSA |
+------------------------------------------------------------------------------------------------------+

The bespoke SVG of the primary screen is at _build/figures/netherlands-coastguard-autonomy/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 at the KCG MOC / JRCC Den Helder seat). AUV-Sonar-Event alert badge in TRACKS → click the M/V contact LBR flag track → Inspector opens (loiter 9h, AIS-gap 18m, sonar scour 1.8m, anomaly 0.86) → click Correlate (runs Sat-AIS + Dash-8 EO + TenneT cross-check) → anomaly badge ≥0.80 unlocks Open Decision Room → 5 persona bubbles populate inside ChatTerminal; civil-society reviewer flags "no pre-ID boarding" → op-coordination reco auto-narrows to scheduled_inspection → /dual-control sign (KCG MOC duty officer) then /dual-control sign (RNLN watch officer) → /execute writes back Zr.Ms. VHF-query + Dash-8 EO pass + Inspector re-survey + NIS2 §23 lodge → switch to map_ops SAR/Surface-Response tab to watch on-station BDA → on confirm/deny, Close registers the ProspectiveItem watch.

[TRACKS alert] -> [Inspector] -> [Correlate] -> (anomaly>=0.80?) -> [Open Decision Room]
       |                                                                     |
       v                                                                     v
 [globe_rmp RMP] <----------------------------------------- [civil-society narrows reco]
                                                                             |
                                                                             v
                              [/dual-control x2] -> [/execute] -> [map_ops SAR/Surface] -> [BDA] -> [Close]

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

EU-RESTRICTED · TLP:AMBER · CIVIL-SECURITY  Dutch North Sea COP - KCG MOC / JRCC Den Helder tenant

[-] Op-coordination persona [L3 EuroLLM]
    Reco: anomaly 0.86 (loiter 9h + AIS-gap 18m + A-18 AUV sonar scour 1.8m @ NorNed/KP-31,
    Dash-8 EO not yet flown). Task a Zr.Ms. patrol VHF Ch16 challenge + AIS-identity request;
    re-route the Dash-8 MSA overhead for an EO pass; launch Inspector-125M USV for KP-31
    re-survey; place a boarding party on standby.

[-] Proportionality persona [L3 EuroLLM]
    P = 0.89 (N=0.93 necessity, P=0.89 proportionality, L=0.95 lawfulness). NorNed is a
    CER/NIS2 essential-entity interconnector; resilience necessity satisfied. Boarding is a
    higher-intrusion step - justify only on non-compliance or confirmed scour cause.

[-] Civil-society reviewer persona [L3 EuroLLM]  (DISSENT)
    Object to the standby boarding party. The vessel master is an identifiable person; a
    pre-identity boarding on an AIS-gap + sonar inference is disproportionate and risks
    surveillance-creep - and this is a CIVIL coast guard, not a navy interdiction. Keep it to
    a VHF challenge + an announced, scheduled inspection; escalate only on refusal. No crew
    biometric ID, no migrant profiling.

[-] Devil's advocate persona [L3 EuroLLM]
    Counter: a 1.8m scour + 9h loiter also fits an innocent anchor-watch in a forecast gale,
    or a trawl-net snag on the cable protector. Don't infer hostile intent. The Dash-8 EO
    pass is the cheap disambiguator - fly it BEFORE any surface escalation.

[-] Maritime domain expert persona [L3 EuroLLM]
    Scour width 1.8m with sustained loiter is more consistent with anchor-drag (alpha=0.82)
    than trawl (narrower, intermittent marks). Recommend the Inspector-125M high-res re-survey
    to confirm cause before any inference is written to the shared picture. ObsLevel = Inferred.

-- GATE VERDICT ------------------------------------------------------------------------
    The civil-society dissent + the devil's-advocate "fly the Dash-8 first" collapse the
    op-coordination reco's "boarding party on standby" into a narrower disposition: Dash-8 EO
    pass + VHF challenge + announced scheduled inspection + Inspector re-survey. Boarding is
    NOT authorised at this gate.
    DB CHECK confirms: disposition 'scheduled_inspection' requires gate_id -> present.
    [/dual-control sign - KCG MOC duty officer]   [/dual-control sign - RNLN watch officer]
    VERDICT: ACCEPT (narrowed)  P=0.89  2-of-2 quorum  ::  weapons cue / mine-tasking /
    biometric ID / migrant profiling REFUSED by decline_guard.

The materially-decision-changing disagreement: the civil-society reviewer's dissent, reinforced by the devil's-advocate "fly the Dash-8 EO pass first," removes the pre-identity boarding the op-coordination persona proposed — the gate accepts a narrower, resilience-only response that fits a civil coast guard.

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

Write-back targets. (1) KCG MOC COP — patrol-tasking via the MOC adapter (CoT-style task extension); lawful basis = Netherlands Coastguard cooperation framework. (2) Dash-8 tasking — EO-pass order to PAL Aerospace MSA via the tasking adapter; lawful basis = KCG surveillance mandate. (3) rMCM/RNLN tasking — Inspector-125M USV re-survey order via the COMMIT toolbox interface; lawful basis = RNLN operational tasking under the MoD PBNI permanent task. (4) nis2.cable_incident.lodge — NIS2 Article 23 significant-incident report to TenneT + the national CSIRT; lawful basis = NIS2 transposition. A PROV-O Activity is written per transition.

BDA + ProspectiveItem. BDA: Dash-8 EO pass shows an anchored coaster with deck gear consistent with anchor-watch in a forecast gale; Zr.Ms. patrol VHF Ch16 challenge issued, vessel responds and confirms anchor-watch; Inspector-125M high-res re-survey confirms anchor-drag scour over the cable protector (no breach); scheduled inspection logged; boarding pre-authorisation never triggered. CMA ObservationLevel of the BDA outcome = Confirmed (direct USV + patrol + Dash-8 observation). ProspectiveItem registered: flag-state-loiter-AISgap-near-cable — a watch for vessels exhibiting loiter + AIS-gap concurrence within 1 nm of named Dutch cable/wind assets, alpha=0.4 prior-belief weight.

PROV-O attribution chain. Entity:AuvSonarEvent-KP31 —wasGeneratedBy→ Activity:RmcmToolboxIngest-v1.0 —used→ Entity:SonarStream-A18. Entity:KcgContactAttribution —wasGeneratedBy→ Activity:SonarAisCorrelator-v1.0 —used→ {Entity:AuvSonarEvent-KP31, Entity:AisTrack-LBR, Entity:SatAisCrossCheck, Entity:Dash8EoFix}. Entity:DecisionRoomTranscript-E06 —wasGeneratedBy→ Activity:DecisionRoomCompose —used→ {Entity:OpCoordReco, Entity:ProportionalityP=0.89, Entity:CivilSocietyDissent, Entity:DevilsAdvAlt, Entity:MaritimeExpertReco}. Entity:DualControlGate —wasInformedBy→ {Entity:KcgMocDutySign, Entity:RnlnWatchSign}. Entity:ZrMsTask —wasGeneratedBy→ Activity:KcgMocWriteBack —used→ Entity:DualControlGate. Entity:Dash8EoOrder —wasGeneratedBy→ Activity:Dash8TaskingWriteBack. Entity:InspectorSurveyOrder —wasGeneratedBy→ Activity:RmcmTaskingWriteBack. Entity:Nis2Lodgement —wasGeneratedBy→ Activity:Nis2LodgeAdapter. Entity:BDA-E06 —wasGeneratedBy→ Activity:PatrolDash8UsvReport. Entity:ProspectiveItem-LoiterAISgap —wasGeneratedBy→ Activity:ProspectiveRegister. Merkle-anchored to Sigstore Rekor; whole chain reproducible from a provenanceOf query.

Deltas-only regulatory traceback (only what differs from the §4.0 EU-RESTRICTED civil-security defaults):

EU AI Act Art 6 + 27 — high-risk public-authority use → FRIA attached at the gate; Art 5 prohibitions (applicable 2 Feb 2025) are structurally excluded by the Declined List + decline_guard (note the added migrant_profiling guard for a coast-guard buyer).
NIS2 Art 21 + 23 — essential-entity (cable/grid) incident reporting is an active write-back, not a side-effect.
CER Directive — critical-entity resilience is the purpose framing; the PBNI is its national expression.
GDPR Art 6(1)(e) — only the vessel-master placeholder touches personal data; no special-category data; no migrant biometric data — the civil-society persona's narrowing + the decline_guard keep it that way.
CISE — inter-agency sharing covenant (KCG ↔ EMSA/EFCA/Frontex node, NL ↔ EE/BE) is transparent and logged; CISE operational since 1 Jul 2024.

§12 — Buyer & stakeholders

Role	Named / TBD	Notes
Civil buyer / champion	[Named contact TBD] — Netherlands Coastguard (Kustwacht) / JRCC Den Helder MOC programme office	the new MOC (2026) + PBNI "situational awareness" mandate are the public hooks; civil authority eases procurement
Edge / procurement route	[Named contact TBD] — RNLN / COMMIT Maritime Systems Division	runs the 12m USV + rMCM toolbox + MSS programmes; the MoD's PBNI "permanent task" lives here
Integration partner	Damen Naval + the Dutch Naval Design / Nov-2024 autonomy consortium (MARIN, DEMCON, RH Marine, Fugro, AVR, SkyDec)	the autonomy edge the COP sits above; a natural integration sponsor `[verified entities]`
Contracting gate-resolver	Pieter-Jan Note, Co-Founder & CEO, MAHI	`[verified person]`; founder's direct warm relationship; an EU contracting prime lifts the legal gate (V 0.10→0.75)
Surveillance partner	PAL Aerospace (Dash-8 MSA)	feed source; not a buyer
Grid/cable essential entity	TenneT (interconnectors) + cable operators	NIS2 §23 write-back recipient
Buyer procurement	Dutch MoD / COMMIT (defence) and/or KCG civil procurement; EU CISE/EMSA route	civil-side procurement is the lower-friction lane

§13 — Competition / incumbency + comparator (cited)

Incumbent COP context: the KCG's new Maritime Operations Centre (2026) brings "new ICT facilities" but the public record does not name a deployed decision-intelligence/anomaly-fusion vendor — the COP modernisation is an ICT-and-facilities programme, leaving the fusion/decision layer as genuine white space. Strategy: arrive as the decision layer on top of the new MOC ICT, not a rip-and-replace. [verified — no named decision-AI incumbent] (kustwacht.nl; cepezed.nl).
Autonomy edge: Damen Naval + the Dutch Naval Design consortium own the platform-level USV autonomy (sense + autonomous navigation) — but that is vessel autonomy, not a cross-agency civil-security MDA+SAR decision COP. No overlap with the decline-safe fusion layer; Damen is an integration partner, not a competitor. [verified] (navalnews.com; seasec.org).
rMCM autonomy: Naval Group + Exail provide the minehunter toolbox autonomy — mine-warfare autonomy at the platform level, explicitly out of scope (and excluded by decline_guard). [verified].
Palantir-class: no public Palantir/Helsing Dutch coast-guard decision-COP deployment is confirmed; the structural differentiator is the sovereign-EU LLM throughout + a civil-society persona seated inside the gate at exactly the tier where it is most absent — and the buyer's civil character makes the decline-safe story land cleanly. [unverified — no public Dutch deployment].

Comparator one-liner. We are not another sensor, another USV, or another video wall; we are the sovereign, human-gated civil decision layer that the KCG's new MOC ICT and the Damen/rMCM autonomy surge have no home for.

§14 — Readiness (honest, pre-pilot)

Reuse (real). The globe_rmp + map_ops surfaces, the AIS multiplexer, EMODnet/IHO S-101 map stack, the 5-persona Decision Room, the PROV-O ledger, FRIA workflow, and the classification-aware AI Provider Router are all in the gallery/architecture. The storm-replay COP pattern transfers to a seabed-anomaly + SAR replay (the SAR co-pillar reuses the OPW/Met-Éireann flood + the maritime pillars).

Real gaps (honest).

No KCG/MOC adapter — write-back to the live MOC COP is AS-DESIGNED, unbuilt; the new MOC ICT spec is not public.
No autonomy data contract yet — the rMCM-toolbox / Damen-autonomy / MAHI-Sense sonar/track schema + API binding is a scoping spike, not built.
No Dutch-sovereign hosting decision — EU-hosted yes; NL-jurisdiction specifics TBD per accreditation.
Legal gate open — solo founder on Stamp-1G cannot sign a paid contract (see §20); an EU contracting prime (MAHI) or a Dutch SI (Damen) is the resolver but unconfirmed.
Sonar-classification confidence is the analytic bottleneck, not AIS attribution — needs a labelled North-Sea-waters corpus.
No named KCG/COMMIT contact yet — access is warm via the EU/MAHI/Damen network but not yet a named budget-owner.
Decline-policing: must hold the civil-security line hard against any pull toward mine-warfare targeting, crew identification, or migrant profiling.

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

Stage 1 — First contact (warm). Trigger: founder-to-founder relationship with MAHI + the all-EU Belgian/Dutch rMCM context. Owner: Founder. Activity: send the Pieter-Jan Note note (adapted below) and ask MAHI/Damen-ecosystem contacts to bridge a KCG-MOC / COMMIT champion. Exit: MAHI/Damen agrees a joint scoping conversation. Deliverable: scheduled session + NDA (founder's own name).

Subject: Edge + sovereign brain — a Dutch coast-guard autonomy play for the PBNI window Pieter-Jan — the autonomous vessels (Alpha-8 / rMCM Inspector + A-18 / the Damen-led Dutch USV) sense the North Sea; Nexus Synergy is the sovereign decision/COP layer above them. The Netherlands has a funded, dated forcing function: the PBNI (€16.8M 2024 + €24.6M 2025) gave Defence a permanent task to protect North Sea infrastructure, and the KCG's new Maritime Operations Centre (Den Helder, 2026) is explicitly an "even clearer picture" ICT moment with no named decision-AI vendor. An all-EU Belgian+Irish (+Dutch via Damen) team is exactly what EDIP's buy-European mandate and EUDIS/EDF maritime calls reward. Two asks: (1) a technical session on the autonomy open-API / sonar+track schema to scope a data contract; (2) an honest conversation about MAHI as the contracting vehicle for a first Dutch discovery — which also clears a legal gate on my side. — [Founder]

Stage 2 — Free discovery (60-min, adapted agenda). Trigger: MAHI/Damen brokers a KCG-MOC / COMMIT intro. Owner: Founder + partner. Activity: run the discovery agenda — 0:00 frame/permission (one sentence: "EU-sovereign COP, the Palantir for the EU with sovereignty in the architecture"; discovery not pitch); 0:05 current operating picture ("walk me through a recent cable-anomaly or a SAR case from detection to close — how many systems, what's the slowest step?"); 0:20 governance/lawful basis (PBNI/NIS2/CER scope, AI Act high-risk, EU-sovereign model-call requirement, raw-fact-vs-inference traceability, the no-migrant-profiling line); 0:35 stakeholders/budget/timing (who owns the MOC/PBNI budget; CISE/EMSA, EDIP, EUDIS; Damen/MAHI already in the picture?); 0:45 map their loop onto detect→enrich→triage→gate→task→execute→assess→close, finding the fuse/triage/gate gap; 0:55 close — reflect back top-3 pains, ask "worth a 30-min walkthrough on your kind of data?". Exit: champion agrees there's a problem worth solving + Declined-List PASS. Deliverable: same-day discovery write-up (sponsor, pains, lawful basis, funding vehicle, next date).

Stage 3 — Scoped demo. Trigger: discovery exit. Owner: Founder. Activity: replay a Dutch North Sea seabed-anomaly + a SAR triage (representative, non-classified) through globe_rmp→Decision Room→map_ops, leading with sovereignty (AI Provider Router refuses non-EU model calls), the civil-society persona inside the gate, the no-migrant-profiling decline line, and claim-level epistemic tagging. Exit: "could we try this on a narrow real slice?" Deliverable: the 1-page pilot proposal.

Stage 4 — Pilot (1-page proposal, filled). Trigger: demo exit. Owner: Founder + MAHI/Damen + champion. Deliverable/template (filled):

Pilot: Dutch North Sea Autonomous Coast-Guard Anomaly-Fusion + SAR COP — KCG MOC + RNLN/COMMIT. Sponsor: [KCG/COMMIT champion TBD] + MAHI/Damen. Problem (their words): "we detect with many sensors and arriving autonomy but can't fuse them into one human-gated anomaly/SAR picture across our six agencies." The one thing we'll prove: fuse AIS + Sat-AIS + Dash-8 EO + rMCM/Damen sonar + TenneT telemetry into one COP and reduce time-to-confident-anomaly (and time-to-SAR-triage) from X to Y (X/Y baseline measured in week 1). Scope in: globe_rmp + map_ops + Decision Room + 1 cable corridor (NorNed) + 1 SAR replay + 1 autonomy feed. Out: mine-warfare tasking, biometric/migrant ID, any displacement of the MOC ICT. Data/lawful basis: non-personal vessel/sonar/SAR telemetry; EU-RESTRICTED isolation tier; EU-hosted. Success criteria: (a) ≥X% false-positive reduction vs single-sensor; (b) gated decision in ≤Y min; (c) full PROV-O reproducibility. Timeline: 8-12 weeks, mid-point checkpoint. Commercials: €0 to the institution if PBNI/EDIP/CISE-funded; else TBD. After: LOI if criteria met. Funding vehicle: PBNI line / EDIP SME / EUDIS / EU CISE.

Exit: success criteria met or credibly trending. Deliverable: pilot report.

Stage 5 — LOI (checklist). Trigger: pilot success. Owner: Founder + solicitor. Activity: LOI capturing — parties (NewCo or founder-own-name + MAHI/Damen prime); statement of intent; scope; success-criteria reference; named sponsor; timeline/next step; indicative commercials ("to be scoped under PBNI/EDIP/EU procurement"); conditions (funding, accreditation, DPA); non-binding except confidentiality; Declined-List affirmation (incl. no migrant profiling); governing law; signatures; solicitor review confirmed. Exit: signed LOI. Deliverable: the LOI (triggers the partner-vehicle / Stamp-4 gate).

Stage 6 — Signed contract. Trigger: LOI + a contracting vehicle exists (MAHI/Damen-as-prime or NewCo on Stamp-4). Owner: prime/NewCo + buyer procurement. Activity: PBNI/EDIP grant or KCG civil award; DPA + security accreditation. Exit: signed contract. Deliverable: production engagement.

§16 — PM / timeline

Stage \ Month        M0  M1  M2  M3  M4  M5  M6  M7  M8  M9  M10 M11 M12 M13 M14
1 First contact      [##]
2 Free discovery         [###]
3 Scoped demo                [###]
4 Pilot (PBNI/EDIP)             [################]
5 LOI                                            [###]
   * partner-vehicle gate ...................... [GATE: critical for a PAID pilot]
6 Signed contract                                    [#########]

Milestones. M1 MAHI/Damen data-contract scoping session · M4 scoped demo accepted · M5-M9 pilot · M10 LOI · M10 partner-vehicle gate (MAHI/Damen-as-prime confirmed OR founder on Stamp-4) · M14 signed contract.

Critical path. The Stamp-1G → partner-vehicle gate is on the critical path for any paid pilot/contract: a free discovery + demo + grant-funded pilot can run without it, but no paid signature is legally possible until an EU prime (MAHI/Damen) is the confirmed contracting vehicle or the founder is on Stamp-4 (≈t_resolve 14 months, reflecting the multi-agency Dutch civil-procurement cadence).

RACI.

Activity	Founder	Warm-intro sponsor (MAHI)	MAHI/Damen partner-vehicle	Buyer champion (KCG/COMMIT)	Buyer procurement (MoD/KCG)
First contact	R/A	C	—	I	—
Discovery	R/A	C	C	R	I
Demo	R/A	C	C	A	I
Pilot delivery	R	I	A/R	C	I
LOI	A	C	C	R	C
Contracting vehicle	C	C	A/R	I	C
Signed contract	C	I	R	A	A/R

§17 — Funding / procurement vehicle

PBNI (North Sea Infrastructure Protection Programme) — the national line: €16.8 M (2024) + €24.6 M (2025) across IenW/Defence/EZK/JenV/BZ; the MoD permanent task + "situational awareness + response system" is the natural budget home for a fusion/decision layer. [verified] (nedzero.nl; noordzeeloket.nl).
KCG Maritime Operations Centre (2026) ICT — the modernisation programme with the explicit "clearer picture / new ICT" justification — the civil-procurement on-ramp. [verified] (kustwacht.nl).
EU CISE / EMSA — operational since 1 Jul 2024; a CISE-compliant national node is a fundable EU-aligned framing (NL already in MARSEC EU 24). [verified] (emsa.europa.eu).
EDIP (European Defence Industry Programme) — €1.5bn 2025-2027 (adopted 8 Dec 2025); consortium grants up to €20m/project; buy-European mandate favours an all-EU Belgian (MAHI) + Dutch (Damen) + Irish (Nexus Synergy) team. [verified].
EUDIS / EDF maritime track — non-dilutive SME calls; EDF 2026 closes 29 Sep 2026. [verified].
Ireland-side enablers (for the founder's pilot delivery): Innovation Voucher (€5k), PSSF (≤€100k), HPSU Feasibility (≤€30k). [verified].

§18 — TWO-STAGE FORMULA SCORECARD

Stage-1 vector {mandate_pull, access_warmth, demonstrability, decline_safety, white_space, cycle_speed, pillar_fit} = {4, 3, 3, 5, 3, 3, 5} [PRIOR]:

mandate_pull = 4 — (2026-06-05) live, dated, funded forcing functions (PBNI €16.8M 2024 + €24.6M 2025, MoD permanent task, Harbers letter 11-Jun-2024; new MOC 2026 ICT) but not a single named line that says "buy a coast-guard decision COP this FY."
access_warmth = 3 — (2026-06-05) warm via the MAHI founder relationship + the all-EU rMCM/Damen ecosystem, but no named KCG/COMMIT budget-owner has offered to bridge or co-sponsor (below NDFEM/DART warmth).
demonstrability = 3 — (2026-06-05) strong reuse (globe_rmp + Decision Room + AIS/EMODnet + SAR pillar) but needs an autonomy data-contract spike before it runs on the buyer's real edge data; the MOC ICT spec is not public.
decline_safety = 5 — (2026-06-05) civil coast guard; asset/vessel/SAR telemetry not person data; weapons-cue/mine-tasking/biometric/migrant-profiling explicitly guarded; no drift possible.
white_space = 3 — (2026-06-05) the MOC modernisation is ICT-and-facilities with no named decision-AI incumbent, and Damen owns only platform autonomy — but TenneT/EMSA/MOC integration is multi-party and contested.
cycle_speed = 3 — (2026-06-05) a civil coast guard buyer + CISE/PBNI grant routes mean a faster non-OJEU discovery/pilot lane than a pure-defence buy.
pillar_fit = 5 — (2026-06-05) squarely the action-loop COP core (detect→fuse→gate→task→close over a sovereign map stack, MDA + SAR).

S1 = 3.62 → P_LOI = 0.55/(1+exp(−1.15·(3.62−2.6))) = 0.420 (≈42.0%) [PRIOR]. Score100 = S1·20 = 72.4 ≈ 72.

Stage-2 vector {contractability, funding_to_pay, procurement_clarity, incumbency_displacement, time_to_value, reference_leverage} = {3, 4, 3, 4, 3, 2} [PRIOR]:

contractability = 3 — (2026-06-05) MAHI (or a Dutch Damen-led SI) as an EU contracting prime is a credible vehicle (founder otherwise Stamp-1G solo).
funding_to_pay = 4 — (2026-06-05) PBNI (€41.4M 2024-25) + EDIP + CISE are real, accessible, dated funding routes.
procurement_clarity = 3 — (2026-06-05) the civil KCG/CISE lane is clearer than a pure-defence MoD buy, though still multi-agency.
incumbency_displacement = 4 — (2026-06-05) we sit above the new MOC ICT + Damen autonomy and integrate, not rip-and-replace.
time_to_value = 3 — (2026-06-05) an 8-12 week pilot can show value, but a paid production buy may outrun an early-stage founder's timeline given the 14-mo civil cadence.
reference_leverage = 2 — (2026-06-05) first EU coast-guard logo; no delivered decline-safe reference yet to de-risk.

S2 = 3.30 → P_raw = 0.70/(1+exp(−1.1·(3.30−2.8))) = 0.444 (≈44.4%) [PRIOR].

Legal gate G = V·T, t_resolve ≈ 14 mo → T = (30−14)/30 = 0.533:

V = 0.10 (today, solo Stamp-1G): G=0.053 → P(Contract|LOI) ≈ 2.4%, P(Contract joint) ≈ 1.0%.
V = 0.45 (co-founder/Dogpatch vehicle): G=0.240 → P(Contract|LOI) ≈ 10.7%.
V = 0.75 (MAHI/Damen confirmed prime): G=0.400 → P(Contract|LOI) ≈ 17.8%, P(Contract joint) ≈ 7.5%.
V = 1.0 (Stamp-4 incorporated): G=0.533 → P(Contract|LOI) ≈ 23.7%.

P(Contract) = P_LOI · G · P_raw. As in the worked examples, an EU contracting prime's value is that it lifts the gate (V 0.10→0.75), not Stage-1.

Reconciliation to board_anchor. The spec sets score100: "[PRIOR-derive]", value: med-high. Derived Score100 = 72 (P_LOI band ≈ 38-46%), value med-high. This sits just below the Belgian sibling (e01, 75 — which has a publicly dated parliamentary AI-in-MIK ask and a warmer in-country MAHI bridge) and at/above the EMSA-CISE sibling (e02), justified because the Dutch buyer has (a) a funded, dated national programme (PBNI), (b) a civil coast-guard buyer that is easier to contract and cleaner on decline-safety, and (c) an open ICT-modernisation window (MOC 2026) with no named decision-AI incumbent — but is held below 75 by weaker named access (no KCG/COMMIT champion yet) and a longer 14-mo civil cadence. Value band: med-high. ✓

§19 — Commercial

Tier	Scope	Indicative ACV
Tier 1	Single-corridor KCG anomaly-fusion + SAR COP pilot-to-production (1 cable/wind slice)	€120-240k/yr
Tier 2	Dutch North Sea full MDA+SAR COP across the six KCG agencies + rMCM/Damen feeds	€600k-1.2m/yr
Tier 3	Belgian-Dutch rMCM multi-domain + CISE-federated coast-guard COP	€2.4-4.8m/yr

Terms. Annual SaaS-style licence; EU-hosted; DPA per tenant; cost advantage from open-source substrate + sovereign HPC + shared conformity file + no forward-deployed-engineer dependency. Requirements before any paid tier: a contracting vehicle (MAHI/Damen-as-prime or NewCo on Stamp-4), a signed DPA, EU-RESTRICTED isolation accreditation, and an autonomy data-sharing agreement (carving out MAHI's/Damen's pre-existing edge IP).

§20 — Legal blockers

X1 — Stamp-1G (hard, critical-path). The solo founder cannot be a director/shareholder or sign a paid contract until Stamp-4. Mitigation: MAHI (or a Dutch Damen-led SI) as the contracting prime (lifts V 0.10→0.75) OR EEA-resident-director cover for a NewCo. ⚖️ CONFIRM (immigration solicitor).
X2 — EU AI Act. High-risk public-authority maritime COP → FRIA required; Art-5 prohibitions (applicable 2 Feb 2025, not 2 Aug) are structurally excluded by the Declined List + decline_guard (incl. the migrant_profiling entry). ⚖️ CONFIRM per-use-case.
X4 — Dual-use export (Reg. (EU) 2021/821). USV/AUV-sonar + AIS/comms fusion can classify as controlled cyber-surveillance. ⚖️ CONFIRM (export counsel).
X5 — Defence procurement (Dir. 2009/81/EC + Art-346 TFEU). A defence-side (COMMIT) buy may use negotiated/exempt procedures; the civil KCG/CISE lane avoids most of this — prefer the civil route. [verified].
X6 — NATO DIANA exclusion (Ireland non-NATO). Use EU vehicles (EDIP/EUDIS/EDF/CISE); do not route via DIANA. [verified].
X7 — Pre-incorporation contracting. Founder personally liable until NewCo formed; sign NDA/MOU in own name under Companies Act 2014 s.45. ⚖️ CONFIRM.
Buyer-specific — CISE / cross-agency data-sharing covenant must be papered (KCG's six agencies ↔ EMSA ↔ TenneT/cable operators); decline-policing: hold the civil-security line hard — any drift to mine-warfare targeting, crew identification, or migrant biometric profiling (a real risk at a coast guard) is fatal and excluded by schema + decline_guard.

§21 — Warm-intro contact + the SPECIFIC ask

Contact: Pieter-Jan Note, Co-Founder & CEO, MAHI (Mechelen, Belgium) — the founder's direct founder-to-founder relationship, and the natural bridge into the all-EU Belgian-Dutch rMCM/Damen autonomy ecosystem. [verified person; email not public].

The specific ask (two parts):

Technical/bridging — a session with MAHI's integration leads (Van den Bergh / Lauwers) on the autonomy open-API + sonar/track schema to scope the data contract, and an ask for MAHI/Damen-ecosystem contacts to bridge a KCG-MOC / RNLN-COMMIT champion, leveraging the public PBNI mandate + the MOC-2026 ICT window.
Commercial/structural — an honest conversation about MAHI (or a Damen-led Dutch SI) acting as the EU contracting prime for a first Dutch coast-guard discovery + pilot, framed as the all-EU Belgian+Dutch+Irish team EDIP's buy-European mandate rewards — which simultaneously resolves the founder's Stamp-1G legal gate.

§22 — Open questions + consolidated Sources

Open questions (do not assert until resolved):

Named KCG-MOC / RNLN-COMMIT budget-owner and whether the PBNI "situational awareness/response-system" need has a funded FY decision-COP line [TBD].
Whether the new MOC (2026) ICT scope already includes a decision/anomaly-fusion procurement, and who the integrator is [TBD — MOC ICT spec not public].
Whether MAHI or a Damen-led Dutch SI will act as the EU contracting prime + the written terms [TBD — founder conversation].
Autonomy (rMCM toolbox / Damen / MAHI Sense) sonar/track schema specifics + data-contract feasibility [TBD — technical spike].
Whether the civil KCG/CISE lane or the defence COMMIT lane is the faster procurement route [TBD].
NL-jurisdiction hosting/accreditation specifics for EU-RESTRICTED [TBD].
Exact EDIP/EUDIS consortium eligibility for a pre-incorporation Irish entity (min-3-MS rule via a MAHI/Damen consortium) [TBD — confirm].

Sources (dated; accessed 2026-06-05):

Netherlands Coastguard / JRCC Den Helder / structure — kustwacht.nl/en (we-are-the-coastguard; what-we-do); noordzeeloket.nl (Coastguard & Coastguard Centre). [verified]
Maritime Operations Centre (MOC) + FTT, due 2026 — cepezed.nl (new building "watchful eye over the North Sea"); kustwacht.nl. [verified]
Dash-8 MSA (PAL Aerospace, since 2022, +80% picture) — palaerospace.com/case-studies/nlcg. [verified]
PBNI North Sea Infrastructure Protection Programme (est. 2023; €16.8M 2024 + €24.6M 2025; MoD permanent task; six ministries; Harbers letter 11-Jun-2024; debate 30-May-2024) — nedzero.nl ("Protection of North Sea infrastructure is high on the cabinet's agenda"); noordzeeloket.nl/en (PBNI). [verified]
Subsea-infrastructure resilience context (Nord Stream, Nov-2024 Baltic cable damage) — hcss.nl (Dec-2025 "Strategies for Securing Subsea Infrastructure"). [verified]
RNLN / COMMIT 12m ASW USV (Damen Naval + MARIN + DEMCON; prototype aspiration end-2025) + Multifunction Support Ships — navalnews.com (CNE-2024 ASW-USV); en.wikipedia.org (Future of the Royal Netherlands Navy; Materiel and IT Command); navylookout.com (MSS concept). [verified]
Nov-2024 Dutch maritime-autonomy trials (AVR, Damen, DEMCON, Fugro, MARIN, RH Marine, SkyDec) — seasec.org (Unmanned Service Vessel experiments). [verified]
Belgian-Dutch rMCM / Vlissingen (first NL hull Mar-2026) / City-class Toolbox (Inspector-125M USV, A-18 AUV UMISAS-120, T-18 towed sonar, UMS Skeldar V-200; toolbox qualification early 2025; €2bn 2019 contract) — naval-technology.com; thedefensepost.com (2026-03); navalnews.com (Euronaval-2024 toolbox; Oostende sea trials). [verified]
MAHI Alpha-8 / MAHI Sense / REPMUS — tectonicdefense.com; maritime-executive.com. [verified]
EU CISE (operational 1-Jul-2024; EMSA-run; NL in MARSEC EU 24 alongside BE/EL/ES/FR/IT/MT) — emsa.europa.eu/cise.html; eeas.europa.eu (MARSEC EU 24); coastguard.europa.eu (NL national authority). [verified]
EDIP — consilium.europa.eu (€1.5bn, 8-Dec-2025 adoption, €20m/project, buy-European). [verified]
EU AI Act Art 5 (applicable 2-Feb-2025) — artificialintelligenceact.eu. [verified]
Netherlands defence spending increase context — trade.gov (Netherlands defense-spending-increase; >€19bn structural). [verified]

STANDING BANNER — read before using this package. (1) Status honesty. Nexus Synergy Ltd is pre-incorporation, pre-revenue, pre-pilot. The Netherlands Coastguard / Royal Netherlands Navy / COMMIT is a TARGET, not a customer; nothing here is a deployment, a contract, or traction. The ~178-surface UI gallery is a gallery, not a fielded system. MAHI and Damen are ecosystem relationships, not signed partners. (2) Anti-cookie-cutter. The §8 mockups are generated programmatically for this buyer (Dutch North Sea, Borssele wind cluster, NorNed/TenneT, JRCC Den Helder, A-18 AUV + Inspector-125M USV, Dash-8 MSA) and look like this buyer's screens — not a reused shell. (3) Every probability is [PRIOR]. All scores are subjective pre-pilot estimates with dated rationales, re-scored after each real conversation. Framing is strictly CIVIL-SECURITY / SAR / critical-infrastructure-resilience / MDA, never warfighting, mine-clearance targeting, or migrant biometric profiling.