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-24 15:30:00Z
1. EXECUTIVE SUMMARY
(HIGH CONFIDENCE) IMMINENT STRATEGIC STRIKE: The conflict window has entered a terminal phase regarding the anticipated ballistic missile strike, now confirmed for No Later Than (NLT) 240000Z. Precursor drone waves (Shahed/Geran) are currently probing Northern and Central sectors to deplete Ukrainian Air Defense (AD) interceptors ahead of the main salvo. Simultaneously, the relief force "Plan 7-B MOD" has gone communications-dark during transit to Rodynske, creating a critical vulnerability on the Pokrovsk Axis as Russian Federation (RF) forces transition from maneuver to kinetic interdiction using Glide Bombs (KABs) in Zaporizhzhia to fix potential reinforcements.
2. CHANGES FROM PREVIOUS REPORT
- Southern Axis Tactics (ESCALATION): RF operations in Zaporizhzhia have shifted from flanking maneuvers (west of Stepnohirsk) to active kinetic fixation. Confirmed KAB launches (241451Z, 241453Z) indicate a move to physically destroy infrastructure and pin UAF reserves, rather than just bypass them.
- IO Narrative (EVOLUTION): The Information Operation (IO) has evolved from seeding a "fake Geneva plan" to high-ranking RF officials formally endorsing a modified "19-point framework." This pivots the threat from confusion to diplomatic entrapment, aiming to portray Kyiv as the intransigent party to delay Western support during the strike window.
- SAR Indicators (NEW): Synthetic Aperture Radar (SAR) analysis highlights rising activity at AB Monchegorsk (Score 8.37 - RISING), a known strategic bomber base, and the 531st Guards Anti-Aircraft Missile Regiment (Score 14.39 - RISING), corroborating the timeline for a major coordinated aerial offensive.
- Reserve Status (CRITICAL GAP): The status of "Plan 7-B MOD" has degraded to CRITICAL GAP 1. Unlike the previous report where deployment was "delayed," the force is now in transit but lacking real-time Command and Control (C2) reporting (as of 241505Z).
3. THREAT ASSESSMENT
- Strategic Decapitation (THREAT LEVEL: CRITICAL): The NLT 240000Z timeline for the ballistic strike is active. The RF intent is to destroy C2 nodes in Dnipropetrovsk/Zaporizhzhia to paralyze the coordination of the Pokrovsk relief force. (HIGH CONFIDENCE)
- Plan 7-B Interdiction (THREAT LEVEL: CRITICAL): RF Intelligence, Surveillance, and Reconnaissance (ISR) and Spetsnaz (SpN) elements are likely cuing KAB and artillery strikes on the 7-B MOD movement corridor. "Anticipation of success" chatter in RF channels (241452Z) suggests they have acquired the convoy's location. (HIGH CONFIDENCE)
- Cognitive Paralysis (THREAT LEVEL: HIGH): The convergence of the Trump-Xi phone call (241456Z) and RF endorsement of the peace framework creates a "pause signal" for the National Command Authority (NCA), risking a delay in authorizing defensive fire measures. (MEDIUM-HIGH CONFIDENCE)
4. OPERATIONAL DEVELOPMENTS
- Pokrovsk Axis: RF 40th/155th Separate Marine Brigades (OMBR) continue exploitation. The operational center has shifted to the M-30/T-05-15 Ground Line of Communication (GLOC), where interdiction prevents UAF withdrawal or reinforcement.
- Zaporizhzhia Front: Confirmed KAB strikes (241451Z, 241453Z) are actively degrading logistics nodes. Dempster-Shafer analysis (Belief 0.26) supports ongoing RF troop advances in this sector, reinforcing the assessment that this is a fixation operation.
- Northern/Central Sectors: RF is conducting low-cost drone probes against Kharkiv and Poltava. These are decoy operations designed to force UAF to expend Short-Range Air Defense (SHORAD) and Patriot missiles prior to the ballistic launch.
- SAR Activity: Significant activity detected at 583rd Guards AA Regiment (Score 13.28) and 1st AA Regiment (Score 8.19), indicating a massive force protection screen is being established to protect RF launch assets from UAF counter-battery fire.
5. INTELLIGENCE GAPS
- PRIORITY 1 (CRITICAL): Status of Plan 7-B MOD. Immediate verification of location, combat effectiveness, and attrition of the relief column is required.
- PRIORITY 2 (TARGETING): Ballistic Payload Composition. Confirmation of whether the 2652nd GRAU arsenal has loaded Iskander-M (quasi-ballistic) or KN-23 (North Korean ballistic) missiles to optimize interception algorithms.
- PRIORITY 3 (BDA): Zaporizhzhia Damage Assessment. Immediate BDA of the 1451Z KAB strikes to determine if southern supply lines to Pokrovsk remain viable.
6. PREDICTIVE ANALYSIS (NEXT 12 HOURS)
- MLCOA (AD Saturation & Convoy Strike): (HIGH CONFIDENCE) Within the next 3-6 hours, RF will intensify KAB strikes on the Plan 7-B MOD corridor to halt the relief force. Simultaneously, a wave of 100+ Shahed drones will saturate UAF airspace. The main ballistic strike (Iskander/KN-23) will launch between 2200Z and 2400Z, targeting regional C2 hubs.
- MDCOA (Operational Collapse): (MEDIUM-HIGH CONFIDENCE) RF successfully interdicts Plan 7-B MOD en route using KABs. The NCA, paralyzed by the "Peace Plan" IO, delays authorizing counter-battery fire. The subsequent ballistic strike destroys the primary J-FIRE (Joint Fires) center, leaving UAF forces at Rodynske encircled and without command guidance.
7. RECOMMENDATIONS
- Force Protection (IMMEDIATE - J3): EXECUTE "NO COMM" PROTOCOLS FOR 7-B MOD. If communications are jammed, the relief force must assume the route is compromised. Authorize immediate dispersion into non-contiguous cells and usage of tactical Electronic Warfare (EW) (Bukovel-AD) to suppress RF ISR drones cuing KABs.
- Air Defense Rules of Engagement (CRITICAL - Air Force): WEAPONS HOLD for Patriot/SAMP-T systems against all drone targets. These assets must be strictly reserved for the confirmed NLT 240000Z ballistic window. Use mobile fire groups (Gepard/VAMPIRE) for Shahed drones.
- Counter-IO (URGENT - STRATCOM): Preemptively announce that the "RF endorsement" of the peace plan is a stalling tactic to cover the ballistic deployment. Explicitly link the diplomatic maneuver to the imminent strike to immunize Western partners.
- C2 Redundancy (J6): Activate subterranean/hardened backup C2 nodes in Dnipropetrovsk immediately. Assume primary nodes are targeted for destruction within 8 hours.
//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 23 Nov 2025, 15: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
3 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 |
|---|---|---|---|
| Rodynske | UKRAINE | 48.3507226, 37.2097768 | |
| Pokrovsk Axis | UKRAINE | 48.282193, 37.1847804 | |
| Zaporizhzhia Sector | UKRAINE | 47.83928419999999, 35.13870970000001 | |
| AB Monchegorsk | RUSSIA | 67.943134, 32.8919562 | |
| Dnipropetrovsk C2 Node | UKRAINE | 48.464717, 35.046183 | |
| M-30/T-05-15 GLOC | UKRAINE | 48.015883, 37.80285 | |
| Hostile AA Protection Screen (583rd/1st AA Regiments) | RUSSIA/OCCUPIED TERRITORY | 61.52401, 105.318756 | |
| Kharkiv | UKRAINE | 50.00201269999999, 36.3073994 | |
| Poltava | UKRAINE | 49.58826699999999, 34.551417 | |
| J-FIRE (Joint Fires) Center | UKRAINE | 47.8786956, 35.0700705 |
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.
