Daily Intelligence Report
At a glance
Counts of the stored claim records and follow-up, not a summary of the narrative. How to read these labels
- Coverage window
- Not stored for this report.
- Follow-up investigation
- None stored for this report.
- Claim records by status
- This report has no claim records.
- Claim records by confidence
- This report has no claim records.
- SAR measurements
- None supplied to this report. No SAR measurements for this period does not mean that monitored sites were unchanged.
- Frontline map data
- Age of the map data is not available.
Read with these limits in mind
- This report is machine-generated from open sources and may contain errors.
- A source’s publication time is not the time of the event it describes.
- Frontline map data can lag the reporting period; map dates do not establish when territory changed.
- No SAR measurements for this period does not mean that monitored sites were unchanged.
Intelligence Summary
Analyst briefMachine-generated narrative. Labels inside it are written by the model. How to read these labels
SUBJECT: DAILY INTELLIGENCE SUMMARY – 2025-12-31 DTG: 2025-12-31T15:00Z AOR: Eastern Europe / Ukraine / Russian Federation Rear
1. EXECUTIVE SUMMARY
(CRITICAL ALERT) IMMINENT SATURATION STRIKE & EASTERN BREACH: The operational tempo has reached a critical crescendo approaching the New Year transition. The most significant new development is the reported deterioration of the Pokrovsk-Myrnohrad defense line, with unconfirmed Russian Federation (RF) claims of Myrnohrad’s seizure and combat activity spilling toward the Dnipropetrovsk administrative border. Simultaneously, Synthetic Aperture Radar (SAR) indicators at RF ammunition depots (Score 27.24 - CRITICAL) combined with multi-vector UAV ingress confirm preparations for a massive saturation strike against Ukrainian energy and decision-making centers expected between 1800Z and 0200Z.
2. CHANGES FROM PREVIOUS REPORT
- Pokrovsk Axis: NEGATIVE SHIFT. Yesterday's report noted "pressure"; current intelligence (1309Z) describes the situation as "grim," with RF forces claiming the capture of Myrnohrad (Dimitrov) and DeepState confirming critical deterioration.
- Strategic Logistics: ALARMING SURGE. SAR analysis of the 260th GRAU Arsenal shows a score jump to 27.24 (up from ~16). This indicates a massive logistical push for heavy munitions, significantly exceeding routine supply rates reported yesterday.
- Hybrid Warfare: NEW THEATER. A subsea cable damage incident in the Gulf of Finland (reported 1324Z) indicates an expansion of RF hybrid operations against NATO/EU infrastructure, likely to deter support ahead of the Jan 3 summit.
- Naval Technology: TACTICAL ADAPTATION. Ukrainian Naval Forces (VMS ZSU) report RF is now actively copying Ukrainian maritime drone (USV) designs, shifting from passive harbor defense to potential offensive maritime capability.
3. THREAT ASSESSMENT
(SAR Score Legend: 0-5 Low/Routine | 5-15 Moderate/Monitor | 15+ High/Critical)
- Strategic Aerial Strike (THREAT LEVEL: CRITICAL)
- Indicator: 260th GRAU Arsenal surged to Score 27.24 (CRITICAL); active multi-vector Shahed ingress (Odesa, Sumy, Chernihiv, Kryvyi Rih); removal of "Bankova" AD restrictions.
- Assessment: (HIGH CONFIDENCE) The surge in logistics activity confirms the loading of heavy munitions. Combined with the "retaliation" narrative for the Valdai incident, a mixed missile/UAV strike targeting the energy grid and Kyiv is imminent (NLT 2026-01-01T0200Z).
- Eastern Front Collapse (THREAT LEVEL: HIGH)
- Indicator: RF MoD claims of "liberation" of Myrnohrad; reports of "Otvažnyje" (Group O) operating near Dnipropetrovsk border.
- Assessment: (MEDIUM CONFIDENCE) While full capture is unconfirmed, the defense in this sector is likely porous. A breach here opens the flank to Dnipropetrovsk, validating the mass evacuations noted in the previous report.
- Northern Escalation (THREAT LEVEL: RISING)
- Indicator: Chief of General Staff Gerasimov inspected "Group North" (Sumy/Kharkiv border) on Dec 31.
- Assessment: (MEDIUM CONFIDENCE) High-level inspections typically precede offensive operations or major force rotations. This may signal the activation of the "infrastructure protection" reservists for a distraction offensive in Sumy.
4. OPERATIONAL DEVELOPMENTS
- Eastern Axis (Donbas):
- Pokrovsk/Myrnohrad: DeepState reports "grim" tactical conditions. RF sources claim the capture of Myrnohrad; if true, this unhinges the northern flank of the Pokrovsk logistical hub.
- Dnipropetrovsk Border: Unconfirmed reports of RF "Group O" elements engaging near the administrative border, attempting to exploit the chaotic evacuation environment.
- Southern Axis (Zaporizhzhia/Odesa):
- Zaporizhzhia: 38th Guards Motor Rifle Brigade (GMRB) and 35th Army elements are conducting "year-end" spoiling attacks despite adverse weather.
- Maritime: UAF VMS ZSU is pivoting to counter-USV operations as RF deploys copycat drone tech.
- Deep Strike Operations:
- UAF Success: Confirmed strikes on the "Temp" plant (Yaroslavl, ~700km range) and Tuapse oil depot (Krasnodar Krai).
- RF Impact: Moscow region experienced a 600k resident blackout; internal RF reports show flight delays and airport chaos.
- Information/Political:
- Chechnya: Conflicting reports regarding Ramzan Kadyrov—rumors of hospitalization vs. automated Telegram activity. Potential instability in Chechen Rosgvardia units.
- Hybrid IO: "Swan Lake" broadcast and fake "US aid block" narratives circulating to demoralize UAF defenders.
5. INTELLIGENCE GAPS
- P1 (Ground Truth): Status of Myrnohrad. Has the city center physically fallen to RF forces, or are fighting positions still held? Immediate confirmation required.
- P2 (Strategic Intent): Gerasimov's Location. Precise geolocation of Gerasimov's "Group North" inspection is needed to predict the vector of the next Northern push.
- P3 (Tech Capability): RF USV Specs. Are the new Russian maritime drones engaging via satellite (Starlink/Tillandsia) or Line-of-Sight? This dictates jamming requirements.
- P4 (Leadership): Kadyrov's Health. Definitive proof of life for Kadyrov is needed; his incapacitation could lead to the withdrawal of "Akhmat" units from the line.
6. PREDICTIVE ANALYSIS (NEXT 24-48 HOURS)
- MLCOA (New Year's Blitz): (HIGH CONFIDENCE) Between 1800Z and 0200Z, RF will launch a maximum-effort strike using Shaheds to strip AD ammunition, followed by Kalibr/Iskander volleys targeting energy infrastructure in Kyiv, Lviv, and Odesa. Ground forces in Pokrovsk will utilize the noise cover to consolidate gains in Myrnohrad.
- MDCOA (Operational Breakthrough): (MEDIUM CONFIDENCE) Capitalizing on the "grim" situation in Myrnohrad, the 33rd GMRR (Dobropilsky salient) and Group O launch a synchronized push across the Dnipropetrovsk border tonight, aiming to create a fait accompli territorial gain before the Jan 3 summit.
- Wildcard: The Gulf of Finland cable damage may be a precursor to a broader maritime sabotage campaign; expect potential disruptions to Norway-Poland gas pipelines.
7. RECOMMENDATIONS
- Immediate ISR Re-Tasking: MYRNOHRAD SECTOR. Shift high-resolution SAR and thermal drone assets to verify the Line of Contact (LOC) in Myrnohrad. If the city is lost, authorize mining of the M-04 highway approaches to Dnipro immediately.
- Air Defense Alert: STATEWIDE RED. All AD units must conserve interceptors for cruise/ballistic threats expected post-1800Z. Mobile Fire Groups (MFGs) should handle Shaheds to preserve Patriot/SAMP-T missiles for high-value targets.
- Counter-Hybrid Measures: BALTIC LIAISON. Alert naval allies in the Baltic Sea regarding the RF USV development and cable cutting; request increased ASW/Surface monitoring.
- Information Operation: KADYROV UNCERTAINTY. Amplify reports of Kadyrov’s health crisis via PsyOps channels targeting Chechen "Akhmat" units on the frontline to induce command paralysis or withdrawal.
//END OF REPORT//
Legacy provenance
This archived report predates claim-level evidence records. Treat its confidence labels as editorial assessments rather than independently verifiable citations.
Frontline context
Territorial control and recent changes shown by DeepState.
Against the previous report from 30 Dec 2025, 15:01 UTC, bright red is newly marked Russian-occupied and green is no longer marked occupied. For the infiltration area, yellow is this report and cyan is the previous report.
Report Visuals
5 visualsGeospatial Analysis
14 locations identified
Historical reconstruction from source editions available by report time.
Places and data export
Coordinates come from geocoding place names found in the report. They locate the named place, not the event described there. Latitude and longitude are WGS 84 decimal degrees.
Show 14 places with coordinates
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Myrnohrad | UA | 48.2962118, 37.2700035 | |
| Pokrovsk Logistical Hub Area | UA | 48.282193, 37.1847804 | |
| Kyiv | UA | 50.4503596, 30.5245025 | |
| Odesa, Sumy, Chernihiv, Kryvyi Rih Energy Infrastructure | UA | 46.4845702, 30.7326047 | |
| Lviv | UA | 49.839683, 24.029717 | |
| 260th GRAU Arsenal | RU | 0, 0 | |
| Dnipropetrovsk Administrative Border Exploitation Zone | UA | 48.464717, 35.046183 | |
| Sumy/Kharkiv Border Sector | UA | 50.00201269999999, 36.3073994 | |
| Zaporizhzhia Front Sector (38th GMRB/35th Army) | UA | 47.83928419999999, 35.13870970000001 | |
| Gulf of Finland Subsea Cable | FI | 59.9124514, 26.2623373 | |
| Temp Plant | RU | 57.8991523, 38.8388633 | |
| Tuapse Oil Depot | RU | 44.0961624, 39.0745411 | |
| Moscow Region Power Grid | RU | 55.340396, 38.2917651 | |
| Dobropilsky Salient (33rd GMRR Position) | UA | 48.015883, 37.80285 |
How to read the labels
Labels on this page come from three separate mechanisms. A label from one does not mean the same as a similar word from another.
1. In the narrative
Machine-generated narrative. Labels inside it are written by the model.
- Unconfirmed:
- Written by the model. Its instruction is to mark claims that rest on a single source.
- Confidence: HIGH / MEDIUM / LOW
- Written by the model. The report stores no definition of these levels, and they are not computed from the claim records. Do not read them as the record confidence above.
2. On claim records: confidence
Record confidence is a threshold on a number stored with the source observation. It is not a probability that the event happened. The follow-up investigation may lower it and never raises it.
- HIGH confidence
- The status is Independently corroborated, Geolocated or Imagery corroborated, and the stored confidence of the supporting observation is at least 0.75.
- MEDIUM confidence
- The stored confidence of the supporting observation is at least 0.5 and the rule for HIGH is not met.
- LOW confidence
- The stored confidence of the supporting observation is below 0.5.
2. On claim records: status
Machine-selected records from the source ledger, labelled by fixed rules. They are a separate selection and are not a list of the sources behind the narrative above.
- Single-source claim
- One retained source observation supports the record, from a sender that is not on the list of official bodies.
- Official claim
- One retained source observation, from a sender whose name matches a keyword list of official bodies. It says who made the claim, not that the claim is verified.
- Multiple reports, same origin
- Several retained observations that do not meet the rule for independent corroboration. They are treated as one origin.
- Independently corroborated
- At least two distinct source documents from at least two differently named senders. The rule compares sender names and document fingerprints. It does not establish that the senders had separate access to the event, and a repost under another name can satisfy it.
- Geolocated
- One retained observation carrying coordinates with a geolocation confidence of at least 0.5. It concerns the location only, not the cause or the outcome.
- Imagery corroborated
- Imagery supports the observation. It does not by itself establish cause or intent.
- Analyst assessment
- A Nightwatch assessment rather than a directly observed fact.
- Contested
- Set by the follow-up investigation: material source accounts remain in conflict.
- Corrected
- Set by the follow-up investigation: the record was changed after the investigation reached a definitive answer.
- Insufficient evidence
- Set by the follow-up investigation: the available evidence does not support the record as first labelled.
3. In the follow-up investigation
Machine-run follow-up on one selected claim record. Sources listed include material that was retrieved and not used.
- Confirmed
- The investigation reached a definitive answer supporting the selected claim. The report was rewritten after it.
- Refuted
- The investigation reached a definitive answer against the selected claim. The report was rewritten after it.
- Materially refined
- The investigation reached a definitive answer that changes the selected claim in a material way. The report was rewritten after it.
- Inconclusive
- The investigation did not reach a definitive answer. The report text was kept; the investigation could only attribute, hedge or lower confidence. Individual findings inside it can still carry their own outcome.
Each finding has its own outcome and a confidence written by the model. That confidence is in the finding as worded, which may itself be a statement that something is unknown.
Kinds of investigation source
- External web page
- A web page retrieved during the follow-up investigation. Its address is stored and linked.
- Source observation behind a claim record
- A source observation the claim records were built from. No address is stored for it.
- Nightwatch archive item
- An item found by searching the Nightwatch archive during the investigation. It may be unrelated to the question. No address is stored for it.
