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-11-30 15:01:05Z
1. EXECUTIVE SUMMARY
(CRITICAL) MULTI-DOMAIN CRISIS SYNCHRONIZATION: The conflict has shifted into a "Multi-Domain Crisis" phase. RF forces have breached the urban periphery of Pokrovsk, infiltrating the city limits and engaging the UAF SKELIA Regiment. This kinetic escalation is perfectly synchronized with a strategic Information Operations (IO) crisis regarding UAF-US peace negotiations (the "Umerov Post Deletion" incident), designed to paralyze National Command Authority (NCA) decision-making. While UAF scored a significant deep-strike success against the Alabuga drone facility, the loss of the Sumy ammunition depot and the imminent threat to the Pokrovsk Ground Line of Communication (GLOC) represent a critical operational danger.
2. CHANGES FROM PREVIOUS REPORT
- Donetsk Front (ESCALATED): Changed from "Tactical Threat" to "Urban Infiltration." RF units have bypassed Hryshyne defenses and entered Pokrovsk proper; the battle is now Close Quarters Combat (CQC).
- Unmanned Systems (UAF SUCCESS): First confirmed operational success of the UAF "Sting" interceptor drone against RF loitering munitions, and the 5th Assault Brigade (5 OShB) recorded the first UGV-on-Vehicle kill (destroying an RF MT-LB). This challenges the previous assessment of total RF BPS (Drone Systems Troops) dominance.
- Deep Strike Status (MIXED): UAF successfully struck the Alabuga Special Economic Zone (RF drone production hub), a significant strategic success. However, RF strikes destroyed a key UAF ammunition depot in Sumy, degrading immediate reserve fire capabilities.
- Strategic IO (CRITICAL INSTABILITY): The threat has shifted from general "Internal Destabilization" to specific "Diplomatic Decapitation." RF is leveraging the deletion of Defense Minister Umerov's social media post to fabricate a narrative of UAF surrender during active US negotiations.
3. THREAT ASSESSMENT
- Pokrovsk Urban Control (THREAT LEVEL: CRITICAL): RF infiltration into the city threatens to physically sever the primary GLOC within 4 hours. The failure/delay of the R-1 Fire Mission (reserve artillery) dramatically increases the probability of city-wide entrapment. (HIGH CONFIDENCE)
- Cognitive Paralysis (THREAT LEVEL: HIGH): The synchronization of the Pokrovsk breach with the "Umerov Diplomatic Crisis" creates a high risk of hesitancy in committing UAF Strategic Reserves. RF IO is successfully framing tactical withdrawals as strategic capitulation. (HIGH CONFIDENCE)
- Southern Axis Air Superiority (THREAT LEVEL: HIGH): RF tactical aviation activity has spiked in the Southeast. Combined with SAR data showing the 1488th Anti-Aircraft Missile Regiment at a score of 13.88 - RISING*, RF is establishing an AD/Air umbrella to support a secondary breakthrough attempt at Stepnohorsk.
- Legend: SAR Score 0-5 (Low), 5-10 (Moderate), 10-25 (High), 25+ (Critical).
- Logistical Sustainment (THREAT LEVEL: MEDIUM): While the Alabuga strike hurts RF long-term, their immediate logistics are sustained via the Kazakhstan corridor. Conversely, the Sumy depot loss constrains UAF high-caliber fire support for the next 48-72 hours. (HIGH CONFIDENCE)
4. OPERATIONAL DEVELOPMENTS
- Pokrovsk Infiltration: RF elements have penetrated the city outskirts. The UAF SKELIA Regiment (425th) is engaged in urban defense utilizing FPV drones to disrupt RF infantry, but lacks heavy fire support.
- Hryshyne Consolidation: RF forces have consolidated positions in Hryshyne, securing the flank for the push into Pokrovsk.
- Technological Counter-Attack: The 5 OShB successfully deployed an armed UGV to destroy an RF MT-LB, providing the first validated TTP (Tactics, Techniques, and Procedures) for ground-robotic counter-mobility.
- Deep Strike Campaign: UAF UAS successfully targeted the Alabuga drone production facility in Tatarstan. Simultaneously, GUR sabotage units conducted operations against occupation forces in Berdyansk.
- Northern Axis Alert: Increased RF tactical aviation activity reported near Kupyansk/Lyman, suggesting a potential shaping operation to fix UAF forces in the north while the main effort presses in Donetsk.
5. INTELLIGENCE GAPS
- PRIORITY 1 (KINETIC STATUS): R-1 Fire Mission Execution. Confirmation is urgently required: Did the planned artillery interdiction against Hryshyne/Pokrovsk RF concentrations occur NLT 1530Z?
- PRIORITY 2 (SIGINT): Tactical Air Frequencies. Identification of C2 frequencies for the surged RF tactical aviation in the South-East to enable "Sting" interceptor and EW targeting.
- PRIORITY 3 (HUMINT/DIPLOMATIC): US Negotiation "Red Lines." Precise understanding of the friction points in the Umerov-US talks is needed to effectively counter the RF "surrender" narrative.
6. PREDICTIVE ANALYSIS (NEXT 24-48 HOURS)
- MLCOA (Urban Siege & Narrative Lock): (HIGH CONFIDENCE) RF will consolidate the Pokrovsk breach NLT 2025-11-30 2000Z, severing the GLOC. They will immediately utilize this tactical success to validate the "UAF collapse" narrative during the US peace talks, aiming to force unfavorable terms.
- MDCOA (Domino Collapse): (MEDIUM CONFIDENCE) RF synchronizes the Pokrovsk pressure with a "blind" ground assault on Stepnohorsk (Southern Axis) under cover of the surged tactical aviation. If UAF reserves remain frozen due to NCA diplomatic confusion, the Southern front may experience a breakthrough parallel to the Donetsk urban fight.
7. RECOMMENDATIONS
- Urban Fire Support (IMMEDIATE - J3): EXECUTE R-1 (MODIFIED). If the original interdiction window is missed, shift fire missions immediately to Close Quarters Support for the SKELIA Regiment within Pokrovsk. Accept higher collateral risk to prevent total GLOC severance NLT 2025-11-30 1600Z.
- Strategic Communications (IMMEDIATE - NCA): PROTOCOL "UNITY". The NCA must issue a visual address NLT 2025-11-30 1630Z explaining the Umerov post deletion (e.g., "operational security adjustment") and explicitly rejecting capitulation. The narrative must pivot to the Alabuga strike success and SKELIA's defense to restore morale.
- Counter-Drone Deployment (URGENT - J3/Tech): DEPLOY "STING" & UGV TTPs. Immediately transfer the "Sting" interceptor units and 5 OShB's anti-vehicle UGV TTPs to the Stepnohorsk sector. These assets are required to counter the RF A2A and UGV threat in the South where traditional air defense is suppressed.
- Deep Strike Follow-Up (URGENT - J2): TARGET KAZAKH NODES. Capitalize on the Alabuga success by executing prepared strike packages against the Caspian/Volga rail hubs supporting the Kazakh corridor NLT 2025-12-01 0400Z. RF logistics must be destabilized while they are focused on the Pokrovsk offensive.
//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 29 Nov 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
9 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 9 places with coordinates
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Pokrovsk | UA | 48.282193, 37.1847804 | |
| Alabuga Special Economic Zone | RU | 55.8354977, 52.067629 | |
| Sumy Ammunition Depot | UA | 50.9077, 34.7981 | |
| Hryshyne | UA | 48.31771209999999, 37.0903532 | |
| Stepnohorsk | UA | 47.5869326, 35.358148 | |
| Kupyansk/Lyman Sector | UA | 49.7055574, 37.6027997 | |
| Berdyansk | UA | 46.7737707, 36.8034779 | |
| Kazakhstan Corridor Rail Hubs (Caspian/Volga) | RU | 41.934977, 50.66894500000001 | |
| 1488th Anti-Aircraft Missile Regiment Position | RU | 61.52401, 105.318756 |
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.
