casualty-correction-maritime-strike

Multiple authoritative and independent origins support the vessel, rescue outcome and most of the victim breakdown. Because the complete toll still originates with one involved-state authority, the correction remains LIKELY rather than CONFIRMED.

Confidence: 4.4/5 · 5 origin families · 3 open items.

• Full public victim list
• Ship manager's detailed statement
• Any Russian public response

The correction is narrow, internally coherent and supported by multiple local desks. The exact injury total remains regional-authority data, so LIKELY is retained.

Confidence: 4.2/5 · 2 origin families · 2 open items.

• Final medical outcome for the injured
• Final structural assessment

The narrow casualty outcome is consistent across an authoritative evolving chain. Independent outlets support occurrence and context, while the final number remains locally sourced.

Confidence: 4.1/5 · 4 origin families · 3 open items.

• Final injury outcomes
• Full damage assessment
• Weapon attribution beyond Ukrainian authorities

Occurrence and deaths have editorial corroboration, while the final regional total is an authoritative but single-origin update. LIKELY is appropriate.

Confidence: 3.9/5 · 3 origin families · 3 open items.

• Final medical outcomes
• Exact weapon assessment
• Whether later regional updates add casualties

A detailed regional summary makes the narrow aggregate likely, but the single origin and window overlap prevent stronger status.

Confidence: 3.6/5 · 1 origin families · 3 open items.

• Final injury severity
• Exact dashboard-window overlap
• Independent confirmation of each listed incident

The detailed regional account is credible and current, but limited source independence keeps it at LIKELY with moderate confidence.

Confidence: 3.5/5 · 1 origin families · 3 open items.

• Hospitalized child's condition
• Independent weapon identification
• Final building damage

Cross-belligerent acknowledgement plus auditable imagery and heat data makes the broad strike-and-fire claim LIKELY. The wording avoids accepting launch counts or all target functions as fact.

Confidence: 4.2/5 · 6 origin families · 4 open items.

• Exact oil-depot damage
• Final casualty count
• How many drones reached targets
• Military function of every affected warehouse

The occurrence of maritime strikes is credible, but the material disagreement over vessel count and type requires CONFLICTED status.

Confidence: 3.1/5 · 4 origin families · 3 open items.

• Whether the six- and seven-vessel lists describe the same operation
• Identity and status of each vessel
• Independent imagery, operator or port confirmation

The claim is deliberately limited to public statements, protests and absence of a decree. Those facts are directly auditable and therefore CONFIRMED; the future leadership outcome remains unknown.

Confidence: 4.4/5 · 4 origin families · 3 open items.

• Whether Syrskyi will later be dismissed
• Whether Fedorov will return
• Content of private consultations

The detailed official claim and multiple attributed reports make the event plausible, but lack of independent evidence prevents LIKELY status.

Confidence: 3.0/5 · 3 origin families · 3 open items.

• Independent imagery or medical confirmation
• Weapon provenance
• Final casualty count

Credible belligerent sources materially disagree about control, and independent map access was incomplete. CONFLICTED is mandatory.

Confidence: 2.9/5 · 2 origin families · 3 open items.

• Actual force presence
• Control of neighborhoods
• Whether either side made a durable change after cutoff

The high tempo is an attributed official count and the lack of confirmed movement is a cautious independent assessment. The combined narrow statement is LIKELY, not definitive.

Confidence: 3.7/5 · 1 origin families · 3 open items.

• Small changes not yet geolocated
• DeepState's 24-hour assessment
• Final revised engagement count