political-military-leadership
Daily situation picture
Would you like one calm daily brief?
Only anonymous interest is measured. No email address is collected.
Evidence and open questionsHow we verify 13 claim clusters
Confidence describes evidence quality, not certainty. Reposts are not counted as independent confirmation.
political-military-leadershipUkraine CONFIRMED
President Volodymyr Zelenskyy publicly announced Mykhailo Drapatyi as the new Commander-in-Chief in place of Oleksandr Syrskyi and separately said he offered Mykhailo Fedorov an unspecified leadership role.
Why this matters
A direct authoritative announcement plus multiple independent editorial confirmations supports CONFIRMED status. Wording is limited to the public announcement and preserves the offer-versus-appointment distinction.
Why evidence is limited
Confidence: 4.6/5 · 5 origin families · 3 open items.
- Formal decree text and effective transition timing
- Fedorov role, acceptance and legal status
- Syrskyi's next assignment
Sources
- Ukrinform — Drapatyi named new Commander-in-Chief ↗
- Ukrinform — Fedorov offered leadership position ↗
- Guardian — Zelenskyy replaces military leader ↗
- Reuters — Ukraine gets new top commander ↗
- ISW — Russian Offensive Campaign Assessment, July 21 ↗
- Guardian — Ukraine war briefing, July 22 ↗
- Liveuamap — July 21 Ukraine event stream ↗
maritime-securityBlack Sea · off Romania LIKELY
The Liberian-flagged LPG tanker Gas Lisbon was struck outside Romanian territorial waters while heading to Ukraine; Romanian rescuers evacuated the full crew and three were injured, while attribution remained under investigation.
Why this matters
Official rescue action, crew evacuation and independent editorial reporting strongly support the bounded event. Attribution is explicitly held below final confirmation, so LIKELY is appropriate.
Why evidence is limited
Confidence: 4.3/5 · 3 origin families · 3 open items.
- Final forensic attribution
- Weapon type and launch origin
- Final vessel damage and cargo condition
civilian-casualtiesZaporizhzhia Oblast · Zaporizhzhia LIKELY
Zaporizhzhia Oblast authorities reported three civilians killed and 24 injured during the July 21-22 reporting day; the city strike accounted for all three deaths and 13 injuries.
Why this matters
A timely authoritative aftermath source and independent event confirmation support LIKELY, while limited numerical independence prevents CONFIRMED.
Why evidence is limited
Confidence: 3.6/5 · 3 origin families · 2 open items.
- Late hospital revisions
- Final separation of city and other regional incidents
civilian-casualty-correctionOdesa LIKELY
Odesa regional authorities raised the injury count from the July 21 daytime strike to four.
Why this matters
The regional authority is authoritative for immediate medical reporting and the correction is internally traceable; single-origin dependence keeps it LIKELY.
Why evidence is limited
Confidence: 3.6/5 · 2 origin families · 2 open items.
- Later medical revisions
- Full damage assessment
civilian-casualtiesKharkiv Oblast LIKELY
Kharkiv Oblast authorities reported that a drone struck a moving civilian car on July 21, killing two passengers and injuring the driver.
Why this matters
A strong, specific local aftermath source supports LIKELY for the narrow casualties, but limited independence prevents CONFIRMED.
Why evidence is limited
Confidence: 3.5/5 · 1 origin families · 3 open items.
- Independent visual verification
- Final condition of the driver
- Weapon provenance beyond the preliminary local assessment
regional-civilian-impactDnipropetrovsk Oblast LIKELY
Dnipropetrovsk Oblast authorities reported five civilians injured in July 21 daytime attacks in the Nikopol and Synelnykove districts.
Why this matters
A credible regional aftermath source supports the bounded minimum, with conservative separation of cutoffs. Limited independence keeps it LIKELY.
Why evidence is limited
Confidence: 3.4/5 · 2 origin families · 2 open items.
- Late hospital revisions
- Complete period alignment across district updates
regional-civilian-impactDonetsk Oblast LIKELY
Donetsk Oblast authorities reported at least two civilians killed and seven injured in July 21 attacks, including a strike on a civilian vehicle.
Why this matters
Traceable local updates and specific aftermath reporting support LIKELY; the exact roll-up remains one official family.
Why evidence is limited
Confidence: 3.5/5 · 2 origin families · 2 open items.
- Late casualty revisions
- Full event list behind the regional minimum
casualty-accounting-clarificationSumy Oblast LIKELY
Sumy Oblast's July 22 morning roll-up recorded seven people injured or seeking medical care, but several had been injured in attacks on July 15, 19 or 20 rather than during the latest reporting day.
Why this matters
The source's explicit date breakdown directly supports the clarification. LIKELY reflects reliance on one reporting chain while preventing a misleading daily sum.
Why evidence is limited
Confidence: 3.5/5 · 1 origin families · 2 open items.
- Whether all seven had previously been counted
- Final medical classifications
civilian-casualtiesKyiv Oblast LIKELY
Kyiv Oblast authorities reported five people, including three children, injured when a residential building was struck on the morning of July 22.
Why this matters
Direct emergency response and a specific official casualty count support LIKELY, with moving-toll risk and limited independence clearly retained.
Why evidence is limited
Confidence: 3.6/5 · 1 origin families · 2 open items.
- Later medical revisions
- Final damage and munition assessment
strike-verificationKursk Oblast LIKELY
Geolocated footage supports that Ukrainian strikes hit a Russian fighter aircraft and an air-defense system at an airfield in Kursk Oblast; complete destruction was not independently established.
Why this matters
Auditable geolocated visual evidence supports the bounded hit claim at LIKELY. The stronger destruction wording is withheld.
Why evidence is limited
Confidence: 4.1/5 · 2 origin families · 3 open items.
- Repairability and final damage
- Whether both systems were operational
- Independent post-strike imagery
long-range-strike-aftermathLipetsk LIKELY
A large industrial fire occurred in Lipetsk after a reported Ukrainian strike; Russian local acknowledgement, geolocated imagery and Astra reporting support the fire, while exact site function and damage remain incomplete.
Why this matters
Cross-environment acknowledgement and geospatial evidence make the fire and likely strike link LIKELY. The report withholds unsupported target and damage claims.
Why evidence is limited
Confidence: 4.1/5 · 2 origin families · 3 open items.
- Exact facility hit
- Degree of operational disruption
- Final attribution and damage assessment
campaign-level-frontline-summaryUkraine frontline PLAUSIBLE
ISW assessed localized Ukrainian gains in two broad directions and no confirmed Russian advances across several major sectors on July 21; no broad breakthrough was independently established.
Why this matters
The bounded no-broad-breakthrough conclusion is credible and evidence-backed, but incomplete map-family independence keeps it PLAUSIBLE.
Why evidence is limited
Confidence: 3.5/5 · 1 origin families · 3 open items.
- Small changes not yet processed
- DeepState's independent 24-hour assessment
- Durability of localized gains
contested-controlKostiantynivka · Donetsk Oblast CONFLICTED
Control of Kostiantynivka remained contested: Russian sources claimed positions and advances, while recently processed footage showed Ukrainian positions in areas where Russian presence had been claimed.
Why this matters
Credible sources materially disagree and the independent reviewer explicitly says control remains contested, so CONFLICTED overrides the numerical score.
Why evidence is limited
Confidence: 3.1/5 · 1 origin families · 3 open items.
- Citywide control
- Age and completeness of available footage
- Map revisions expected after cutoff
Actor ledger
Responsible-side claims in this memo
Restrained actor labels keep attribution visible without turning the report into a scoreboard.
Ukraine
0No verified selected event in this edition.
Russia
0No verified selected event in this edition.
Afternoon update
Since this morning
No separate material delta has been published after the morning report. The next checks keep the map and continuity ledger in the same order.
Method and coverage
How this report was checked
- Claim clusters
- 13
- Source families
- 14
- Confirmed / likely
- 11
18 republication chains were detected and grouped.