VIGIL CONSILIUM Search
Context. Not headlines.
Standing Watch · Demonstration scope

Baltic Maritime & Critical Infrastructure Risk

Damage to Baltic cables and pipelines, the attribution that follows it, and the civilian systems that depend on them. A demonstration scope: it shows how Standing Watch organises existing Vigil monitoring around a defined exposure, on the public record, with no organisation represented.

How Standing Watch works
Questions
4
Module
NATO Eastern Flank
Cadence
Weekly
Scope reviewed through
Current cycle
Material changes
0

Scope definition

Exposure

An organisation whose operations, cover or continuity depend on cross-border physical links in the Baltic — a telecommunications or energy operator, an underwriter of subsea or marine risk, a corporate continuity function with Nordic-Baltic exposure, or a policy function following how states respond to damaged infrastructure. The question such a reader keeps having to answer is not whether an incident was reported, which reporting answers, but whether a link came back, how fast, whether traffic rerouted, and whether any authority has established what caused it.

Why these questions together

The scope is built on a single, hard separation that most coverage of this subject collapses: DAMAGE, CAUSE, DELIBERATE INTERFERENCE, LEGAL FINDING and STATE ATTRIBUTION are five different things arriving at five different times, and a reader who treats them as one will be wrong in both directions. Fifteen named assets have been damaged on nine occurrence days since September 2022. One case was closed by prosecutors as an accident. One has charges against three ship's officers, a dismissal on jurisdiction, an appeal that restored it, and no merits hearing. Not one has reached a state attribution. The four questions read the damage, the ladder, the civilian dependency and the protective response, and the scope's whole value is that it holds them apart.

What this scope does not answer

  • It publishes no cable or pipeline route geometry, no landing stations and no damage coordinates. Occurrences are filed in broad sea areas, which is why the module authors no critical-infrastructure markers at all; publicly searchable is not a reason to publish.
  • The recorded series counts DAMAGE, independently of cause or attribution. Fifteen asset-records across nine occurrence days is not fifteen incidents and is not a count of sabotage.
  • A month is a covered zero only from October 2023, when both the operator sweep and the authority sweep were run. The twelve months before that are inside the series range and are not covered; their empty bins mean no coverage.
  • It states no repair capability, standing capacity or restoration time for any named live link. Individual repairs are recorded as operators reported them; no state or operator publishes standing capacity and none is inferred.
  • It does not attribute. Where an authority has established something, the record says what act established it and at what level; where nothing has been established, it says that instead — which is the current position in every undersea case.
  • It is not comprehensive Baltic monitoring. It reads cross-border physical links and the institutions that answer damage to them, from public sources, on a weekly review cycle. It is not continuous, it is not comprehensive maritime intelligence, and it carries no privileged access.

Watch on NATO Eastern Flank 4 of the module’s active questions are in scope; membership is an editorial decision, recorded on the scope.

Latest review Cycle of . Outcomes are the questions’ own review outcomes, counted; a question not reviewed in the cycle is shown as pending.

Questions reviewed
4 of 4
Baseline
4

Every active question was reviewed in the cycle of 2026-09-21. 4 questions established their baselines.

What changed No question in scope recorded material movement in the current cycle.

A quiet cycle is a legitimate result. The questions below record what each review checked and found unchanged.

Baseline
01 Is the exposure of Baltic undersea infrastructure changing, and does attribution ever arrive?02 Is hybrid pressure against allied societies changing in form, and does attribution follow it?03 Are the civilian systems collective defence depends on being strengthened?04 Is Nordic accession becoming integrated command, basing and forward presence?Opened this cycle; its first review against the baseline is due in the next.

Questions under watch 4 canonical Watch questions, in scope order, spanning Physical damage and response · Attribution and legal process · Civilian dependency · Northern protective arrangements. The record is the question’s own; the relevance note is the scope’s.All Watch questions

  1. Physical damage and responseInfrastructure

    Is the exposure of Baltic undersea infrastructure changing, and does attribution ever arrive?

    Confirmed damage to cables and pipelines, the protective response, and how far each case climbs the attribution ladder.

    BaselineModerate confidence

    Current condition as of

    Fifteen named assets have been damaged on nine occurrence days since September 2022.

    Observables 6 named

    1. A state attribution by a competent authority in any case
    2. Any case moving up the attribution ladder
    3. An official finding that damage was not deliberate

    All 6 observables

  2. Attribution and legal processPolitical

    Is hybrid pressure against allied societies changing in form, and does attribution follow it?

    Sabotage, arson, devices in transit networks and interference, and the legal acts that follow them.

    BaselineModerate confidence

    Current condition as of

    The North Atlantic Council stated in May 2024 that Russia is conducting hybrid activities against Allies, naming seven of them.

    Observables 5 named

    1. A further collective statement by the Council
    2. A charge converting to a verdict
    3. An incident of a form not previously recorded on flank territory

    All 5 observables

  3. Civilian dependencyInfrastructure

    Are the civilian systems collective defence depends on being strengthened?

    Energy and communications continuity, transport and regulatory host support, and population warning across the flank.

    BaselineModerate confidence

    Current condition as of

    Civilian systems across the flank are functioning.

    Observables 5 named

    1. Repair times and redundancy on damaged cross-border links
    2. Activation of national public-warning systems
    3. Publication of host-nation support or mobility arrangements

    All 5 observables

  4. Northern protective arrangementsMilitary

    Is Nordic accession becoming integrated command, basing and forward presence?

    Command arrangements, forward presence and infrastructure in the northern arena since Finnish and Swedish accession.

    BaselineModerate confidence

    Current condition as of

    Finland acceded in April 2023 and Sweden in March 2024.

    Observables 5 named

    1. Growth or change in the Mikkeli land component command
    2. Publication of the Finland formation’s garrison, lead unit or headquarters
    3. Published air or maritime integration arrangements in the north

    All 5 observables

Activity context The recorded series the questions sit beside — a count of dated, sourced occurrences at published markers, per week, never an effect or a live picture. The Map surface carries the full series, the key developments and the inspector.Map — NATO Eastern Flank

  1. Damage to Baltic subsea cables and pipelines

    Confirmed physical damage to named subsea cables and pipelines in the Baltic and its approaches, counted independently of attribution.

    1. 06 Jul 2026 to 12 Jul 2026: 0 records.
    2. 13 Jul 2026 to 19 Jul 2026: 0 records.
    3. 20 Jul 2026 to 26 Jul 2026: 0 records.
    4. 27 Jul 2026 to 02 Aug 2026: 0 records.
    5. 03 Aug 2026 to 09 Aug 2026: 0 records.
    6. 10 Aug 2026 to 16 Aug 2026: 0 records.
    7. 17 Aug 2026 to 23 Aug 2026: 0 records.
    8. 24 Aug 2026 to 30 Aug 2026: 0 records.
    9. 31 Aug 2026 to 06 Sep 2026: 0 records.
    10. 07 Sep 2026 to 13 Sep 2026: 0 records.
    11. 14 Sep 2026 to 20 Sep 2026: 0 records.
    12. 21 Sep 2026 to 21 Sep 2026: 0 records.

    Recorded events · each resolves to a source · weekly bins · 26 Sep 2022 → 21 Sep 2026

    Newest week
    0
    12 weeks
    0
    Full series
    15
    Reviewed

    Bears on01 Is the exposure of Baltic undersea infrastructure changing, and does attribution ever arrive?

    Open on the map

  • 0
  • 1–2
  • 3–5
  • 6–10
  • 10+

System access The questions are not floating text. They run through records the module maintains, and they are read on four surfaces. Listed below: the surfaces, and every record at least two of the scope’s questions share.

Records the scope’s questions share named by two or more questions

Means and systems 1

Vigil analysis 1

Meaningful-change notice What a notice between weekly reviews would contain, composed from this cycle’s own material changes. An example of the concept — nothing here is sent, and no delivery system exists.

ExampleBaltic Maritime & Critical Infrastructure RiskIssued only on movement observed, observable met or assessment changed. A quiet review stays in the weekly state.

No notice this cycle. Every question in scope was reviewed and none recorded material movement — a result the weekly state carries, and one a notice would only repeat.

What this demonstrates This public scope shows how Vigil organises a defined set of standing questions around one exposure. The records under it remain part of the public corpus.

Public Vigil

Vigil chooses the questions and publishes the corpus freely.

Every Watch question, its observables, its ledger and its sources stay public, including the reviews that found nothing moved. Nothing shown in a scope is withheld from Watch.

Professional monitoring

The organisation defines which questions matter to its exposure. Vigil maintains that scope.

The value is the customised scope, the sustained attention, a defined review responsibility, interpretation relevant to the exposure, and delivery of the material changes between reviews. Not access to information already published.

Exists
The public demonstration scope. The weekly review that already produces every figure on it. This contact channel.
Built, not launched
Vigil Professional: a personal research workspace over this corpus — monitoring, evidence tracing, comparison, conditional scenarios, briefing production and saved work — with accounts, reviewed-change notifications and a published price. It is not on sale, nothing can be charged, and no part of the public corpus is behind a payment.
Under validation
Organisation-specific scopes: questions Vigil does not already publish, delivery to a team, cadence beyond weekly, and what any of that would cost. None of it is built, priced or sold, and none of it is included in the personal subscription above.
Not built
Shared team workspaces, an API, single sign-on. Each waits for actual demand, not for a roadmap.

Work with a scope like this in Vigil Professional

Define a Standing Watch scope

Tell Vigil which geopolitical questions your organisation has to keep under review. A written reply from the editor; no form, no call booking, no price list.

Standing Watch All Watch questions How Watch works