Take Action

The letter tool should help a reader turn sourced concerns into a message they can inspect before sending. It should keep the output editable, source-aware and moderate in tone, with claims tied to humanitarian need, lawful dispute-settlement routes and nuclear-safety dependencies rather than unsupported casualty totals.

The MVP validates the form locally and does not submit, email or store the generated letter. Users remain responsible for checking the recipient name, factual claims, requested action, personal details and final wording before using the draft outside the site.

Printable leaflets should be treated as versioned public-information material, not as slogans detached from evidence. A leaflet should show the publication or review date, the claims it includes, source boundaries and a correction route for updates after printing.

Because printed material can circulate without the website around it, the file should avoid overclaiming and should direct readers back to source records where possible. It should not include private contact details, unverified testimony or urgent safety instructions unless those have been separately reviewed.

Social-media graphics should preserve the same evidence discipline as articles and downloads. A graphic that carries a number, map, quote or policy claim should include enough context for a viewer to find the source, understand the date and avoid treating a scenario or estimate as verified fact.

Graphics should also be accessible and correction-aware. Text needs readable contrast, images need usable alt text when posted, and any corrected figure should trigger a review of the downloadable graphic so old versions do not keep circulating as current evidence.

Policy briefs should turn evidence into bounded decision questions. A useful brief says which problem it addresses, which source period it uses, what the cited evidence does not prove and what practical options follow from the record.

For this project, policy briefs should keep humanitarian access, civilian protection, reconstruction, peaceful-settlement mechanisms and nuclear-safety preconditions separate enough that one source is not asked to prove the whole case.

Update subscriptions should be narrow, consent-based and easy to understand. A verified-update workflow should tell readers what they will receive, how often, who handles the address, how to unsubscribe and how corrections or source updates are distinguished from general commentary.

The current MVP validates newsletter fields locally but does not connect a mailing-list provider or store submissions. Before subscriptions go live, the site should add retention rules, consent records, unsubscribe handling and a privacy notice that names any provider involved.

Event materials should help facilitators use the project without weakening the evidence boundaries. Slides, handouts and discussion notes should keep source dates, confidence labels, accessibility needs and correction routes visible, especially when material may be reused away from the website.

Event packs should avoid collecting attendee political views, trauma details or sensitive personal stories unless a specific, published and secure workflow exists. The safest default is to provide source-backed prompts, discussion questions and links to current pages rather than private testimony or unsupported claims.