War Radar: An Automated Pipeline That Uses AI to Classify Conflict and Evacuation Reports

✍️ OpenClawRadar📅 게시일: October 3, 2026🔗 Source
Ad

War Radar, a new project from the Ukrainian agency SEOPort, publishes a daily world map of armed-conflict risk. The daily estimates are calculated automatically, and AI models are used only for a few narrow classification tasks. It is a practical case study in where models belong in an automated system — and where they do not.

What it shows

  • Countries with available data, updated daily: each country’s current status (from armed violence to major armed conflict), ongoing events such as coups, major disasters, epidemics and internet shutdowns, and a four-level estimate of the risk of a new outbreak of armed violence or a coup within 90 days.
  • Evacuations and warnings on a two-hour cycle: reports of diplomatic staff being withdrawn and new official travel warnings from several governments are checked every two hours.
  • A “Possible sharp escalation in fighting” mark: when reports of fighting in a country suddenly spike, an AI model reads the headlines and judges whether they suggest a sharp escalation. The project publishes its record: in a 2022–2026 check about half of these marks coincided with a sharp rise in deaths, but the mark missed most major escalations, including the 2022 invasion of Ukraine. It does not affect the risk level.
  • Five languages: English, Ukrainian, Polish, German and Spanish, with weekly summaries back to 2018.
Ad

Where AI models fit in

The risk level itself comes from a formula, not a language model: it combines the level and trend of armed violence, recent history, official travel warnings, embassy evacuations, news tone and the situation in neighboring countries, each weighted by how strongly it was linked to crises in the past. Models are used where fixed rules break down — deciding whether a news report really describes an embassy evacuation, or whether the headlines suggest a sharp escalation in fighting.

Under the hood it is a set of scheduled Python jobs that collect and process data, use SQLite, and generate a static site served by nginx. Failures trigger a Telegram alert. Conflict data arrive with a delay of about two months, so recent escalations may not yet be reflected in the risk level — a limitation the project states on the site.

Validation and limitations

The project describes the result as a rough estimate, not a forecast. The formula was fitted on 2015–2022 and tested on 2023–2026, years it had not seen. In that test, weeks rated “Low” were followed by a new crisis about 1 in 110 times, and weeks rated “Very high” about 1 in 4 times — so even at the top level, most weeks pass without a crisis. A public “Checking the estimates” page records every weekly rating from launch and compares it with what happened 90 days later, misses included.

For anyone building automation with AI agents, the design choice is the interesting part: deterministic code does the counting, models handle narrow yes/no classification, and the system publishes observed crisis frequencies for each risk level together with its known limitations.

Ad

👀 See Also

OpenClaw를 사용한 IRS 도박 세금 보고서 자동화
Use Cases

OpenClaw를 사용한 IRS 도박 세금 보고서 자동화

한 개발자가 OpenClaw를 사용하여 DraftKings, FanDuel, BetRivers에서 거래 데이터를 추출하고, 보너스 베팅을 걸러내며, 잔액 연속성을 통해 베팅과 지급금을 연결하고, 단일 세션에서 IRS 제출용 CSV와 PDF 감사 보고서를 생성했습니다.

OpenClawRadar
클로드 코드를 활용한 AI 생성 예술과 비디오로 일본 여행 블로그 만들기
Use Cases

클로드 코드를 활용한 AI 생성 예술과 비디오로 일본 여행 블로그 만들기

한 개발자가 일본에 관한 개인 에세이 웹사이트를 구축하기 위해 Claude Code를 사용하여 창작 파이프라인 전체를 처리한 과정을 기록했습니다. 여기에는 글 다듬기, Nano Banana Pro를 이용한 이미지 변환, Veo 3.1과 3.0-fast를 이용한 비디오 애니메이션, Railway에 배포하기까지 모든 과정이 포함됩니다.

OpenClawRadar
OpenClaw를 사용하여 탱크 전투 봇 만들기: AgenTank.ai 체험하기
Use Cases

OpenClaw를 사용하여 탱크 전투 봇 만들기: AgenTank.ai 체험하기

AgenTank.ai는 무료 브라우저 기반 탱크 배틀 게임으로, OpenClaw 개발자가 실용적이고 재미있는 프로젝트로 실력을 쌓을 수 있습니다. 또 다른 TODO 앱 대신, AI 에이전트(OpenClaw)가 전략을 주도하는 자율 탱크를 만들어 다른 플레이어의 탱크와 싸웁니다.

OpenClawRadar
레딧 사용자가 AI 에이전트 재시작 비용으로 예산의 30%가 낭비된다고 보고, 체크포인팅 해결책 공유
Use Cases

레딧 사용자가 AI 에이전트 재시작 비용으로 예산의 30%가 낭비된다고 보고, 체크포인팅 해결책 공유

r/LocalLLaMA의 한 개발자가 자신의 팀이 작업 중 실패한 워크플로우 재시작에 AI 예산의 30%를 소비하고 있다는 사실을 발견했습니다. 그들은 모든 도구 호출에 대해 체크포인팅을 구현했고, 이로 인해 중복 처리를 제거하여 API 비용이 즉시 감소했습니다.

OpenClawRadar