About Vigil Consilium
What Vigil is, how content gets sourced, reviewed and published, what role AI plays, and how to hold the project to account. If themethodology is the rulebook, this page is the disclosure statement.
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.
Status: public alpha
Vigil is in public alpha. The structure and credibility machinery are real and enforced, and the developments briefs are verified reporting. Each conflict module is updated on its stated cadence: Ukraine–Russia is reviewed weekly, while Mali, the Caucasus and Syria are reviewed monthly and updated when major developments are verified. 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 thedemo 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.
Review workflow
Nothing publishes automatically. Every change follows the same path:
- 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.
- Review — the full change set is read, line by line, against public evidence before anything is committed. Corrections happen here.
- 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.
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.