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-14 DTG: 2025-12-14T16:00Z
1. EXECUTIVE SUMMARY
(CRITICAL) OPERATIONAL RESILIENCE & KINETIC ESCALATION: The Pokrovsk sector remains stabilized as the UAF 7th Separate Airborne Assault Brigade (7 KShDV) successfully repelled a major RF mechanized push near Hryshyne, validating the "Contested" assessment. However, the kinetic threat level has critically escalated with the confirmed RF deployment of a double-warhead Shahed-136 variant (100kg payload) and the expansion of Guided Aerial Bomb (KAB) strikes into the Zaporizhzhia operational rear. Contrary to previous assessments of a logistical pause, SAR data indicates a sudden, critical surge in activity at the 260th GRAU arsenal, suggesting an imminent renewal of saturation fires.
2. CHANGES FROM PREVIOUS REPORT
- Pokrovsk Sector (CONFIRMATION): The successful defense by 7 KShDV (destroying an RF column in fog) reinforces yesterday’s assessment of a "Contested" front, moving beyond the initial "Skelya 425" counter-attack to a sustained defensive hold.
- Aerial Threat (ESCALATION): Intelligence confirms a new Shahed variant with a dual warhead (100kg total), doubling the destructive potential against hardened infrastructure compared to previous models.
- 260th GRAU (REACTIVATION): Previous reporting indicated a failure/delay in the expected barrage (Score 0.00). NEW SAR DATA (2025-12-14) indicates a massive spike in activity (Score 26.95 - CRITICAL), suggesting the depot is actively onloading/offloading for a renewed surge.
- Legend: SAR Score 0-5 (Low), 5-10 (Moderate), 10-25 (High), 25+ (Critical).
- Deep Strike Capabilities (SUCCESS): UAF operations have shifted from purely logistical targets to dismantling the RF Integrated Air Defense System (IADS) in Crimea, confirming the destruction of Kasta-2E2 and S-400 (96L6) radar nodes.
3. THREAT ASSESSMENT
- Air/Missile Threat (THREAT LEVEL: CRITICAL):
- New Shahed Variant: The 100kg payload variant poses a severe risk to energy infrastructure and hardened command posts previously resilient to standard strikes.
- KAB Deep Strike: Confirmed expansion of KAB launch zones targeting Zaporizhzhia Oblast (rear area), threatening the Southern logistical spine in addition to the previously identified Dnipro vector.
- Logistics/Artillery (THREAT LEVEL: HIGH - RISING): The sudden SAR activity spike at the 260th Main Missile and Artillery Directorate (GRAU) arsenal indicates the previous "pause" was likely a reload cycle. Expect renewed high-intensity artillery saturation on the Eastern Axis within 24-48 hours.
- Hybrid/IO (THREAT LEVEL: HIGH):
- Diplomatic Coercion: RF information operations are likely to leverage the Zelenskyy-US (Witkoff/Kushner) meeting in Berlin to push narratives of "external management" or "peace traps," especially if no immediate aid package is announced.
- Odesa Stability: The threat of hybrid unrest targeting TCCs (Territorial Recruitment Centers) remains high due to persistent infrastructure failure, though no physical attacks were reported in the last 12 hours.
4. OPERATIONAL DEVELOPMENTS
- Eastern Axis (Donetsk):
- Pokrovsk/Hryshyne: UAF 7 KShDV utilized heavy fog to ambush and destroy an RF mechanized column. This confirms UAF tactical control of the Hryshyne approaches.
- Logistics Interdiction: UAF struck an RF repair/maintenance base in occupied Donetsk, degrading local armor regeneration capabilities.
- Southern Axis (Crimea/Zaporizhzhia):
- Crimea SEAD (Suppression of Enemy Air Defenses): GUR "Ghosts" unit confirmed destruction of 39N6 "Kasta-2E2" (low-altitude) and 96L6 (S-400 component) radars. This creates a temporary blind spot in RF IADS over the peninsula.
- Zaporizhzhia City: RF executed KAB/missile strikes on civilian infrastructure; UAF detected and engaged RF reconnaissance UAVs over Kherson, indicating pre-strike shaping.
- Northern Axis/Deep Rear:
- Volgograd (RF): Confirmed UAF strike on Uryupinsk oil depot, extending the engagement zone significantly eastward.
- Sumy: RF drone strike hit residential infrastructure; UAF SSO neutralized an RF "Storm" sabotage group infiltrating the border forest area.
- Diplomatic/Strategic:
- President Zelenskyy initiated high-level talks with US negotiators in Berlin.
- Belarusian opposition figures released in the prisoner swap held a press conference in Kyiv, a significant IO win for GUR.
5. INTELLIGENCE GAPS
- P1 (CRITICAL): Technical Analysis of Dual-Warhead Shahed. Immediate recovery of wreckage required to determine fuse type, guidance modifications, and terminal behavior for AD adjustment.
- P2 (URGENT): 260th GRAU Vector. SAR shows activity is "CRITICAL" (26.95). Is this material arriving for storage, or departing for the front? Identifying the rail output destination (Volnovakha vs. Ilovaisk) is essential for predicting the next main effort.
- P3 (PRIORITY): Huliaipole Status. RF claims of a breakthrough remain unverified (PERSISTENT GAP). Need visual confirmation of the Line of Contact (LOC).
- P4 (DIPLOMATIC): Berlin Outcomes. Specifics on security guarantees or munitions released from the Zelenskyy-Witkoff meeting to inform near-term sustainment planning.
6. PREDICTIVE ANALYSIS (NEXT 24-48 HOURS)
- MLCOA (Retaliatory Saturation): (HIGH CONFIDENCE) Stung by the loss of S-400 radars in Crimea, RF will launch a complex air attack targeting Odesa and Dnipro within 24 hours, utilizing the new 100kg Shahed variants to overwhelm degraded AD. Simultaneously, ground forces at Pokrovsk will pause mechanized assaults to wait for the munitions surge observed at the 260th GRAU.
- MDCOA (Logistical Strangulation): (MEDIUM CONFIDENCE) RF leverages the KAB expansion into Zaporizhzhia and the new Shahed capabilities to sever the Donetsk-Dnipro GLOCs (Ground Lines of Communication) completely. If successful, this isolates the Pokrovsk defenders from the supplies necessary to exploit their recent defensive victories.
7. RECOMMENDATIONS
- Air Defense (IMMEDIATE - J3): ADJUST ENGAGEMENT PROTOCOLS. Issue immediate guidance to Mobile Fire Groups (MFGs) and SHORAD units regarding the 100kg Shahed. The increased payload likely requires earlier interception ranges to prevent critical damage from debris/blast wave near protected assets.
- Trigger: Immediate dissemination of technical intel.
- ISR (PRIORITY - J2): TRACK 260th GRAU OUTFLOW. Re-task orbital and HUMINT assets to monitor rail lines exiting the 260th arsenal. If trains move south toward Rostov/Donbas, expect a renewed artillery offensive in 48-72 hours.
- Trigger: Movement of rolling stock from depot sidings.
- Operations (URGENT - OC South): EXPLOIT IADS GAP. Capitalize on the destruction of the S-400 and Kasta radars in Crimea. Authorize immediate deep-strike planning against Crimean logistics hubs while the RF air picture is degraded.
- Trigger: Confirmation of RF radar downtime (SIGINT silence).
- Maneuver (SUSTAIN - OC East): RESUPPLY 7 KShDV. Prioritize Class III/V resupply to the 7th Brigade during the current fog/weather window. They have expended significant ordnance stopping the column and require restocking before the 260th GRAU surge arrives.
//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 13 Dec 2025, 15:02 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
10 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 10 places with coordinates
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Pokrovsk/Hryshyne Front Line | UA | 48.31771209999999, 37.0903532 | |
| 260th GRAU Arsenal | UA | 48.015883, 37.80285 | |
| Kasta-2E2 Radar Site | UA | 0, 0 | |
| S-400 (96L6) Radar Node | UA | 48.379433, 31.16558 | |
| Uryupinsk Oil Depot | RU | 50.7974183, 42.0056002 | |
| Zaporizhzhia Oblast Rear Area | UA | 47.8388, 35.139567 | |
| RF Armor Repair Base | UA | 48.015883, 37.80285 | |
| Donetsk-Dnipro GLOCs | UA | 48.10421789999999, 36.9959521 | |
| Sumy Border Forest Area | UA | 50.9077, 34.7981 | |
| Odesa/Dnipro Critical Infrastructure | UA | 48.464717, 35.046183 |
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.
