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 – 2026-01-11 DTG: 2026-01-11T15:00Z AOR: Eastern Europe / Ukraine / Caspian Sea / Russian Strategic Rear
1. EXECUTIVE SUMMARY
(NEW) The conflict’s strategic geography has expanded dramatically with the first confirmed Ukrainian Special Operations Forces (SOF) strike on Russian energy infrastructure in the Caspian Sea (1433Z), successfully hitting three Lukoil drilling platforms. Concurrently, a "Logistical Crisis" has emerged in the Ukrainian rear: severe winter weather has physically collapsed critical anti-drone protective screens in Zaporizhzhia, while systemic Russian interdiction has delayed over 60 trains, paralyzing internal Ground Lines of Communication (GLOC). Tactically, Russian Federation (RF) forces have achieved a breach in the Zaporizhzhia sector, capturing Belogorye, supported by a critical spike in Command and Control (C2) activity at the 49th Combined Arms Army (CAA) HQ.
2. CHANGES FROM PREVIOUS REPORT
- Strategic Reach: EXTENDED. Previous assessments focused on Volgograd (900km). New data confirms strikes on the Caspian shelf (1,500km+), forcing a dilemma for RF Air Defense (AD) allocation.
- Zaporizhzhia Front: DEFENSIVE BREACH. The "Contested" status of Zelene/Huliaipole flanks has deteriorated. Belogorye is assessed as LOST (High Confidence), and the physical collapse of anti-drone tunnels (1305Z) exposes previously safe supply routes to immediate interdiction.
- Logistics Integrity: SEVERELY DEGRADED. The previous report noted grid instability. Current intelligence confirms a systemic rail paralysis (60+ trains stalled) and the physical destruction of road protection measures due to weather.
- Aerial Threat: TACTICAL EVOLUTION. Emergence of "Molniya" drone swarms (26 intercepted in one wave, 1400Z) represents a shift from sporadic harassment to high-volume saturation aimed at depleting Short Range Air Defense (SHORAD) magazines.
3. THREAT ASSESSMENT
(SAR Score Legend: 0-5 Low/Routine | 5-15 Moderate/Monitor | 15+ High/Critical)
- Southern Axis Offensive C2 (THREAT LEVEL: CRITICAL)
- Indicators: 49th Combined Arms Army HQ SAR Score 16.71 (RISING); 689th GRU Intel Center SAR Score 16.92 (RISING).
- Assessment: (HIGH CONFIDENCE) The coordinated spike in SAR activity at the 49th CAA HQ and its associated GRU node indicates a major command push to exploit the tactical capture of Belogorye. This is not a localized skirmish but a synchronized offensive effort.
- Logistical "Kill Zones" (THREAT LEVEL: HIGH)
- Indicators: Validated collapse of anti-drone meshes/tunnels due to wind (1403Z); delayed rail traffic (1315Z).
- Assessment: (HIGH CONFIDENCE) RF drone operators will immediately exploit the loss of physical overhead cover on Zaporizhzhia roads. Resupply convoys are currently naked to FPV strikes until Electronic Warfare (EW) assets are repositioned.
- Shahed Supply Chain (THREAT LEVEL: VARIABLE)
- Indicators: Instability in Iran; Belief Score 0.094 (Logistical Shift).
- Assessment: (MEDIUM CONFIDENCE) While current stocks allow for saturation (650+ UAVs destroyed in 24h), domestic unrest in Iran may disrupt the medium-term flow of Shahed components to the RF.
4. OPERATIONAL DEVELOPMENTS
- Strategic / Deep Strike:
- Caspian Sea: UAF SOF confirmed strikes on Lukoil platforms V. Filanovsky, Yuri Korchagin, and Valery Grayfer (1433Z). Video BDA confirms kinetic impact and fires.
- Snake Island: UAF DPSU maintains control; video released to counter RF narratives (1449Z).
- Northern Axis (Kyiv/Zhytomyr/Sumy):
- Zhytomyr: UAV transit detected moving west toward Narodychi (1436Z).
- Sumy: RF pushing KAB (Guided Aerial Bomb) strikes to shape the battlefield; false RF narrative of UAF withdrawal circulated (0445Z).
- Eastern Axis (Donbas):
- Pokrovsk: RF assault repelled (1410Z), but high attrition noted.
- Lyman: Presence of African mercenaries confirmed via FPV footage (1440Z), corroborating POW testimony of "meat assault" tactics using non-national personnel.
- Southern Axis (Zaporizhzhia):
- Belogorye: Confirmed capture by RF forces (0959Z).
- Road Network: Anti-drone protection infrastructure failed due to weather; routes explicitly vulnerable (1403Z).
5. INTELLIGENCE GAPS
- P1 (Battle Damage Assessment): Caspian Oil Output. Specific impact on crude flow from the Filanovsky platform is required to assess the economic pain threshold for Moscow.
- P2 (Tech Intelligence): "Molniya" Drone Specs. Debris analysis from the 26 downed units (1400Z) is needed to determine guidance method (optical vs. GPS) to tune EW jammers.
- P3 (Enemy Intent): 49th CAA Objective. Does the SAR spike at 49th CAA HQ indicate a drive for Huliaipole proper, or a turning maneuver to cut the T0803 highway?
6. PREDICTIVE ANALYSIS
- MLCOA (Retaliatory Grid Strike): (HIGH CONFIDENCE) In response to the humiliation of the Caspian strikes, RF Strategic Aviation (Tu-95MS) will launch a missile wave NLT 2026-01-12 0400Z targeting Kyiv energy nodes and stranded rail segments. The current UAV activity over Zhytomyr is a route-clearing/AD-mapping precursor.
- MDCOA (Zaporizhzhia Breakthrough): (MEDIUM CONFIDENCE) RF forces exploit the weather-induced collapse of UAF anti-drone screens. Mechanized units from the 49th CAA, masking under the weather, push rapidly from Belogorye to sever the H-15 highway while UAF logistics are paralyzed by the lack of road cover and rail delays.
- IO Forecast: (HIGH CONFIDENCE) RF will intensify the "Depleted AD" narrative (citing Klitschko fakes) to lower Western confidence in resupply efficacy during the rail crisis.
7. RECOMMENDATIONS
- Electronic Shielding (Zaporizhzhia): TRIGGER: Collapse of physical anti-drone tunnels. ACTION: Immediately redeploy mobile EW teams ("Bukovel" or equivalent) to the Huliaipole supply route to create an electronic dome replacing the physical one. End state: Restoration of logistical throughput NLT 2026-01-11 2000Z.
- Rail Protection: TRIGGER: 60+ train delays. ACTION: Prioritize mobile AD coverage (Gepard/Avenger) for major rail choke points where trains are currently static targets.
- Caspian Retaliation Prep: TRIGGER: Confirmed SOF strike. ACTION: Disperse all strategic aviation and SOF basing assets immediately. Expect RF retribution strikes targeting the units responsible for the Caspian operation.
- Counter-Mercenary IO: TRIGGER: Visual confirmation of African combatants. ACTION: Disseminate POW testimony (169th Bde) and drone footage of mercenaries to African media outlets to disrupt RF recruitment pipelines abroad.
//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 10 Jan 2026, 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 |
|---|---|---|---|
| Caspian Sea Drilling Platforms (Filanovsky, Korchagin, Grayfer) | RU | 61.52401, 105.318756 | |
| Belogorye | UA | 47.8388, 35.139567 | |
| 49th Combined Arms Army (CAA) HQ | UA | 47.8388, 35.139567 | |
| 689th GRU Intel Center | UA | 47.8388, 35.139567 | |
| Zaporizhzhia Logistics Corridor (GLOCs) | UA | 47.83928419999999, 35.13870970000001 | |
| Huliaipole | UA | 47.6607145, 36.2732384 | |
| Kyiv Energy Nodes | UA | 50.4503596, 30.5245025 | |
| Snake Island | UA | 46.484583, 30.7326 | |
| Zhytomyr Airspace | UA | 50.2615588, 28.6666776 | |
| Sumy Battlefield Shaping Area | UA | 50.9077, 34.7981 | |
| Pokrovsk | UA | 48.282193, 37.1847804 | |
| Lyman Engagement Zone | UA | 48.9897585, 37.8049964 |
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.
