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-21 18:01:00Z
1. EXECUTIVE SUMMARY
(HIGH CONFIDENCE) CRITICAL UPDATE: The operational situation has deteriorated significantly as the Russian Federation (RF) synchronizes the active kinetic breach at Pokrovsk with a lethal hybrid campaign in the Ukrainian deep rear. While the 40th and 155th Separate Marine Brigades (OMBR) exploit gaps west of Mirnohrad, a new fatal explosion at an Odesa Recruitment Center (TCC) and amplified political friction (addressed directly by the UAF Supreme Commander) indicate a coordinated effort to induce internal paralysis. Synthetic Aperture Radar (SAR) confirms a massive logistics surge at the 2652th Artillery Armament Base, signaling that the anticipated strategic missile strike is fueled and imminent.
2. CHANGES FROM PREVIOUS REPORT
- Ground Situation (ESCALATION): The Pokrovsk sector has officially transitioned to "Active Exploitation," with RF forces attempting to maneuver rather than just assault.
- Hybrid Threat (NEW): A confirmed fatal explosion at an Odesa TCC represents a shift from general shelling to targeted internal sabotage/terrorism against mobilization infrastructure.
- Logistics Intelligence (UPDATED): While previous reports monitored the 260th GRAU base, new SAR data identifies the 2652th Artillery Armament and Ammunition Base as the primary node for immediate reconstitution (Score 24.38 - RISING sharply).
- Deep Strike Capability (NEW): UAF has successfully expanded deep strikes beyond rail sabotage to kinetic infrastructure targets in Slavyansk-na-Kubani (Krasnodar Krai), confirming reach into the Black Sea adjacent rear.
- Political/Information Environment (SHIFT): The threat landscape now includes acute "Internal Political Fracture" as a critical vulnerability, evidenced by President Zelensky’s urgent public address regarding internal disputes ("srach") and direct engagement with US VP Vance.
3. THREAT ASSESSMENT
- Pokrovsk-Mirnohrad Breach (THREAT LEVEL: CRITICAL): The defensive line is breached. The primary threat is now the physical severance of the Kostiantynivka Ground Line of Communication (GLOC) by RF Spetsnaz (SpN) operating in the tactical rear. (HIGH CONFIDENCE)
- Internal Stability/Hybrid (THREAT LEVEL: HIGH - RISING): The Odesa TCC incident suggests RF intelligence services have activated deep-cover assets to violently disrupt mobilization, aiming to compound the effects of the "US Peace Plan" disinformation narratives. (MEDIUM-HIGH CONFIDENCE)
- Strategic Missile Strike (THREAT LEVEL: CRITICAL - IMMINENT): The reconstitution rate at 2652th GRAU (Delta +13.75) combined with the previous UAV saturation confirms the missile strike package is assembled. Impact is expected within 12-24 hours. (HIGH CONFIDENCE)
4. OPERATIONAL DEVELOPMENTS
- Pokrovsk Axis: 40th/155th OMBR are conducting high-tempo mechanized maneuvers. UAF reserves are deploying for counter-penetration but face heavy RF interdiction fire.
- Deep Rear (UAF): Confirmed successful UAV strike on Slavyansk-na-Kubani, causing casualties and infrastructure damage. This sustains the counter-logistics pressure established by the Sverdlovsk/Perm rail attacks.
- Deep Rear (RF Hybrid): Fatal explosion at Odesa TCC. This creates a dual-front dilemma: frontline combat vs. rear-area security.
- Diplomatic/Political: High-level contact established between UAF National Command Authority (NCA) and US Vice President Vance to mitigate the destabilizing effects of the "territorial concession" rumors.
5. INTELLIGENCE GAPS
- PRIORITY 1 (IMMEDIATE): Odesa TCC Forensics. Was the explosion caused by a timer-based IED, a suicide drone, or an internal agent? Determining the vector is essential to protecting other TCCs.
- PRIORITY 2 (TARGETING): 2652th GRAU Cargo Manifest. SAR shows high activity, but we lack confirmation of whether the shipment involves Kinzhal (Hypersonic) or Kalibr (Cruise) missiles, which dictates AD dispersal protocols.
- PRIORITY 3 (TACTICAL): Spetsnaz Infiltration Coordinates. Exact location of RF SpN teams targeting the Kostiantynivka GLOC remains unknown despite their assessed proximity (5-10km).
6. PREDICTIVE ANALYSIS (NEXT 24-48 HOURS)
- MLCOA (Coordinated Paralysis): (HIGH CONFIDENCE) RF will launch the strategic missile strike (from 2652th/260th stocks) targeting energy and C2 nodes tonight/early morning. Simultaneously, sabotage groups will strike a second TCC or mobilization node to maximize panic. On the front, mechanized forces will attempt to physically cut the M-30/T-05-15 road.
- MDCOA (Strategic Collapse): (MEDIUM CONFIDENCE) The combination of the Odesa attack, the "Peace Plan" rumors, and a successful missile strike leads to a temporary breakdown in UAF National Command Authority cohesion. This results in contradictory orders to the Pokrovsk sector, allowing the 40th OMBR to encircle defending units before reserves can engage.
7. RECOMMENDATIONS
- Force Protection (Internal) (IMMEDIATE - J2/Security Services): Raise Force Protection Condition to DELTA for all TCCs and mobilization centers in Odesa, Dnipro, and Kyiv. Deploy counter-sabotage teams to perimeter defense; assume further hybrid attacks are imminent.
- GLOC Security (IMMEDIATE - J3): Deploy Task Force Raven (Mobile Reserve) specifically to the Kostiantynivka GLOC. Rules of Engagement (ROE) must authorize aggressive preemptive fires against any unidentified personnel within 5km of the supply route.
- Air Defense Re-Tasking (URGENT - Air Force): Based on SAR activity at 2652th GRAU, transition all Patriot/SAMP-T batteries to Anti-Ballistic Mode. Cease engagement of single Shahed/Geran UAVs with high-value interceptors; prioritize energy and C2 protection.
- Information Operations (STRATCOM): Immediately publicize the Slavyansk-na-Kubani strike. Frame the narrative as "Russia burns while it lies," to counter the domestic demoralization caused by the Odesa TCC incident and political rumors.
//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 20 Nov 2025, 23:31 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
7 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 7 places with coordinates
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Pokrovsk | UA | 48.282193, 37.1847804 | |
| TCC Odesa | UA | 46.4845702, 30.7326047 | |
| 2652th Artillery Armament and Ammunition Base | RU | 0, 0 | |
| Slavyansk-na-Kubani | RU | 45.2605456, 38.1258833 | |
| Kostiantynivka GLOC | UA | 48.52394289999999, 37.7075811 | |
| Kyiv | UA | 50.0529506, 30.7667133 | |
| Dnipro | 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.
