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-29 DTG: 2025-12-29T15:00Z
1. EXECUTIVE SUMMARY
(STRATEGIC DIVERGENCE) DIPLOMATIC SOLIDIFICATION VS. TACTICAL ACCELERATION: Following the Zelenskyy-Trump summit, a 15-year US-Ukraine security framework and $100bn reparation plan has been confirmed. In response, the Russian Federation (RF) has accelerated operational tempos to shape the battlefield prior to any implementation. Key developments include the confirmed loss of Dibrova (Lyman Sector) and a concerted Kremlin narrative—supported by localized advances—claiming RF forces are within 15km of Zaporizhzhia City. SAR analysis indicates a drastic shift in RF Air Defense posture, suggesting anticipation of UAF deep strikes or protection for a renewed offensive surge.
2. CHANGES FROM PREVIOUS REPORT
- Lyman Sector Degradation: CONFIRMED LOSS. Unlike the previous report describing forestry combat, the RF Ministry of Defense (MoD) has officially confirmed the capture of Dibrova (1002Z), and UAF lines in the Serebryanske Forest are at risk of envelopment.
- Zaporizhzhia Threat Level: ESCALATION. Previous reporting noted a "widening" offensive. Current reporting (1454Z) involves direct claims by Putin and Gerasimov of a 15km proximity to Zaporizhzhia city limits, alongside the reported capture of Lukyanivske.
- Sumy Axis: NEW THREAT VECTOR. A new RF narrative (claiming forces 20km from Sumy) has emerged, supported by "Group North" command statements, creating a dilemma for UAF reserve allocation.
- SAR Focus Shift: AIR DEFENSE SURGE. While the previous report flagged Bomber activity (Shaykovka), current SAR data highlights a massive spike in Air Defense activity at the 1528th Anti-Aircraft Missile Regiment (Score 30.84 - RISING), indicating a defensive hardening of the RF rear.
- Diplomatic Clarity: DEFINED FRAMEWORK. The ambiguous "peace meeting" from yesterday has crystallized into a confirmed 15-year security pact proposal and a $100bn reparation mechanism.
3. THREAT ASSESSMENT
(SAR Score Legend: 0-5 Low/Routine | 5-15 Moderate/Monitor | 15+ High/Critical)
- Zaporizhzhia Breakthrough (THREAT LEVEL: CRITICAL):
- Indicator: RF 35th Army intensification near Orikhiv and claims of capturing Lukyanivske.
- Assessment: (HIGH CONFIDENCE) The coordinated messaging by Putin/Gerasimov regarding the "15km" line indicates this is the RF Main Effort. The capture of Lukyanivske suggests the defensive belt is bending; a breach here threatens the logistics of the entire Southern Grouping.
- Strategic Air Defense Hardening (THREAT LEVEL: HIGH):
- SAR Analysis: 1528th Anti-Aircraft Missile Regiment HQ surged to Score 30.84. Simultaneously, the 583rd AA Regiment rose to 15.66.
- Assessment: (MEDIUM CONFIDENCE) RF is likely repositioning strategic AD assets to protect key command nodes or staging areas from UAF deep strikes anticipated following the US-UA security pact announcement.
- Northern Diversion (Sumy) (THREAT LEVEL: MEDIUM):
- Indicator: Claims of RF presence 20km from Sumy; "Group North" activity.
- Assessment: (LOW CONFIDENCE) Currently assessed as an Information Operation (IO) or Special Operations Forces (SOF) probe to fix UAF reserves. Visual confirmation is lacking.
4. OPERATIONAL DEVELOPMENTS
- Southern Axis (Zaporizhzhia/Nikopol):
- Orikhiv/Primorske: RF "Vostok" and "Dnipro" groups are conducting a multi-pronged push. RF claims control of Lukyanivske. Gerasimov explicitly targeting Zaporizhzhia city.
- Nikopol: Imminent threat from UAV group (Shahed-type) tracking from Zaporizhzhia Oblast (1439Z).
- Eastern Axis (Lyman/Donbas):
- Lyman: Dibrova confirmed lost. RF intending to use this foothold to strike towards Zarichne.
- Pokrovsk: Flanks eroding; RF claims SE sector of Gryshyne captured. However, UAF 7th Corps (DShV) continues to stabilize the northern industrial sector.
- Northern Axis (Kharkiv/Sumy):
- Kupyansk: RF Commander Kuzovlev set a "liquidation" timeline for Feb 2026.
- Sumy: Unverified reports of RF units 20km from the city.
- Rear Area/Hybrid:
- Kyiv: SBU neutralized a joint RF/Belarusian agent targeting Thermal Power Plants (TPPs).
- Infrastructure: Private companies authorized to procure internal Electronic Warfare (EW) systems for facility protection.
5. INTELLIGENCE GAPS
- P1 (Ground Truth): Zaporizhzhia FEBA. Urgent verification of the Forward Edge of Battle Area (FEBA) south of Zaporizhzhia is required. Does the "15km" claim reflect a recon element or a consolidated main force line?
- P2 (Enemy Intent): 1528th AA Regiment. Why has the 1528th surged to Score 30.84? Determine if this unit is deploying to the border or protecting a specific logistical hub (e.g., an "Oreshnik" staging site).
- P3 (Tactical): "Omich" Robot Status. No visual confirmation of "Omich" platforms in the last 24h despite previous warnings. Have they been deployed to the Oskil river line yet?
6. PREDICTIVE ANALYSIS (NEXT 24-48 HOURS)
- MLCOA (Lyman Expansion & Southern Pressure): (HIGH CONFIDENCE) Capitalizing on the capture of Dibrova, RF forces will launch immediate assaults toward Torske to sever the supply lines for UAF units in the Serebryanske Forest. Simultaneously, heavy mechanized pressure will continue near Orikhiv to validate the Kremlin's "15km" narrative.
- MDCOA (Northern Opening): (MEDIUM CONFIDENCE) RF converts the Sumy IO threat into a kinetic reality by launching a battalion-sized cross-border raid NLT 2025-12-30 0600Z, aiming to panic UAF command into diverting reserves meant for Zaporizhzhia.
- Strategic Expectation: (HIGH CONFIDENCE) Expect a high-volume missile/UAV strike on energy infrastructure (specifically Naftogaz/heating) tonight to test the "private EW" defenses mentioned by PM Shmyhal and punish the US-UA pact.
7. RECOMMENDATIONS
- ISR Retasking: PRIORITY 1. Redirect satellite and high-altitude UAV assets to the Sumy border region immediately to confirm/deny the presence of RF armored columns supporting the "20km" claim.
- Defensive Reinforcement: LYMAN SECTOR. Command must authorize immediate reinforcement or a controlled retrograde for units in Serebryanske Forest to prevent encirclement following the loss of Dibrova.
- Civil Defense: ZAPORIZHZHIA EVACUATION. Given the high confidence in RF prioritization of the Zaporizhzhia axis and the 15km claim, accelerate evacuation protocols for the southern suburbs of the city NLT 2025-12-29 2000Z.
- Counter-IO: REALITY CHECK. Release geolocated footage of UAF positions south of the 15km mark (if held) to debunk the Putin/Gerasimov narrative and maintain civilian morale in Zaporizhzhia.
//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 28 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
4 visualsGeospatial Analysis
12 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 12 places with coordinates
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Dibrova | UA | 48.76431119999999, 37.8324032 | |
| Zaporizhzhia City | UA | 47.83928419999999, 35.13870970000001 | |
| Lukyanivske | UA | 47.6108276, 35.4451503 | |
| Sumy | UA | 50.9077, 34.7981 | |
| 1528th Anti-Aircraft Missile Regiment HQ | RU | 0, 0 | |
| Orikhiv/Primorske Contact Area | UA | 47.6424248, 35.2962326 | |
| Nikopol | UA | 47.56746, 34.394815 | |
| Serebryanske Forest | UA | 48.015883, 37.80285 | |
| Kupyansk | UA | 49.7055574, 37.6027997 | |
| Kyiv Thermal Power Plants (TPPs) | UA | 50.4503596, 30.5245025 | |
| Gryshyne | UA | 48.015883, 37.80285 | |
| Zarichne | UA | 49.0221765, 37.9271381 |
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.
