About Vigil Consilium

Purpose

Vigil Consilium is an independently maintained conflict-context project. It exists to connect what happened — the developments a news feed reports — to the map, the actors, the forces, the history and the economic consequences that explain why it matters and what to watch next. It is a context layer, not a news service: deliberately slower than the news, and built to be more durable than it.

Two ways to work

Vigil is published in two matched layers. Read is the written analysis — modules, Weekly Briefs, Analytical Notes and the canonical records behind them. Explore is the same corpus made interactive: the actors in a system, the relationships between them, how their forces are organised, what their logistics depend on, what happened and when, what Vigil is watching, and how well each record is established. Neither is a summary of the other, and every panel in Explore links back to the record it came from.

Explore is not a tactical tracker, a prediction engine or a scoring system. It publishes no unit positions, strengths or movements, no route between logistics nodes, no probabilities and no ratings — because Vigil does not hold that information and will not infer it.

This is Vigil Consilium V2.0. Coverage and depth per module are described below and stated on each module page.

Coverage and completeness

Vigil Consilium is independently developed and actively expanding. The structure and credibility machinery are real and enforced, and the developments briefs are verified reporting. Each conflict is reviewed on its stated cadence. All five published modules are reviewed every week. Each receives a dated weekly brief; quiet weeks explicitly record when no material change was identified. Parts of the baseline reference content are still working through a progressive source-review pass. Every page states its own dates, confidence and profile completeness, and any record that is an illustrative sample is labelled as such (see the demo archive). The project would rather show the seams than pretend there are none.

Ownership and independence

Vigil is an independently maintained project. It is not affiliated with any government, political party, military organisation, financial institution, media company, or advocacy group.

The project is currently self-directed and has no sponsored editorial relationships. Any future funding, partnerships, sponsorships, or material conflicts of interest will be disclosed publicly on this page before they take effect. Vigil carries no advertising, affiliate links or paid placements: nobody pays for coverage.

Vigil accepts voluntary reader support towards its research, infrastructure and continued development. It is voluntary, it is not a subscription to anything, and it buys no access, preference or influence over what Vigil publishes or how it is assessed.

Review workflow

Nothing publishes automatically. Every change follows the same path:

1. Drafting — content is drafted against the site's schemas, which mechanically require sources, confidence grades and as-of dates on every claim. A draft that lacks them cannot build, let alone publish.
2. Review — the full change set is read, line by line, against public evidence before anything is committed. Corrections happen here.
3. Publication — deployment is a deliberate, manual act. There is no scheduled or automated publishing.

Editorial process and AI assistance

AI tools may assist with coding, data formatting, drafting, and consistency checks. AI output is not treated as a source. Material claims require review against public evidence before publication, and editorial responsibility remains with the project. The schema machinery — confidence grades, source requirements, sensitivity rules, link validation — applies to AI-assisted drafts exactly as it would to any other, and is enforced at build time.

Corrections

Material errors are corrected in place and logged publicly on thecorrections page — what changed, when, and on which page. The log is never purged and records are not silently rewritten.

Spotted an error? Write to[email protected]with the page URL and, if you have it, a source. Every substantiated correction is credited in the log unless you ask otherwise.

Follow Vigil on X, LinkedIn and YouTube for analysis, Shorts and project updates.

What we deliberately exclude

The project's safety rules are structural, not aspirational: no current unit positions, strengths, movements or readiness; military and nuclear sites are shown at area level only; economics is exposure and context, never investment advice. The full rules are in the methodology.