About the Project

The project exists to document the costs of war in language that is humane, source-aware and useful for public judgment. It brings together civilian harm, economic pressure, nuclear risk, displacement, testimony and peace options without asking readers to treat one cost as the only cost.

The mission is not neutrality between harm and the people harmed. It is discipline: separate evidence from interpretation, show uncertainty where it exists, avoid theatrical certainty and make practical routes toward peace visible beside the damage.

This section should state how the project is funded, who controls editorial decisions and whether any partner, donor or sponsor has a material interest in the content. If there is no external funding, that should be said directly rather than left implied.

Funding disclosure is especially important on a war-information site because money can shape emphasis, topic choice and public trust even when it does not change a single sentence. Readers should be able to see the relationship between support, independence and accountability.

The editorial team section should identify who is responsible for commissioning, writing, editing, source review, translation and publication decisions. A public role can be named as a person, an organisation or a clearly described editorial function when safety requires caution.

The page should also explain how disagreements are handled. On topics such as civilian casualties, sanctions, nuclear safety and negotiations, good editorial work depends on checking claims before they become slogans and correcting language when evidence changes.

Reviewer roles should explain what kind of scrutiny a page receives before publication. A reviewer may check sources, data handling, legal risk, conflict sensitivity, accessibility, translation quality or whether a scenario is clearly distinguished from a forecast.

The site should not use review language as decoration. If review is limited, pending or absent, that status should be visible. If a page makes high-stakes claims, the review record should be stronger than for a simple navigation or contact page.

Every substantial page should make editorial responsibility visible. Author metadata explains who prepared the text, what role they had, when the page was last updated and whether the item is reporting, analysis, scenario work, opinion or another labelled format.

This does not turn a page into a personal brand. It gives readers a route for judging expertise, conflicts of interest and accountability before they rely on material about civilian harm, budgets, nuclear risk or peace proposals.

Reviewer metadata should explain who checked the work and what kind of review happened. A source review is different from a legal review, a sensitivity review, a data review or a translation review, and readers should not have to guess which one took place.

When a page has not yet been reviewed, the site should say so plainly. A missing review is not automatically a false claim, but it is a limit on how much confidence the page asks from the reader.

Funding disclosure should state who pays for the project, whether funders can influence editorial choices and whether any article, tool or campaign page is sponsored. The answer may be simple, but it needs to be visible before trust is requested.

War-related public information can be used for advocacy, fundraising or policy pressure. Clear funding language helps readers separate evidence, interpretation and institutional interest.

Contact details should give readers a practical way to report errors, ask for corrections, raise safety concerns, request data removal or contact the editorial team. A contact route is part of accountability, not a decorative footer item.

Because the site deals with war, testimony and vulnerable groups, the contact process should also make limits clear: what can be changed, what cannot be promised, and how urgent safety concerns are handled.