VIGIL CONSILIUM
Context. Not headlines.
Contents

Open Professional
Professional methodology
What Vigil Professional is

Chapter 04

Monitor

Monitor is the editorial cycle made legible: what was reviewed, what moved, and what was checked and found unchanged — over the geography, actors and recorded activity of the module it is scoped to.

The workspace

One toolbar governs everything: what the surface is scoped to, which instruments are on it, and whether the arrangement is kept.

The Monitor toolbar: a workspace selector reading “This cycle”, an “Add instrument” control, and to the right Filter, Compare, Layout and Save view; beneath them a row of instrument chips — what moved, geography, monitored questions, places, modules, cycle chronology, recorded activity, evidence, actors, recent in the corpus and strategic systems.
  1. Workspace — what the surface is scoped to. The whole cycle, one module, or a Standing Watch scope.
  2. Add instrument — put another panel on the workspace.
  3. Filter narrows every instrument at once; Compare takes the current selection into Compare.
  4. Save view keeps the arrangement, the layers and the selection as a row in your Library.
  5. The instruments. A lit one is on the workspace; press one to add or remove it. On a phone they are tabs, one instrument at a time.
Eleven instruments are available; the workspace opens with the ones that suit its scope. Nothing is hidden behind a menu you have to discover.

Scope first. If you know which theatre you care about, pick it in theWorkspace selector at the start of the toolbar — the workspace narrows to that module, or to a Standing Watch scope, and its instruments narrow with it. If you do not, stay on This cycle and read across all 8 modules at once. The rail on the left lists each module's Observable Matrix, Tempo Lab and Timeline — the deeper instruments, not the scope.

The cycle, and what the counts mean

The row of figures at the top of Monitor is the review cycle. Every one of them is a count of reviews, never of events: how many standing questions were looked at, and what the looking found.

The Monitor workspace for the review cycle to 14 October 2026: 79 of 83 questions reviewed, 28 moved, 41 reviewed and held, 10 opened on a baseline, 4 pending; the What moved list leading the page, rows dated 11 and 14 October with their modules, one row — “Are the Gulf’s fixed energy nodes being restored faster than they are re-struck?” — selected; beside it the eight module cards, Levant among them, with what moved and what was reviewed and held in each, and an inspector open on that question showing its latest review, its six observables, its current reading and four actions.
One review cycle across the modules your subscription covers: questions reviewed, moved, checked and found unchanged, and opened on a baseline. Every figure is a count of reviews.

The most important thing on this page“Reviewed and held” is a finding. It means somebody opened the file, checked it against the evidence, and recorded that nothing moved — with a date and a basis. A product that showed only movement would teach you that nothing was looked at. Read the held count as work done, because that is what it is.

The workspace leads with What moved: the questions whose latest review recorded a change, in the corpus's own order. The other half of the cycle is one press away — Monitored questions files every standing question by what its latest review found, and Reviewed and heldopens the quiet ones. Selecting anything opens it in the inspector;Escape or Close puts the inspector away and returns you to the row you pressed, and the selection is in the address, so the browser's Back button brings you to it from any record you open.

Watch questions

A Watch question is a standing question whose answer could materially change an assessment.

There are 83 of them across the 8 modules, and every one is public — you can read any of them today at Watch without an account. What Professional adds beneath them is the observable-level record, which Investigate covers.

One Watch question inside Professional — “Is the Strait of Hormuz commercially usable again?” — with the date its condition is as of, the date it was last reviewed, its review band and its confidence; the actions available on it; and its current reading under “Where the question stands”, marked as an assessment.
  1. Three different dates, never merged: what the condition is as of, when it was last reviewed, and the review band that follows from it.
  2. What you can do with it — follow it, take it into a brief or a collection, put it in the timeline, or open the public dossier.
  3. The register. This reading is Vigil’s assessment rather than a recorded fact, and the mark says so.
  4. “Why it matters” and “Confidence” — the record’s own account of what the reading rests on.
A question is a file with a history, not a status. The ledger is the part that makes the current reading checkable.

The five review outcomes

Every review records exactly one of these, and each means something narrow:

Baseline
The question was opened and its current condition recorded. Nothing has been reviewed against it yet.
No material change
The standing file was checked and nothing moved. A finding, not an absence.
Movement observed
New evidence bears on the question; the assessment holds.
Observable met
One of the named observables occurred. "Met" describes evidence, not success.
Assessment changed
The evidence moved Vigil’s reading. The condition line advanced on this date.

“Met” does not mean “happened, and that settles it”An observable being met describes evidence: the thing Vigil said would bear on the question occurred. It is not a verdict on the question, and it is not success or failure for anybody. The question's own condition line is the only place the answer moves.

A question that has been answered is retired rather than deleted. It keeps its ledger, and where the work continues it names the successor question that took it on.

Geography

The geography instrument: a header reading “Geography · 182 places” with a link to the public map, a layers control and a module filter, a world map with numbered badges where several places overlap and a note in its corner that 106 of 182 carry recorded activity, and beneath it a register across every module, each opening to list its located places.
  1. How many located places are in scope, and a route to the same geography on the public map.
  2. Layers, and the module filter — which record families are drawn, and from where.
  3. A numbered badge is several marks overlapping at this zoom, drawn as one; press it to zoom in and separate them. It is never a count of events.
  4. The register: every place, filed by module. Open a module — or focus the map on it — to list its places, with how many activity records sit at each.
Points only, at the coordinates the records themselves publish. No route, no zone and no line of control is drawn, and no mark is sized by a count.

Standing Watch

A named exposure, held across several questions at once.

A scope groups canonical Watch questions around one defined exposure — a route, a sector, a decision context — and states what it covers, for whom, what it depends on and what it cannot tell you. Everything under it is the public corpus: the same questions, observables, records, sources and review outcomes, produced by the same weekly cycle.

The Gulf Energy & Maritime Risk standing scope inside Monitor: six of six questions reviewed this cycle, and all six moved; the What moved list of those six questions, the cycle chronology, three recorded-activity series, the top of a Gulf map carrying 29 located places, and an inspector waiting for a selection.
A scope opened as a working surface: its own cycle figures, its geography, its recorded activity, and the review entries behind its questions.

What a scope is notIt runs no second research process, holds no records of its own, and produces no risk score — there is no number anywhere on it summarising the exposure. What it adds is the selection, the stated relevance of each question to the exposure, and a review state derived from the questions' own ledgers.

17 scopes are maintained. 2 are public and stay public.

Activity Tempo

Counts of dated, reported occurrences at published markers. Nothing else.

The Iran–Gulf Tempo Lab with three recorded-activity series selected — maritime disruption, attacks on US and partner military positions, and energy infrastructure strikes — each drawn as weekly bins of recorded occurrences between 28 February and 26 September 2026, under the toolbar that chooses the series, the bins and the window, with a legend giving the count bands and a note that a covered bin with no record is drawn empty.
  1. Each series is put on the axis independently. They are never summed and never drawn as one line.
  2. Bin size, and the window — dates or a preset. The window is stated above the strip.
  3. One row per series, on a shared time axis so their timing can be compared.
  4. The legend: five count bands, and “no coverage” drawn differently from a covered bin with no records.
Records are placed in bins by date and counted. No smoothing, no interpolation, no normalisation, and no heatmap anywhere.

What a busier bin meansMore records met that series' stated inclusion rule in that period. It does not mean severity, effect, risk, probability, threat, escalation or operational tempo — and a quieter bin may mean that reporting thinned rather than that activity did. Two series are not commensurable with each other, and none of them is commensurable with a figure published by anyone else.

Which modules have Tempo

Not all of them, and that is a decision. A series exists only where Vigil has a defensible, repeatable inclusion rule — a population it can define, published markers to count at, and reporting it can apply the rule to consistently.

Current coverage is Ukraine–Russia, Sahel, Caucasus, Syria, Taiwan Strait, Iran–Gulf and NATO Eastern Flank, with 14 series in total. Levant maintain none, and their Tempo rail is absent rather than empty.

An absent series is not a quiet theatreA module without Tempo is not a less important module and is not one where less is happening. It is a module for which Vigil has not established a counting rule it would be prepared to defend. Counts it could not defend would be worse than none. The same rule is stated in the public methodology.

Keeping a workspace

  1. Scope it

    Pick the module or the standing scope you work on.

  2. Arrange it

    Add or remove instruments, set the layers, filter to the outcomes you care about.

  3. Select

    Leave the object you were looking at selected — the view remembers it.

  4. Save view

    It appears in your Library and reopens exactly as it was, against today’s corpus.

A saved Monitor view stores the arrangement and nothing else. It caches no reading, which is why it cannot show you a stale one.

Next: Investigate — what the readings on this surface rest on.