VIGIL CONSILIUM
Context. Not headlines.
Vigil Professional · walkthrough

One record, in full

This is a real, published Professional record — not a mock-up, not a screenshot and not a simplified version. It is one of 445, shown in the order a subscriber reads it, with the chain it sits in above and below, and with the surfaces they read it on. Everything on this page is free to read and always will be.

What this page is. One observable record of 445, published openly so that the depth can be checked rather than claimed. The other 444 are behind the subscription; this one is not, on purpose. Nothing here is fabricated for demonstration and nothing is simplified: if the record is reviewed next week, this page changes with it. For the short guided tour of what Professional is for, start at the walkthrough; this page is its depth.

1 · The exposure

A Standing Watch scope — a named exposure held across several questions at once, narrower than a module and wider than a single question.

Standing Watch

Taiwan Civil Resilience

Whether Taiwan's communications, energy and import systems keep working under sustained coercion and access pressure — read on published requirements, holdings, incidents and thresholds.

An organisation whose operations, obligations or planning depend on civilian systems inside Taiwan continuing to function while pressure is applied below the threshold of attack — an operator, insurer, lender or manufacturer with Taiwanese exposure, a continuity or country-risk function, a government or agency with people and assets on the island. The questions it has to keep checking are not whether an incident occurred, which reporting answers, but whether the conditions that govern continuity have moved: what the communications layer does when data is degraded, what the energy reserves actually are per fuel, whether what arrives keeps arriving, and whether the instrument that would constrain access has been used rather than described.

4 questions in scope · reviewed weekly · 6 stated limits

A subscriber opening this scope sees each of its questions with the mechanism it carries, what the scope depends on, and — set out at length — what the scope cannot tell them. We are going to follow one of its questions down.

2 · The question, which is free

Public Watch. Anyone can read this, today, with no account.

Public Watch question

Can communications and civil systems function under disruption?

The August 2026 throttling drills cut mobile data to about one per cent of capacity for roughly 17 million people and showed which layers survive: voice, SMS and emergency cell broadcast kept working; payments, banking, ticketing and app authentication did not. No new undersea-cable or grid incident has been identified since the drills, and attribution for cable incidents has been contested in every case on record.

Condition as of 2026-09-06 · 5 named observables · last reviewed 2026-10-18

Read it in Vigil Research

Public Watch names the observables — what evidence would bear on the question — and stops there, because that is what a reader needs in order to understand the assessment. One of the named observables on this question is Payment and authentication continuity under throttling. What follows is what Professional adds beneath it.

The Taiwan Strait module in Monitor, with the question “Can communications and civil systems function under disruption?” selected: its latest review outcome and date printed in Watch’s own words, it has five observables, and the inspector prints the current reading beside the module’s What moved list, its geography, its one recorded-activity series and the days of the cycle entries were written on.
The same question, in Monitor: its latest review, dated and in Watch’s own words, beside the module’s geography, its recorded activity and the days of the cycle.

3 · The Professional record

This is the paid layer. This is all of it, for this record.

Observable record · Vigil Professional

Payment and authentication continuity under throttling

The layer that failed in August: whether any subsequent drill or measure keeps payments, banking or ticketing working at one per cent of capacity.

What is being checked

Whether any measure, rule or subsequent drill keeps retail payment, banking authentication or ticketing working at the data capacity the August rounds imposed. The August evidence separates two layers cleanly: the bearers the state controls held, and the commercial services layered on data did not. This observable reads the second layer, and only a measure or a repeat drill can move it.

Current reading as of 2026-09-13

FACT

Failed under test, and unaddressed since. On 10 and 13 August 2026 mobile data was reduced to roughly one per cent of capacity for about seventeen million people, some 73 per cent of the population, for a scheduled half hour. Voice, SMS, emergency calls and cell-broadcast alerts were kept running by design. Reporting from the central round records that retailers were unable to take electronic payment, that official websites and online services were unreachable, and that the national alert itself directed recipients to look up guidance online. No measure addressing that has been identified since.

What has held

  • The layers that held in August are the ones built on the most robust bearers — voice, SMS, emergency calls and cell broadcast — and they were deliberately excluded from the throttling rather than tested by it.

Evidence 3 dated entries, newest first

2026-09-13bears on it without direction

No further drill announced and no civil-systems measure identified in the review window.

ITEM Taiwan Strait developments — 13 September 2026 · 2026-09-13 · sources: taiwan-ncc, cna-focus-taiwan

2026-08-13bears toward the observable being met

The northern round at 256 Kbps, which confirmed the same split between excluded bearers and data-dependent services on a second population.

EVENT The throttling exercise repeats across northern Taiwan · 2026-08-13 · sources: taiwan-ncc, cna-focus-taiwan

2026-08-10bears toward the observable being met

The central round — the condition imposed, the exclusions granted, and the commercial services reported as unusable during it.

EVENT Taiwan runs its first mobile-network throttling exercise · 2026-08-10 · sources: taiwan-ncc, cna-focus-taiwan, taipei-times

Every entry names the canonical record it rests on. In the product each of those is a link, and following one lands on the development, event or brief itself with its own sources and dates.

What would constitute movement 4 conditions

  1. A regulator or ministry measure requiring an offline or low-bandwidth fallback for payment or authentication.
  2. A subsequent drill in which retailers are reported taking electronic payment at throttled capacity.
  3. A bank, payment operator or transport authority publishing a continuity arrangement for the same condition.
  4. A drill extended to the fixed-line network, which the two rounds did not touch.

Stated in advance, so that a later change can be checked against what Vigil said would count rather than explained after the fact. Vigil never states that it expects any of them, and no likelihood or horizon is attached to any entry.

What this reading cannot establish 3 limits

  • The drills throttled the mobile network only. Fixed-line and enterprise connectivity were not degraded, so the exercise does not establish what a payment network does when every path is constrained.
  • The reported effects come from journalism rather than from an operator or regulator measurement, and no party has published a count of transactions that failed.
  • A scheduled half-hour with the robust bearers protected is the mildest version of the condition, and nothing here is read as establishing behaviour under a longer or unannounced one.

Review ledger

  • 2026-10-04 · No material change — Checked with the parent review. No drill or measure keeping payments, banking or ticketing working under throttling was reported in the window; the layer that failed in August remains untested since.
  • 2026-09-27 · No material change — Checked with the parent's review. No measure, rule or repeat drill addressing payment or authentication continuity at throttled capacity was identified in the window.
  • 2026-09-15 · Baseline — Record opened by the Taiwan propagation pass. This is the clearest instance in the corpus of an exercise producing a negative finding about a civilian system, and the record keeps the finding at the layer it was observed in.

Checked 2026-10-18 on the parent question's review. It has not changed since it was opened, and the ledger says so rather than leaving the reader to guess.

The Investigate workspace with the query “payment continuity”, the walkthrough’s own observable record selected, and the evidence chain beside it naming the parent question, the observables that check it, this record, and the registry sources it cites.
The same record, reached by query. Selecting it opens the chain beneath it without leaving the page.

4 · The system it runs on

The question names cables, ports and a strait. Those are records too, and Professional works them as a system.

Supply system · Economy & Logistics

Maritime trade routing and undersea connectivity

A very large share of world shipping passes through here, and so does the island's connection to the internet.

8 nodes in the record’s authored order · 4 documented disruptions · assessed as of 2026-09

In the Economy & Logistics workbench this record is a journey: its nodes in their authored order, banded origin, process, movement and delivery, traced upstream or downstream from any node, with its documented disruptions beneath. Select a node and its record opens; select an edge and the inspector says why Vigil connects the two. The arrows are schematic — an order the record states, never a route it has not established — and no width, length or arrow encodes a quantity. The Handbook chapter shows all six instruments.

The Flows instrument on Taiwan’s maritime trade and undersea connectivity in the presentation state: the supply system’s nodes in their authored order as a left-to-right journey of role runs, each banded by role and marker type and joined by schematic arrows, with the record’s documented disruptions in a strip beneath and the status line giving its assessment date, review date and confidence.
The walkthrough’s own module: the supply system the connectivity question runs on, drawn as the record’s authored order — an order, not a route.

5 · The civilian system it tests

The question is about whether communications keep working for people. That system is a record as well, and Professional works it with what it rests on.

Civilian system · Humanitarian & Resilience

Communications and warning continuity

Fifteen international cables, the layered redundancy behind them, the services that stop when data does, and the alert system meant to work when everything else is degraded.

Condition: Operating; redundancy being built (as of 2026-08) · rests on 1 other service · 4 resilience measures — 2 in progress, 1 in place, 1 tested or used

In the Humanitarian & Resilience workbench this record is a service lane: what it rests on — the energy system — on the left, the published supply and cable records it runs through, the service itself with its resilience measures, and what rests on it on the right. The measures stand on the rung their sources support, so the redundancy still being built is never drawn as capacity in place, and the August warning drill is recorded as what it tested, not as proof that warning works. The Handbook chapter shows all six instruments.

The Services instrument on Taiwan’s communications and warning continuity in the presentation state: what it rests on (energy and grid continuity, the maritime trade and undersea connectivity supply system, the sea-access system), the published nodes that supply system names, the service with its resilience measures — cable designation, satellite and microwave redundancy, inter-island cables, public warning tested in the August drills — and what rests on it.
The walkthrough’s own civilian system: communications continuity with what it rests on and its measures, each on the rung its sources support.

6 · The force it tests

A force is a record as well — organised, equipped and sustained in the records’ own words — and Professional works it from its chain of command to what keeps it operating. This one is from another module, because it is the clearest connected example.

Force · Forces & Operations

Russian Ground Forces

Combined-arms armies providing the bulk of the invasion's manpower.

5 subordinate records in the Atlas · 7 documented equipment claims · 3 sustainment dependencies · status as of 2026-06

Sustainment dependency · documented · confidence high · as of 2026-07

Russian rear-area sustainment

The ground force's operating range is the range a railhead can support; road transport exists to bridge railhead to unit, as the sustainment record states.

8 nodes in the record’s authored order · 3 documented disruptions · assessed as of 2026-07

In the Forces & Operations workbench this force is a sustainment lane: industrial base, strategic rear, depots and repair, transport, operational logistics, then the formation — each card an Economy & Logistics record the force’s own record names, with the edge’s basis on the card and the edges it inherits from the command above it markedvia. The edge above is the record’s own claim: a dependency, in the record’s words, with its basis, confidence and date — never a route, a capacity or a stock. From the inspector, Open in Economy & Logistics hands the dependency to the Flows instrument, where the sustainment record is drawn once, as its authored order of nodes, and where it is owned. Nothing on either canvas is a strength, a position or an arrow of advance. The Handbook chapter shows all six instruments.

The Sustainment instrument on the Russian Ground Forces in the presentation state, drawn as one force lane: Industrial base (the defence-industry system the Armed Forces of the Russian Federation author a dependency on, marked via that command), Strategic rear (the Russian strategic rear system, an assessed dependency), Depots · repair, Transport · networks (the military logistics system, an assessed dependency), Operational logistics (Russian rear-area sustainment, a documented dependency, and the refining-and-fuel record inherited via the parent, assessed) and Formation (the Ground Forces); each card carrying the edge’s basis as a tag, and a row of counts beneath — own sustainment edges, inherited from the chain, industrial records, logistics records, documented.
What keeps a formation operating, read from Economy & Logistics records the force’s own record names: a dependency with its basis on each card, inherited edges marked via the command that authors them. A dependency, never a route, a capacity or a stock.

7 · How it connects

Steps 2, 4 and 5 are three records. Network shows the references that join them — and says what each one is.

  1. Monitoring · authored on Can communications and civil systems function under disruption?, in connections.logistics[]

    Can communications and civil systems function under disruption? Bears on Maritime trade routing and undersea connectivity

    A Watch question, system or industry record names this record as bearing on a monitored question.

    Does not establish: Not a claim that the two are connected in the world, and not an alert. Network is not a detection engine.

  2. Reference · authored on Communications and warning continuity, in logistics[]

    Communications and warning continuity Runs through Maritime trade routing and undersea connectivity

    One record names the other in a reference list — an analysis, a relationship’s context, a place a record names.

    Does not establish: A reference, not a claim of a material connection. It shows where to read further.

  3. Recorded dependency · authored on Communications and warning continuity, in depends[]

    Communications and warning continuity Depends on Energy and grid continuity

    A dependency the record states, with its basis — documented (a published source states it) or assessed (Vigil infers it and says so).

    Does not establish: Not a measure of how much depends, and not evidence that a disruption on one side has occurred or would propagate.

Opened in Network, the question sits at the centre of the canvas with the records its own fields name around it, and every line answers the same two questions: what does this line mean, and which record states it? The first line above is a monitoring line — the question names the supply system as something it bears on — and the second a reference: the civilian system names the supply system it runs through. Neither is a claim about structure in the world, so path tracing uses them only when the reader allows those kinds of line; with them allowed, the documented path from the question to the civilian system is the first two lines. A path is a chain of references, not an explanation: none of these lines says that a disruption on one record would reach another, and nothing on the canvas is weighted or scored. In the public Explore view, View connectionsdraws the same lines around any record in one module; theNetwork chapter shows what the workbench adds.

The Network workbench centred on the Taiwan Strait Watch question “Can communications and civil systems function under disruption?”: the question in amber at the centre of the canvas, and around it the records its own fields name — Taiwan and the People’s Republic of China, the coast guard and communications administration, Keelung, Hualien and Penghu, the first island chain, a grey-zone campaign, civilian-system and economic objects, related questions, events and the Japan–Taiwan relationship record — each drawn the same size with its kind’s outline and icon, joined by lines whose pattern gives their kind. The supply system “Maritime trade routing and undersea connectivity” is selected and outlined in amber; the inspector beside the canvas reads it: its kind and module, 30 recorded lines, the actions to show more, isolate, centre, trace and open it in Economy & Logistics or Investigate, and its recorded connections grouped by kind, starting with its route nodes, each with a Basis button. Because a record other than the centre is selected, it and its own lines are brought forward and the rest of the canvas is faded but still drawn and named; the line above the canvas gives the records and lines on it, says what is brought forward, how many names are held back where they would overlap, and offers to clear the focus.
One investigation: the question at the centre, the records its fields name around it, the inspector on the selected record with every recorded line grouped by kind. Placement and size measure nothing; every line is one reference a record makes.

8 · What cites it

Records are not islands. This one is read by a scenario template.

Scenario template

International cables out of service for a stated period

If a stated number of Taiwan's international cables were out of service for a stated period, which recorded dependencies are engaged, what does the record credit as an alternative, and what does the module still not know?

5 assumptions you set · 12 authored implications, each citing the records it rests on · 5 invalidators

What it does not model

Every template publishes this list, and it is the reason a Vigil scenario is worth reading. A run carries no probability, no score and no horizon. For this template, in its own words:

The Taiwan Strait cable-disruption scenario template: the assumptions a reader sets on the left, the assumption-to-record chain in the middle, and on the right the conditions that would invalidate the premise and the list of things the template does not model.
And the scenario that cites it. The assumptions are the reader’s; the implications are authored rules citing canonical records; nothing is generated.

9 · And then out

The end of the chain is something somebody else can check.

A subscriber can put this record into a collection, a timeline or a comparison, and assemble a briefing from canonical blocks that carry their own wording, dates, confidence and sources, with their own text labelled as theirs. What is saved is a reference to the record, never a copy of it — so when this reading is next reviewed, the collection, the timeline and the brief move with it instead of quietly going stale.

The briefing on paper: a Vigil Consilium intelligence-brief masthead, the title “Gulf maritime access — September”, the scope line “Iran–Gulf · week to 14 September 2026”, an executive summary marked as the author’s own, and beneath it numbered blocks each carrying its register, its condition date and its confidence.
What the end of a chain looks like: a briefing composed from canonical blocks, each printing its own register, condition date, confidence and sources, with the author's own summary and annotation marked as theirs. This draft is an Iran–Gulf one — it is the Builder's own demonstration document, not the Taiwan Strait chain above.

And because they followed the question, the next material change to it reaches them without being looked for. A review that finds nothing changed sends nothing.

That was one of 445

There are 445 records like this one across 8 modules — Ukraine–Russia, Sahel, Caucasus, Syria, Taiwan Strait, Iran–Gulf, NATO Eastern Flank and Levant — under 83 public Watch questions, with 16 standing scopes and 23 scenario templates over them. Each carries its own test, register, evidence, movement conditions, limits and ledger, exactly as this one does.

Every Professional plan includes this whole toolset. The coverage you choose decides which research modules it works over; coverage and pricing are on the Professional page.

Back to the walkthrough See the whole product Open Professional

Handbook · Professional methodology · Terms · Privacy