STANDING BANNER — read before using this package. (1) Status honesty. Nexus Synergy Ltd is pre-incorporation, pre-revenue, pre-pilot. The Belgian Navy / MIK 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 is a warm founder relationship, not a signed partner. (2) Anti-cookie-cutter. The §8 mockups are generated programmatically for this buyer (Belgian North Sea, MIK Zeebrugge, rMCM Oostende, MAHI Alpha-8) 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 / critical-seabed-infrastructure protection / MDA, never warfighting or mine-clearance targeting.

§0 — Header + one-line thesis

Nexus Synergy as the sovereign, human-gated decision/operating-picture layer that turns Belgium's Maritime Information Crossroads (MIK) and its incoming rMCM/MAHI uncrewed-systems edge into one auditable critical-seabed-infrastructure-protection COP — fusing AIS + Sat-AIS + USV sonar + grid telemetry into a single anomaly picture above the wind farms, interconnectors and fibre cables of the Belgian North Sea, with a 5-persona Decision Room (including a civil-society reviewer) seated inside every escalation.

One line: MAHI senses the seabed; Nexus Synergy decides — lawfully, sovereignly, and on the record.

§1 — Entity snapshot (cited)

Belgian Navy / Naval Component — operates the rMCM minehunters and patrol vessels (Castor P902, Pollux P903; a third patrol vessel due by 2027). Commands NATO's Standing Mine Countermeasures Group and participates in Baltic Sentry. [verified] (armyrecognition.com, navalnews.com).
Coast Guard Centre — Maritime Information Crossroads (MIK), Zeebrugge — the maritime-security cell (sister to MRCC Ostend, the maritime-safety/SAR cell). Runs a GIS-based unified COP coordinating Defence, maritime police, customs and FPS Mobility; 24/7 control room with a Barco OpSpace video wall. Integrator: e-BO Enterprises (won the Belgian MoD tender in 2020). [verified] (ebo-enterprises.com, kustwacht.be, barco.com).
rMCM programme — M940 Oostende — first Belgian replacement-MCM vessel, first moored Zeebrugge November 2025; built by Belgian Naval & Robotics (Naval Group + Exail, Kership prime); carries a 12 m USV + AUV + UAV toolbox for autonomous mine detect/classify/ID. 12 hulls (6 BE + 6 NL) by 2030. [verified] (naval-group.com, navalnews.com).
MAHI (Mechelen, Belgium) — maritime-autonomy company; Alpha-8 USV unveiled 2 March 2026; open/modular MAHI Sense autonomy stack; used by UK MoD, US Navy, Belgian Navy; flown at NATO REPMUS 2025. CEO Pieter-Jan Note is the founder's direct warm-intro counterpart. [verified] (tectonicdefense.com, maritime-executive.com).
Nexus Synergy Ltd — pre-incorporation Irish EU-sovereign decision-intelligence / COP platform; the sovereign decision layer above MAHI's edge. [status: pre-incorporation].

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

Belgium has an acute, named, dated critical-seabed-infrastructure-protection gap, and a fusion/decision layer is precisely the missing piece:

The threat is live and political. Belgium has publicly "stepped up protection of North Sea infrastructure" — submarine cables, pipelines and offshore wind farms — against sabotage, espionage and accidental disruption, with North Sea Minister Annelies Verlinden naming "massive cables on the seabed" as a protection priority and the geopolitical context (Russian shadow-fleet incursions, the Baltic cable-cut crisis) cited as the forcing function. [verified] (belganewsagency.eu, 02/06/2026; armyrecognition.com).
Parliament has asked for exactly our wedge. On 12 February 2025 the House of Representatives' Defence Committee met on the MIK and critical infrastructure; Frigate Captain De Winter called for additional investment including "further development of AI applications within the MIK." [verified] (bluecluster.be).
The incumbent COP vendor names the gap itself. e-BO Enterprises' own MIK case study states the future development need is "AI-powered anomaly detection" to cut false positives and detect emerging threats like drone activity. The COP exists; the decision intelligence on top of it does not. [verified] (ebo-enterprises.com).
A sensing surge with no fused brain. The rMCM Oostende + MAHI Alpha-8 + REPMUS 2025 mean a flood of new uncrewed-systems sonar/AIS/UAV data is arriving — but the seabed-anomaly fusion + human-gated escalation across agencies is not a coherent product. The Belgian MoD has commissioned a CMIP RTI-ecosystem feasibility study precisely to fill this. [verified] (bluecluster.be CMIP ecosystem study).

The detect→fuse→triage→gate→task→assess→close chain is broken at fuse/triage/gate: today the MIK detects (rich sensors) and acts (phone/email/CAD), but multi-source anomaly fusion and an auditable human-gated escalation across Defence + Coast Guard + cable/grid operators is manual. That gap is the wedge.

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

Use case. A sovereign, human-gated critical-seabed-infrastructure-protection COP for the Belgian North Sea: fuse AIS + Sat-AIS (Copernicus/EMSA) + USV/AUV sonar (MAHI Sense) + Elia grid telemetry + IHO S-101 ENC + EMODnet bathymetry into one anomaly picture over the Prinses Elisabethzone wind cluster, the interconnectors and the fibre cables; surface a single concurrence-scored anomaly; and seat a 5-persona Decision Room (op-coordination, proportionality, civil-society reviewer, devil's advocate, maritime domain expert) inside every escalation before any coast-guard challenge or scheduled inspection is tasked.

Value.

Faster, defensible detection of seabed/cable interference (loiter + AIS-gap + sonar-scour concurrence) instead of single-sensor false-positive noise — directly answering the MIK's stated AI-anomaly need.
One auditable picture across agencies (Defence, Coast Guard, customs, cable/grid operators) with CISE-aligned sharing, 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; emotion recognition; social scoring; untargeted scraping; psychometric profiling; weapons cueing; or mine-neutralisation / clearance targeting. Vessel telemetry and seabed sonar are object/asset data, not person 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.

§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).
USV-Sonar-Event — sensor (MAHI Sense / rMCM AUV side-scan); seabed-object centroid; object length; scour width; classification (anchor_drag / trawl_snag / debris / unknown).
Cable-Segment / Pipeline-Segment — corridor id (C-7), KP marker, operator, criticality weight.
WindCluster — Prinses Elisabethzone array; turbine/cable footprint.
GridTelemetry — Elia interconnector power-flow (MW), nominal vs dip.
ProtectionZone — 1 nm polygon around a cable/pipeline/wind asset.
Asset — Castor/Pollux patrol, M940 Oostende, Alpha-8 USV, Coast Guard helo.
DecisionGate — proportionality score, persona transcript, dual-control signatures.

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

The hard entity-resolution problem: deciding whether a fresh seabed scour at KP-19 is attributable to the loitering AIS contact — a multi-source concurrence (loiter + AIS-gap + sonar) 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: Belgian Navy, MIK, cable/grid operator). The load-bearing safety property is the civilian-resilience→intrusive-action boundary: a contact cannot record an inspection/boarding authorisation without a recorded human dual-control gate, enforced as a DB CHECK, not application logic.


SQL
43 lines
-- USV/AUV sonar event from an uncrewed asset (MAHI Sense / rMCM toolbox), org-scoped + RLS.
CREATE TABLE synergy.usv_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,                       -- 'MAHI-ALPHA8-01' | 'M940-AUV-2'
    event_at        timestamptz NOT NULL,                -- 14:02:18Z
    cable_segment   text,                                -- 'C-7' (KP-19)
    object_len_m    numeric(6,1),                        -- 2.1
    scour_width_m   numeric(6,1),                        -- 2.1
    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                       -- MahiSenseIngest-v1.2 attribution
);
ALTER TABLE synergy.usv_sonar_event ENABLE ROW LEVEL SECURITY;
CREATE POLICY org_isolation ON synergy.usv_sonar_event
    USING (org_id = current_setting('app.current_org_id')::uuid);

-- Seabed-infrastructure contact = the cross-agency alert entity; the resilience->action boundary lives here.
CREATE TABLE synergy.seabed_contact (
    id                  uuid PRIMARY KEY DEFAULT gen_random_uuid(),
    org_id              uuid NOT NULL,
    cable_segment       text NOT NULL,                   -- 'C-7'
    vessel_mmsi         text,                            -- anonymised in the shared picture
    flag_state          text,                            -- 'PAN'
    sonar_event_id      uuid REFERENCES synergy.usv_sonar_event(id),
    ais_gap_minutes     numeric(6,1) NOT NULL DEFAULT 0, -- 22.0
    loiter_hours        numeric(6,1) NOT NULL DEFAULT 0, -- 11.0 inside the 1nm zone
    in_protection_zone  boolean NOT NULL DEFAULT false,  -- 1nm polygon test
    grid_dip_observed   boolean NOT NULL DEFAULT false,  -- Elia telemetry dip y/n
    anomaly_score       numeric(4,3) NOT NULL,           -- 0.88 (multi-source concurrence)
    proportionality     numeric(4,3) NOT NULL,           -- P = 0.90 (CER/NIS2 resilience necessity)
    disposition         text NOT NULL DEFAULT 'monitor'
                        CHECK (disposition IN ('monitor','vhf_query','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 request) without a recorded human gate.
    CHECK (disposition IN ('monitor','vhf_query') OR gate_id IS NOT NULL)
);
ALTER TABLE synergy.seabed_contact ENABLE ROW LEVEL SECURITY;
CREATE POLICY org_isolation ON synergy.seabed_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 or boarding-request 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
38 lines
def assess_seabed_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)          # PAN flag, loiter 11h
    contact.satais = sat_ais_crosscheck(mmsi)                        # Copernicus/EMSA self-report check
    contact.grid_dip = elia_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')
    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.94, proport=0.90, lawful=0.95)   # P = 0.90
    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 — coast-guard challenge + USV re-survey; no weapons cue.
    write_back("mik_cop", requesting_org,
               PatrolTask(asset="Castor", task="vhf_query+ais_identity_request"))
    write_back("rmcm_tasking", "naval_component",
               UsvSurveyOrder(asset="Alpha-8", target="C-7/KP-19", mode="re-survey"))
    write_back("nis2.cable_incident.lodge", "elia",                 # NIS2 Art 23 significant-incident
               Nis2Lodgement(cable="C-7", 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 + Alpha-8 re-survey confirm/deny scour cause; UNO close.

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


YAML
41 lines
workflow: belgium_seabed_infra_protection_loop
trigger:
  on_event: usv_sonar_event.created   # MAHI Sense / rMCM AUV side-scan
tenant_scope: app.current_org_id
nodes:
  - id: enrich_correlate
    skill: correlate_sonar_to_ais
    inputs: { sonar_event: $trigger.event, sat_ais: copernicus_emsa, grid: elia_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                   # MIK duty officer + Navy 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, predictive_policing]
    on_refuse: { goto: log_refusal }
  - id: task_patrol
    skill: write_back_mik_cop
    inputs: { asset: Castor, task: "vhf_query+ais_identity_request" }
    depends_on: decision_room_gate
  - id: task_usv_resurvey
    skill: write_back_rmcm_tasking
    inputs: { asset: Alpha-8, target: "C-7/KP-19", mode: re-survey }
    depends_on: decision_room_gate
  - id: lodge_nis2
    skill: nis2_cable_incident_lodge
    inputs: { cable: C-7, operator: elia, 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_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 dual-control sign; the decline_guard block is a hard refusal list independent of any persona's recommendation.

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

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

Figure E01.1 — globe_rmp (primary). ShellLayout + TopBar (with PccPill + RendererChip: CesiumJS-globe) + LeftSidebar glyph-rail + MapConsole rendering the CesiumJS-globe over the Belgian North Sea (EMODnet bathy, IHO S-101 ENC, Prinses Elisabethzone wind cluster, cable C-7 with the KP-19 scour break, the M/V loiter track, MAHI Alpha-8 USV + M940 Oostende glyphs) + a right-rail 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.

+--------------------------------------------------------------------------------------------------+
| Belgian Seabed-Infrastructure RMP - Navy + MIK Zeebrugge (CesiumJS-globe)                        |
+-------------------------------------------------------------------+------------------------------+
|        . - '' - .      BELGIAN NORTH SEA (Prinses Elisabethzone)  | TRACKS (sorted: anomaly)     |
|     /   o ----._  \   wind cluster + interconnector + fibre cables| M/V contact  PAN flag        |
|    |  [!] AIS gap  |   EMODnet bathy -34m :: IHO S-101 ENC        |   AIS gaps 22m, loiter 11h   |
|    |   M/V contact |   M/V contact (PAN flag, AIS gaps 22min)     |   over cable C-7 + wind C    |
|    |  speed 3kn 11h|   loiter 11h astride cable corridor C-7      | USV sonar event (Alpha-8)    |
|     \ __X cable C7_/   USV sonar: seabed scour @ KP-19 (drag)     |   KP-19  seabed scour 2.1m   |
|      \ '. ____ .' /    Alpha-8 USV side-scan: object 2.1m fresh   |   class: anchor_drag .84     |
|        ' - x__ - '     Elia telemetry: nominal (no MW dip yet)    | GRID telemetry (Elia)        |
|   Camera {lat 51.62 lon 2.81 alt 14km} CesiumJS-globe             |   interconnector nominal     |
|   Concurrence: AIS gap + USV sonar scour + loiter-in-zone         |   watch: cable C-7 segment   |
|   -> ANOMALY 0.88  ::  HUMAN GATE before any tasking              | [#] CISE share: MIK cell     |
|                                                                   | gate: coast-guard challenge  |
|                                                                   |   not weapons cue (civil)    |
+-------------------------------------------------------------------+------------------------------+
| EMODnet bathy + IHO S-101 + AIS mux + Sat-AIS Copernicus + MAHI Sense USV sonar :: MIK fusion ON |
+--------------------------------------------------------------------------------------------------+

Figure E01.2 — map_ops (secondary). The 2D surface-response picture once a coast-guard challenge / scheduled inspection is gated: ShellLayout + a LAYERS panel (cable C-7, 1nm zone, wind cluster, AIS, Sat-AIS, USV sonar, patrol assets, Alpha-8) + MapConsole + an INCIDENTS ticker. Note the explicit ROE line — no weapons cueing, no mine-neutralisation tasking in this COP.

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

+------------------------------------------------------------------------------------------------------+
| Belgian North Sea Surface-Response Picture  (Navy + Coast Guard Centre / MIK)                        |
+--------------------+---------------------------------------------------------------------------------+
| LAYERS             | MAP  ========================================================================== |
| [x] Cable C-7      | Belgian North Sea  51.62N 2.81E  ::  cable C-7 @ KP-19, wind cluster C edge     |
| [x] 1nm zone       |   M/V contact [!] loiter 11h inside 1nm protection zone, AIS gaps 22 min        |
| [x] Wind clstr C   |   USV side-scan: fresh seabed scour 2.1m -> attributed to loiter track          |
| [x] AIS tracks     |   Elia interconnector telemetry nominal (no power dip) -> resilience watch      |
| [x] Sat-AIS        |   cable C-7 ===?=== scour @ KP-19   1nm zone polygon   wind cluster C           |
| [x] USV sonar      |   > Castor (P902) VHF Ch16 query + AIS-identity request                         |
| [x] Patrol (2)     |   > M940 Oostende on-station, launch Alpha-8 USV for KP-19 re-survey            |
| [ ] Alpha-8 USV    |   > Coast Guard Centre / MRCC Ostend notified (safety co-pillar)                |
| ETA panel:         |   ROE: civil-security, voice challenge first, scheduled inspection              |
| Castor 55m query   |   NO weapons cueing :: NO mine-neutralisation tasking in this COP               |
| M940 on-station    |                                                                                 |
| Alpha-8 re-survey  |                                                                                 |
+--------------------+---------------------------------------------------------------------------------+
| INCIDENTS: M/V loiter+sonar scour :: Castor VHF query :: Alpha-8 re-survey :: MIK CISE share EE+NL   |
+------------------------------------------------------------------------------------------------------+

The bespoke SVG of the primary screen is at _build/figures/belgium-repmus-seabed-mahi/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 MIK seat). USV-Sonar-Event alert badge in TRACKS → click the M/V contact PAN flag track → Inspector opens (loiter 11h, AIS-gap 22m, sonar scour 2.1m, anomaly 0.88) → click Correlate (runs Sat-AIS + Elia 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 (MIK duty officer) then /dual-control sign (Navy watch officer) → /execute writes back Castor VHF-query + Alpha-8 re-survey + NIS2 §23 lodge → switch to map_ops 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 Surface-Response] -> [BDA] -> [Close]

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

▣ EU-RESTRICTED · TLP:AMBER · CIVIL-SECURITY ▣  Belgian Seabed-Infra COP — MIK Zeebrugge tenant

⊟ Op-coordination persona [L3 EuroLLM]
   Reco: anomaly 0.88 (loiter 11h + AIS-gap 22m + USV sonar scour 2.1m @ C-7/KP-19).
   Task Castor (P902) VHF Ch16 challenge + AIS-identity request; M940 Oostende launch
   Alpha-8 USV for KP-19 re-survey; request boarding party on standby.

⊟ Proportionality persona [L3 EuroLLM]
   P = 0.90 (N=0.94 necessity, P=0.90 proportionality, L=0.95 lawfulness). Cable C-7 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. This is critical-infrastructure RESILIENCE, not interdiction. Keep it
   to a VHF challenge + a scheduled, announced inspection; escalate only on refusal.

⊟ Devil's advocate persona [L3 EuroLLM]
   Counter: a 2.1m scour + 11h loiter also fits an innocent anchor-watch in bad weather, or a
   trawl-net snag on the cable protector. Don't infer hostile intent. Inspect, don't accuse.

⊟ Maritime domain expert persona [L3 EuroLLM]
   Scour width 2.1m with sustained loiter is more consistent with anchor-drag (alpha=0.84)
   than trawl (which shows narrower, intermittent marks). Recommend Alpha-8 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 alternative collapse the op-coordination
   reco's "boarding party on standby" into a narrower disposition: VHF challenge + announced
   scheduled inspection + Alpha-8 re-survey. Boarding is NOT authorised at this gate.
   DB CHECK confirms: disposition 'scheduled_inspection' requires gate_id -> present.
   [/dual-control sign - MIK duty officer]   [/dual-control sign - Navy watch officer]
   VERDICT: ACCEPT (narrowed)  P=0.90  2-of-2 quorum  ::  weapons cue / mine-tasking REFUSED by guard.

The materially-decision-changing disagreement: the civil-society reviewer's dissent, backed by the devil's advocate, removes the pre-identity boarding the op-coordination persona proposed — the gate accepts a narrower, resilience-only response.

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

Write-back targets. (1) MIK COP — patrol-tasking via the e-BO/Barco adapter (CoT-style task extension); lawful basis = Belgian Coast Guard cooperation framework. (2) rMCM/MAHI tasking — Alpha-8 USV re-survey order via MAHI Sense open API; lawful basis = Naval Component operational tasking. (3) nis2.cable_incident.lodge — NIS2 Article 23 significant-incident report to the cable/grid operator (Elia) + the national CSIRT; lawful basis = NIS2 transposition. A PROV-O Activity is written per transition.

BDA + ProspectiveItem. BDA: Castor on-station, VHF Ch16 challenge issued, vessel responds and confirms anchor-watch in deteriorating weather; Alpha-8 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 observation). ProspectiveItem registered: flag-state-loiter-AISgap-near-cable — a watch for vessels exhibiting loiter + AIS-gap concurrence within 1 nm of named Belgian cable/wind assets, alpha=0.4 prior-belief weight.

PROV-O attribution chain. Entity:UsvSonarEvent-KP19 —wasGeneratedBy→ Activity:MahiSenseIngest-v1.2 —used→ Entity:SonarStream-Alpha8. Entity:SeabedContactAttribution —wasGeneratedBy→ Activity:SonarAisCorrelator-v1.0 —used→ {Entity:UsvSonarEvent-KP19, Entity:AisTrack-PAN, Entity:SatAisCrossCheck}. Entity:DecisionRoomTranscript-E01 —wasGeneratedBy→ Activity:DecisionRoomCompose —used→ {Entity:OpCoordReco, Entity:ProportionalityP=0.90, Entity:CivilSocietyDissent, Entity:DevilsAdvAlt, Entity:MaritimeExpertReco}. Entity:DualControlGate —wasInformedBy→ {Entity:MikDutySign, Entity:NavyWatchSign}. Entity:CastorTask —wasGeneratedBy→ Activity:MikCopWriteBack —used→ Entity:DualControlGate. Entity:Alpha8SurveyOrder —wasGeneratedBy→ Activity:RmcmTaskingWriteBack. Entity:Nis2Lodgement —wasGeneratedBy→ Activity:Nis2LodgeAdapter. Entity:BDA-E01 —wasGeneratedBy→ Activity:PatrolUsvReport. 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.
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, not an afterthought.
GDPR Art 6(1)(e) — only the vessel-master placeholder touches personal data; no special-category data; the civil-society persona's narrowing keeps it that way.
CISE — inter-agency sharing covenant (MIK ↔ EE/NL/EMSA) is transparent and logged.

§12 — Buyer & stakeholders

Role	Named / TBD	Notes
Edge partner / contracting gate-resolver	Pieter-Jan Note, Co-Founder & CEO, MAHI	`[verified person]`; founder's direct warm relationship; MAHI as the Belgian contracting prime lifts the legal gate (V 0.10→0.75)
Technical integration counterpart	Bertold Van den Bergh / Quinten Lauwers (MAHI)	`[verified]` — MAHI Sense open API / track + sonar schema for the data-contract spike
MIK / Coast Guard champion	[Named contact TBD] — via the 12-Feb-2025 Defence Committee thread (Frigate Captain De Winter named publicly)	the AI-anomaly need is publicly on record
rMCM / Naval Component	[Named contact TBD]	M940 Oostende programme office
Incumbent COP integrator	e-BO Enterprises (+ Barco)	sit above, integrate — do not displace the GIS COP
Grid/cable essential entity	Elia (grid) + cable operators	NIS2 §23 write-back recipient
Buyer procurement	Belgian MoD / DG MR (Material Resources)	EDIP / national CMIP ecosystem route

§13 — Competition / incumbency + comparator (cited)

Incumbent COP: e-BO Enterprises built and maintains the MIK GIS COP (2020 MoD tender) with a Barco OpSpace video wall. Strategy: integrate above it, not replace it — e-BO's own roadmap names "AI-powered anomaly detection" as the future need, which is exactly the layer we provide. [verified] (ebo-enterprises.com).
rMCM autonomy: Naval Group + Exail provide the mission-system autonomy on the minehunter toolbox — but that is mine-warfare autonomy at the platform level, not a cross-agency civil-security seabed-infra COP. No overlap with the decline-safe fusion layer. [verified].
Palantir-class: no public Palantir/Helsing seabed-infra COP deployment in Belgium 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. [unverified — no public Belgian deployment].
PESCO CSIP: an Italy-led seabed-protection capability project whose six participating Member States are Italy, Germany, Spain, France, Portugal and Sweden — Belgium, though a PESCO member overall, is not among the six named CSIP project participants, so CSIP is an ecosystem context, not a buyer route, for Belgium. [verified — pesco.europa.eu CSIP project page].

Comparator one-liner. We are not another sensor or another minehunter; we are the sovereign, human-gated decision layer that the MIK has publicly asked for and that the rMCM/MAHI sensing surge has 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 replay.

Real gaps (honest).

No MAHI data contract yet — the MAHI Sense sonar/track schema + open-API binding is a scoping spike, not built.
No MIK/e-BO adapter — write-back to the live MIK COP is AS-DESIGNED, unbuilt.
No Belgian-sovereign hosting decision — EU-hosted yes; Belgian-jurisdiction specifics TBD per accreditation.
Legal gate open — solo founder on Stamp-1G cannot sign a paid contract (see §20); MAHI-as-prime is the resolver but unconfirmed.
Sonar-classification confidence is the analytic bottleneck, not AIS attribution — needs a labelled Belgian-waters corpus.
Decline-policing: must hold the civil-security line hard against any pull toward mine-warfare targeting or crew identification.

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

Stage 1 — First contact (warm). Trigger: founder-to-founder relationship with MAHI. Owner: Founder. Activity: send the Pieter-Jan Note note (adapted below). Exit: MAHI agrees a joint scoping session. Deliverable: scheduled session + NDA (founder's own name).

Subject: Edge + sovereign brain — a Belgian seabed-infra play for the EDIP window Pieter-Jan — MAHI senses the seabed (Alpha-8 / MAHI Sense, REPMUS-proven); Nexus Synergy is the sovereign decision/COP layer above it. Belgium's MIK has publicly asked for "AI applications within the MIK" (Defence Committee, 12 Feb 2025) and e-BO's own roadmap names AI anomaly detection as the gap. Two asks: (1) a technical session on the MAHI Sense open API / sonar+track schema to scope a data contract; (2) an honest conversation about MAHI as the Belgian contracting vehicle for a first EDIP/national CMIP discovery — an all-EU Belgian+Irish team is exactly what EDIP's buy-European mandate rewards. — [Founder]

Stage 2 — Free discovery (60-min, adapted agenda). Trigger: MAHI brokers a MIK/Naval-Component intro. Owner: Founder + MAHI. 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 seabed/cable anomaly from detection to close — how many systems, what's the slowest step?"); 0:20 governance/lawful basis (NIS2/CER scope, AI Act high-risk, EU-sovereign model-call requirement, raw-fact-vs-inference traceability); 0:35 stakeholders/budget/timing (who owns the MIK budget; EDIP / CMIP ecosystem / STAR; 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 Belgian North Sea seabed-anomaly (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, 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 + champion. Deliverable/template (filled):

Pilot: Belgian North Sea Seabed-Infra Anomaly-Fusion COP — MIK + MAHI. Sponsor: [MIK/Naval champion TBD] + MAHI. Problem (their words): "we detect with many sensors but can't fuse them into one human-gated anomaly picture across agencies." The one thing we'll prove: fuse AIS + Sat-AIS + MAHI-Sense sonar + Elia telemetry into one COP and reduce time-to-confident-anomaly from X to Y (X/Y baseline measured in week 1). Scope in: globe_rmp + map_ops + Decision Room + 1 cable corridor + MAHI Alpha-8 feed. Out: mine-warfare tasking, biometric ID, any displacement of e-BO's COP. Data/lawful basis: non-personal vessel/sonar 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 EDIP/CMIP-funded; else TBD. After: LOI if criteria met. Funding vehicle: EDIP SME / national CMIP ecosystem / EUDIS.

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 prime); statement of intent; scope; success-criteria reference; named sponsor; timeline/next step; indicative commercials ("to be scoped under EDIP/national procurement"); conditions (funding, accreditation, DPA); non-binding except confidentiality; Declined-List affirmation; 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-as-prime or NewCo on Stamp-4). Owner: MAHI/NewCo + buyer procurement. Activity: EDIP consortium grant or national CMIP 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
1 First contact (MAHI)[##]
2 Free discovery        [##]
3 Scoped demo              [##]
4 Pilot (EDIP/CMIP)           [############]
5 LOI                                     [##]
   * Stamp-4 / MAHI-prime gate ........... [GATE: critical for a PAID pilot]
6 Signed contract                            [######]

Milestones. M1 MAHI data-contract scoping session · M3 scoped demo accepted · M4-M7 pilot · M7 LOI · M7 partner-vehicle gate (MAHI-as-prime confirmed OR founder on Stamp-4) · M9 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 MAHI is the confirmed contracting prime or the founder is on Stamp-4 (≈t_resolve 9 months).

RACI.

Activity	Founder	Warm-intro sponsor (MAHI)	MAHI / partner-vehicle	Buyer champion (MIK/Navy)	Buyer procurement (BE MoD/DG MR)
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

EDIP (European Defence Industry Programme) — €1.5bn 2025-2027 (adopted 8 Dec 2025, signed 17 Dec 2025); consortium grants up to €20m/project; buy-European 35% non-associated-component cap — an all-EU Belgian (MAHI) + Irish (Nexus Synergy) team is squarely advantaged. [verified].
Belgian national — STAR Plan / Strategic Vision 2025 — €34.8bn capacity commitments 2026-2034 (€24.7bn to spend); ~€1.17bn mine warfare; unmanned-systems / cyber / ISR investment lines. [verified].
CMIP RTI ecosystem — Belgian MoD-commissioned feasibility study for a mission-driven critical-maritime-infrastructure-protection innovation ecosystem — the natural national on-ramp. [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, 4, 3, 5, 3, 2, 5} [PRIOR]:

mandate_pull = 4 — (2026-06-05) live dated forcing functions (12-Feb-2025 Defence Committee AI-in-MIK ask; North Sea infra-protection drive; CMIP study; STAR €1.17bn mine-warfare) but not a single named funded line that says "buy a seabed COP this FY".
access_warmth = 4 — (2026-06-05) founder-to-founder MAHI relationship (Pieter-Jan Note) is a genuinely warm Belgian bridge to the Navy/MIK ecosystem; just short of a budget-owner who has offered to co-sponsor.
demonstrability = 3 — (2026-06-05) strong reuse (globe_rmp + Decision Room + AIS/EMODnet) but needs a MAHI Sense data-contract spike before it runs on the buyer's real edge data.
decline_safety = 5 — (2026-06-05) critical-infrastructure resilience, asset/vessel telemetry not person data, weapons-cue/mine-tasking explicitly guarded; no biometric/predictive drift possible.
white_space = 3 — (2026-06-05) e-BO owns the COP and Naval Group the minehunter autonomy, but the cross-agency AI-anomaly fusion layer is genuinely unfilled (e-BO names it as a future gap).
cycle_speed = 2 — (2026-06-05) MoD/EDIP procurement is multi-body; a grant-funded discovery/pilot route exists but a paid contract is slow.
pillar_fit = 5 — (2026-06-05) squarely the action-loop COP core (detect→fuse→gate→task→close over a sovereign map stack).

S1 = 3.76 → P_LOI = 0.55/(1+exp(−1.15·(3.76−2.6))) = 0.435 (≈43.5%) [PRIOR]. Score100 = S1·20 = 75.2 ≈ 75.

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

contractability = 3 — (2026-06-05) MAHI as a Belgian contracting prime is a credible vehicle (founder still Stamp-1G solo otherwise).
funding_to_pay = 4 — (2026-06-05) EDIP €20m/project + STAR mine-warfare + national CMIP are real, accessible, dated funding routes.
procurement_clarity = 2 — (2026-06-05) EDIP consortium + national MoD is navigable but multi-step; not a single sub-OJEU pilot lane.
incumbency_displacement = 4 — (2026-06-05) we sit above e-BO's COP 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.
reference_leverage = 2 — (2026-06-05) first EU logo; no delivered decline-safe reference yet to de-risk.

S2 = 3.12 → P_raw = 0.70/(1+exp(−1.1·(3.12−2.8))) = 0.411 (≈41.1%) [PRIOR].

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

V = 0.10 (today, solo Stamp-1G): G=0.070 → P(Contract|LOI) ≈ 2.9%, P(Contract joint) ≈ 1.3%.
V = 0.45 (co-founder/Dogpatch vehicle): G=0.315 → P(Contract|LOI) ≈ 12.9%.
V = 0.75 (MAHI confirmed prime): G=0.525 → P(Contract|LOI) ≈ 21.6%, P(Contract joint) ≈ 9.4%.
V = 1.0 (Stamp-4 incorporated): G=0.700 → P(Contract|LOI) ≈ 28.8%.

P(Contract) = P_LOI · G · P_raw. MAHI's value, exactly as in the worked examples, 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: high. Derived Score100 = 75 (P_LOI band ≈ 38-48%). This is above the Irish naval-service MAHI row (66.4) — justified because the Belgian buyer has (a) a publicly dated parliamentary AI-in-MIK ask, (b) a confirmed funded national/EU budget environment (STAR + EDIP), and (c) a warmer, in-country MAHI bridge — while sharing the same gate-lift mechanic. Value band: high. ✓

§19 — Commercial

Tier	Scope	Indicative ACV
Tier 1	Single-cell MIK anomaly-fusion COP pilot-to-production (1 sea-basin slice)	€120-240k/yr
Tier 2	Belgian North Sea full seabed-infra COP across agencies + MAHI/rMCM feeds	€600k-1.2m/yr
Tier 3	Belgian-Dutch rMCM multi-domain COP + CISE federation	€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-as-prime or NewCo on Stamp-4), a signed DPA, EU-RESTRICTED isolation accreditation, and a MAHI Sense data-sharing agreement (carving out MAHI'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 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. ⚖️ CONFIRM per-use-case.
X4 — Dual-use export (Reg. (EU) 2021/821). USV-sonar + AIS/comms fusion can classify as controlled. ⚖️ CONFIRM (export counsel).
X5 — Defence procurement (Dir. 2009/81/EC + Art-346 TFEU). Belgium may use negotiated/exempt procedures for security-sensitive contracts — can help or exclude. [verified].
X6 — NATO DIANA exclusion (Ireland non-NATO). Use EU vehicles (EDIP/EUDIS/EDF); 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 (MIK ↔ Defence ↔ Coast Guard ↔ cable/grid operators); decline-policing: hold the civil-security line hard — any drift to mine-warfare targeting or crew ID is fatal and excluded by schema + 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. [verified person; email not public].

The specific ask (two parts):

Technical — a session with MAHI's integration leads (Van den Bergh / Lauwers) on the MAHI Sense open API + sonar/track schema to scope the data contract that feeds the seabed-anomaly COP.
Commercial/structural — an honest conversation about MAHI acting as the Belgian contracting prime for a first EDIP / national-CMIP discovery + pilot, framed as the all-EU Belgian+Irish team EDIP's buy-European mandate rewards — which simultaneously resolves the founder's Stamp-1G legal gate.

(Secondary, post-MAHI: ask MAHI/REPMUS contacts to bridge a MIK / Naval-Component champion, leveraging the public 12-Feb-2025 Defence Committee AI-in-MIK record.)

§22 — Open questions + consolidated Sources

Open questions (do not assert until resolved):

Named MIK / Naval-Component budget-owner and whether the AI-anomaly need has a funded FY line [TBD].
Whether MAHI will act as contracting prime + the written terms [TBD — founder conversation].
MAHI Sense sonar/track schema specifics + data-contract feasibility [TBD — technical spike].
Whether the CMIP RTI ecosystem study yields a procurement lane Nexus Synergy can enter [TBD].
Belgian-jurisdiction hosting/accreditation specifics for EU-RESTRICTED [TBD].
Exact EDIP consortium eligibility for a pre-incorporation Irish entity (min-3-MS rule via MAHI consortium) [TBD — confirm].

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

Belgian-Dutch rMCM / M940 Oostende — naval-group.com (first mooring Zeebrugge); navalnews.com (2025-11); euro-sd.com (2025-03); thedefensepost.com (2026-03). [verified]
MAHI Alpha-8 / MAHI Sense / REPMUS — tectonicdefense.com; maritime-executive.com (ONE SEA membership); natlawreview.com (2026-03-02 unveiling). [verified]
NATO REPMUS / Dynamic Messenger 2025 — mc.nato.int; bairdmaritime.com; armadainternational.com (3,800 participants, 260 systems, 22 nations). [verified]
MIK Zeebrugge / e-BO / Barco — ebo-enterprises.com (2020 MoD tender, GIS COP, AI-anomaly future need); kustwacht.be (MRCC/MIK structure); barco.com (OpSpace). [verified]
12-Feb-2025 Defence Committee / De Winter AI-in-MIK ask — bluecluster.be. [verified]
Belgium North Sea infra protection — belganewsagency.eu (2026-06-02, Verlinden); armyrecognition.com (Castor/Pollux, 3rd vessel by 2027, Baltic Sentry, SMCMG). [verified]
Marine Spatial Plan 2026-2034 / Elia — belganewsagency.eu; selinc.com. [verified]
STAR Plan / Belgian defence budget — dsei.co.uk (€33bn); defensenews.com (2025-07; €1.27bn 3rd frigate); euro-sd.com (2025-02). [verified]
EDIP — consilium.europa.eu (€1.5bn, 8-Dec-2025 adoption, €20m/project, 35% cap); europarl.europa.eu (signed 17-Dec-2025). [verified]
PESCO CSIP — pesco.europa.eu CSIP project page (Italy-led; six participants IT/DE/ES/FR/PT/SE; Belgium not among the named CSIP participants). [verified]
EU AI Act Art 5 (applicable 2-Feb-2025; guidelines 4-Feb-2025) — artificialintelligenceact.eu; ec.europa.eu AI Act Service Desk. [verified]
CMIP RTI ecosystem study — bluecluster.be CMIP ecosystem study. [verified — existence; detail PDF not text-extractable]

SQL

43 lines

-- USV/AUV sonar event from an uncrewed asset (MAHI Sense / rMCM toolbox), org-scoped + RLS.
CREATE TABLE synergy.usv_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,                       -- 'MAHI-ALPHA8-01' | 'M940-AUV-2'
    event_at        timestamptz NOT NULL,                -- 14:02:18Z
    cable_segment   text,                                -- 'C-7' (KP-19)
    object_len_m    numeric(6,1),                        -- 2.1
    scour_width_m   numeric(6,1),                        -- 2.1
    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                       -- MahiSenseIngest-v1.2 attribution
);
ALTER TABLE synergy.usv_sonar_event ENABLE ROW LEVEL SECURITY;
CREATE POLICY org_isolation ON synergy.usv_sonar_event
    USING (org_id = current_setting('app.current_org_id')::uuid);

-- Seabed-infrastructure contact = the cross-agency alert entity; the resilience->action boundary lives here.
CREATE TABLE synergy.seabed_contact (
    id                  uuid PRIMARY KEY DEFAULT gen_random_uuid(),
    org_id              uuid NOT NULL,
    cable_segment       text NOT NULL,                   -- 'C-7'
    vessel_mmsi         text,                            -- anonymised in the shared picture
    flag_state          text,                            -- 'PAN'
    sonar_event_id      uuid REFERENCES synergy.usv_sonar_event(id),
    ais_gap_minutes     numeric(6,1) NOT NULL DEFAULT 0, -- 22.0
    loiter_hours        numeric(6,1) NOT NULL DEFAULT 0, -- 11.0 inside the 1nm zone
    in_protection_zone  boolean NOT NULL DEFAULT false,  -- 1nm polygon test
    grid_dip_observed   boolean NOT NULL DEFAULT false,  -- Elia telemetry dip y/n
    anomaly_score       numeric(4,3) NOT NULL,           -- 0.88 (multi-source concurrence)
    proportionality     numeric(4,3) NOT NULL,           -- P = 0.90 (CER/NIS2 resilience necessity)
    disposition         text NOT NULL DEFAULT 'monitor'
                        CHECK (disposition IN ('monitor','vhf_query','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 request) without a recorded human gate.
    CHECK (disposition IN ('monitor','vhf_query') OR gate_id IS NOT NULL)
);
ALTER TABLE synergy.seabed_contact ENABLE ROW LEVEL SECURITY;
CREATE POLICY org_isolation ON synergy.seabed_contact
    USING (org_id = current_setting('app.current_org_id')::uuid);

Python

38 lines

def assess_seabed_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)          # PAN flag, loiter 11h
    contact.satais = sat_ais_crosscheck(mmsi)                        # Copernicus/EMSA self-report check
    contact.grid_dip = elia_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')
    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.94, proport=0.90, lawful=0.95)   # P = 0.90
    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 — coast-guard challenge + USV re-survey; no weapons cue.
    write_back("mik_cop", requesting_org,
               PatrolTask(asset="Castor", task="vhf_query+ais_identity_request"))
    write_back("rmcm_tasking", "naval_component",
               UsvSurveyOrder(asset="Alpha-8", target="C-7/KP-19", mode="re-survey"))
    write_back("nis2.cable_incident.lodge", "elia",                 # NIS2 Art 23 significant-incident
               Nis2Lodgement(cable="C-7", 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 + Alpha-8 re-survey confirm/deny scour cause; UNO close.

YAML

41 lines

workflow: belgium_seabed_infra_protection_loop
trigger:
  on_event: usv_sonar_event.created   # MAHI Sense / rMCM AUV side-scan
tenant_scope: app.current_org_id
nodes:
  - id: enrich_correlate
    skill: correlate_sonar_to_ais
    inputs: { sonar_event: $trigger.event, sat_ais: copernicus_emsa, grid: elia_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                   # MIK duty officer + Navy 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, predictive_policing]
    on_refuse: { goto: log_refusal }
  - id: task_patrol
    skill: write_back_mik_cop
    inputs: { asset: Castor, task: "vhf_query+ais_identity_request" }
    depends_on: decision_room_gate
  - id: task_usv_resurvey
    skill: write_back_rmcm_tasking
    inputs: { asset: Alpha-8, target: "C-7/KP-19", mode: re-survey }
    depends_on: decision_room_gate
  - id: lodge_nis2
    skill: nis2_cable_incident_lodge
    inputs: { cable: C-7, operator: elia, 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_usv_resurvey]
audit: { provo: true, merkle_anchor: rekor, retention: 7y }

+--------------------------------------------------------------------------------------------------+ | Belgian Seabed-Infrastructure RMP - Navy + MIK Zeebrugge (CesiumJS-globe) | +-------------------------------------------------------------------+------------------------------+ | . - '' - . BELGIAN NORTH SEA (Prinses Elisabethzone) | TRACKS (sorted: anomaly) | | / o ----._ \ wind cluster + interconnector + fibre cables| M/V contact PAN flag | | | [!] AIS gap | EMODnet bathy -34m :: IHO S-101 ENC | AIS gaps 22m, loiter 11h | | | M/V contact | M/V contact (PAN flag, AIS gaps 22min) | over cable C-7 + wind C | | | speed 3kn 11h| loiter 11h astride cable corridor C-7 | USV sonar event (Alpha-8) | | \ __X cable C7_/ USV sonar: seabed scour @ KP-19 (drag) | KP-19 seabed scour 2.1m | | \ '. ____ .' / Alpha-8 USV side-scan: object 2.1m fresh | class: anchor_drag .84 | | ' - x__ - ' Elia telemetry: nominal (no MW dip yet) | GRID telemetry (Elia) | | Camera {lat 51.62 lon 2.81 alt 14km} CesiumJS-globe | interconnector nominal | | Concurrence: AIS gap + USV sonar scour + loiter-in-zone | watch: cable C-7 segment | | -> ANOMALY 0.88 :: HUMAN GATE before any tasking | [#] CISE share: MIK cell | | | gate: coast-guard challenge | | | not weapons cue (civil) | +-------------------------------------------------------------------+------------------------------+ | EMODnet bathy + IHO S-101 + AIS mux + Sat-AIS Copernicus + MAHI Sense USV sonar :: MIK fusion ON | +--------------------------------------------------------------------------------------------------+

+------------------------------------------------------------------------------------------------------+ | Belgian North Sea Surface-Response Picture (Navy + Coast Guard Centre / MIK) | +--------------------+---------------------------------------------------------------------------------+ | LAYERS | MAP ========================================================================== | | [x] Cable C-7 | Belgian North Sea 51.62N 2.81E :: cable C-7 @ KP-19, wind cluster C edge | | [x] 1nm zone | M/V contact [!] loiter 11h inside 1nm protection zone, AIS gaps 22 min | | [x] Wind clstr C | USV side-scan: fresh seabed scour 2.1m -> attributed to loiter track | | [x] AIS tracks | Elia interconnector telemetry nominal (no power dip) -> resilience watch | | [x] Sat-AIS | cable C-7 ===?=== scour @ KP-19 1nm zone polygon wind cluster C | | [x] USV sonar | > Castor (P902) VHF Ch16 query + AIS-identity request | | [x] Patrol (2) | > M940 Oostende on-station, launch Alpha-8 USV for KP-19 re-survey | | [ ] Alpha-8 USV | > Coast Guard Centre / MRCC Ostend notified (safety co-pillar) | | ETA panel: | ROE: civil-security, voice challenge first, scheduled inspection | | Castor 55m query | NO weapons cueing :: NO mine-neutralisation tasking in this COP | | M940 on-station | | | Alpha-8 re-survey | | +--------------------+---------------------------------------------------------------------------------+ | INCIDENTS: M/V loiter+sonar scour :: Castor VHF query :: Alpha-8 re-survey :: MIK CISE share EE+NL | +------------------------------------------------------------------------------------------------------+

[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 Surface-Response] -> [BDA] -> [Close]

▣ EU-RESTRICTED · TLP:AMBER · CIVIL-SECURITY ▣ Belgian Seabed-Infra COP — MIK Zeebrugge tenant ⊟ Op-coordination persona [L3 EuroLLM] Reco: anomaly 0.88 (loiter 11h + AIS-gap 22m + USV sonar scour 2.1m @ C-7/KP-19). Task Castor (P902) VHF Ch16 challenge + AIS-identity request; M940 Oostende launch Alpha-8 USV for KP-19 re-survey; request boarding party on standby. ⊟ Proportionality persona [L3 EuroLLM] P = 0.90 (N=0.94 necessity, P=0.90 proportionality, L=0.95 lawfulness). Cable C-7 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. This is critical-infrastructure RESILIENCE, not interdiction. Keep it to a VHF challenge + a scheduled, announced inspection; escalate only on refusal. ⊟ Devil's advocate persona [L3 EuroLLM] Counter: a 2.1m scour + 11h loiter also fits an innocent anchor-watch in bad weather, or a trawl-net snag on the cable protector. Don't infer hostile intent. Inspect, don't accuse. ⊟ Maritime domain expert persona [L3 EuroLLM] Scour width 2.1m with sustained loiter is more consistent with anchor-drag (alpha=0.84) than trawl (which shows narrower, intermittent marks). Recommend Alpha-8 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 alternative collapse the op-coordination reco's "boarding party on standby" into a narrower disposition: VHF challenge + announced scheduled inspection + Alpha-8 re-survey. Boarding is NOT authorised at this gate. DB CHECK confirms: disposition 'scheduled_inspection' requires gate_id -> present. [/dual-control sign - MIK duty officer] [/dual-control sign - Navy watch officer] VERDICT: ACCEPT (narrowed) P=0.90 2-of-2 quorum :: weapons cue / mine-tasking REFUSED by guard.

Role

Named / TBD

Notes

Edge partner / contracting gate-resolver

Pieter-Jan Note, Co-Founder & CEO, MAHI

[verified person]; founder's direct warm relationship; MAHI as the Belgian contracting prime lifts the legal gate (V 0.10→0.75)

Technical integration counterpart

Bertold Van den Bergh / Quinten Lauwers (MAHI)

[verified] — MAHI Sense open API / track + sonar schema for the data-contract spike

MIK / Coast Guard champion

[Named contact TBD] — via the 12-Feb-2025 Defence Committee thread (Frigate Captain De Winter named publicly)

the AI-anomaly need is publicly on record

rMCM / Naval Component

[Named contact TBD]

M940 Oostende programme office

Incumbent COP integrator

e-BO Enterprises (+ Barco)

sit above, integrate — do not displace the GIS COP

Grid/cable essential entity

Elia (grid) + cable operators

NIS2 §23 write-back recipient

Buyer procurement

Belgian MoD / DG MR (Material Resources)

EDIP / national CMIP ecosystem route

Stage \ Month M0 M1 M2 M3 M4 M5 M6 M7 M8 M9 1 First contact (MAHI)[##] 2 Free discovery [##] 3 Scoped demo [##] 4 Pilot (EDIP/CMIP) [############] 5 LOI [##] * Stamp-4 / MAHI-prime gate ........... [GATE: critical for a PAID pilot] 6 Signed contract [######]

Activity

Founder

Warm-intro sponsor (MAHI)

MAHI / partner-vehicle

Buyer champion (MIK/Navy)

Buyer procurement (BE MoD/DG MR)

First contact

R/A

—

Discovery

R/A

Demo

R/A

Pilot delivery

A/R

LOI

Contracting vehicle

A/R

Signed contract

A/R

Tier

Scope

Indicative ACV

Tier 1

Single-cell MIK anomaly-fusion COP pilot-to-production (1 sea-basin slice)

€120-240k/yr

Tier 2

Belgian North Sea full seabed-infra COP across agencies + MAHI/rMCM feeds

€600k-1.2m/yr

Tier 3

Belgian-Dutch rMCM multi-domain COP + CISE federation

€2.4-4.8m/yr