A maintained set of questions organised around a defined exposure.
Vigil’s Watch questions, selected and maintained around one professional or operational exposure — reviewed on the weekly cycle, with the material changes separated from the reviews that found nothing moved. The method is Watch’s, unchanged; what a scope adds is the selection, the relevance to that exposure, and the state of the set as a whole.
- Public questions
- 42
- Conflicts
- 6
- Cadence
- Weekly
- Demonstration scope
- 1
- Latest public review
Two uses of one method The questions, the observables, the review outcomes and the ledgers are the same objects. What differs is who defines the set.
Public Watch
Questions Vigil maintains because they matter to understanding the system.
42 active questions across 6 conflicts, each with its current assessment, its named observables, what would change the assessment, its confidence and basis, a dated review ledger and its connected records. Each question is reviewed on the Weekly Brief cycle and can be updated between briefs when material evidence appears.
Standing Watch
A selected set of those questions maintained around a defined professional or operational exposure.
The scope names which questions an organisation has to keep checking and why each matters to that exposure. Its review state — what moved, what did not, which question is still pending, through which cycle the whole set was reviewed — is derived from the questions’ own ledgers. The research is never duplicated.
The question a scope answers: what are the questions this organisation would have to keep checking — and did any of the answers materially move?
How a scope works Six steps, five of which already exist for every public question. The scope adds the first.Watch methodology
- ScopeOne exposure, responsibility or decision context, stated in a line. Never a named client on the public record.
- QuestionsA selected set of canonical Watch questions, each with one authored note on why it matters to the scope.
- ObservablesThe questions’ own named evidence — what a review checks against, written so a reader can check it too.
- Weekly reviewThe existing Sunday cycle reviews every question and writes its ledger. The scope consumes that work; it adds none.
- Material changeMovement observed, an observable met or an assessment changed — separated from the reviews that found nothing moved.
- Evidence · Map · Tempo · SystemEvery finding opens the record it rests on, the activity beside it and the system it runs through.
Live demonstration A public scope over public questions, behaving exactly as the real system does — including in the weeks when nothing moves. No organisation is represented.
Demonstration scopeIran–Gulf
Gulf Energy & Maritime Risk
Commercial access, energy infrastructure and regional security conditions affecting Gulf maritime and energy exposure.
- Questions
- 5
- Reviewed this cycle
- 5 of 5
- Movement
- 2
- Unchanged
- 2
- Baseline
- 1
- Scope reviewed through
01 Is the Strait of Hormuz commercially usable again?02 Is Bab el-Mandeb still usable, and for whom?03 Are the Gulf's fixed energy nodes being restored faster than they are re-struck?04 Does Gulf air and missile defence become institutionally integrated?05 Does the Makkah Agreement become an operational defence mechanism?
How it is kept current A scope is not a second editorial workflow.Editorial process
Derived every cycle, from the questions
The current assessment and its date · the latest review outcome · the review ledger · confidence and basis · the outcome counts across the set · the material-change list · which question is pending · the activity series beside each question · the records the questions share.
Authored once, on the scope
The exposure it is organised around · which questions belong · why each matters to that exposure · which recorded series give it context. Membership changes are editorial decisions, not weekly work.
What this demonstrates How a defined set of standing questions is maintained around one exposure, on the public corpus, through the existing weekly review.
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.
- Under validation
- Organisation-specific scopes and their delivery, cadence beyond weekly, pricing, and questions that are not public. None is built, priced or sold.
- Not built
- Accounts, billing, automated notices, private workspaces, an API. Each waits for actual demand, not for a roadmap.
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.