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 – 181900Z NOV 25
1. EXECUTIVE SUMMARY
(HIGH CONFIDENCE) CRITICAL NEW DEVELOPMENT: The Russian Federation (RF) has committed the 40th Separate Marine Brigade (OMBR) to the Pokrovsk axis, reinforcing the 155th OMBR. This major conventional escalation is synchronized with an imminent (0-8 hours) threat of Spetsnaz (SpN) interdiction against the sole remaining road supply line (GLOC) at Kostiantynivka. While general missile arsenal activity remains stable/falling, new SAR data indicates RISING activity at Air Bases Monchegorsk and Pskov, suggesting a potential divergence in threat vectors or localized reconstitution not previously tracked.
2. CHANGES FROM PREVIOUS REPORT
- Ground Force Disposition (SIGNIFICANT CHANGE): Unlike the previous reporting period which focused on the aftermath of the air campaign, the primary shift is now on the ground. The introduction of the 40th OMBR (Volodymyrivka–Sofiivka sector) indicates RF intent to transition from fixing operations to a breakthrough attempt, exploiting the logistical fragility caused by the rail severance.
- SpN Threat Timeline (STATUS CHANGE: PEAK WINDOW → IMMINENT): The threat of rear-area interdiction has moved from a general "peak window" to a specific, tactical timeline of 0-8 hours. Intelligence indicates SpN elements are positioned to strike.
- Strategic Strike Indicators (STATUS CHANGE: STABLE → MIXED): Previous assessment of "stable/falling" arsenal activity holds for GRAU sites (e.g., '2652th' showing 0.00 score/falling), BUT SAR analysis now detects a RISING trend at AB Monchegorsk (Score 8.49) and AB Pskov (Score 12.96). This contradicts the assessment of a total pause in aerial threat generation.
- IO/Diplomatic Context (NEW): A new Information Operation (IO) vector has emerged involving alleged sabotage in Poland. RF is amplifying these claims to potentially slow cross-border logistics, creating a "strategic delay" to compound the tactical logistics crisis.
3. THREAT ASSESSMENT
- GLOC Interdiction (THREAT LEVEL: CRITICAL - IMMEDIATE): The Kostiantynivka–Pokrovsk road corridor is the operational center of gravity. With the rail line confirmed severed, any road closure >4 hours due to SpN ambush or IEDs creates immediate ammunition starvation at the front. (HIGH CONFIDENCE)
- Ground Breakthrough (THREAT LEVEL: HIGH - RISING): The combination of the 155th and newly committed 40th OMBR creates a localized force superiority capable of overwhelming UAF defenders if resupply is interdicted. (HIGH CONFIDENCE)
- Aerial Strike (THREAT LEVEL: LOW-MEDIUM): While a mass missile strike remains unlikely in the next 24 hours, the rising activity at northern air bases (Monchegorsk/Pskov) suggests a potential buildup for future operations or smaller, targeted sorties. (MEDIUM CONFIDENCE)
4. OPERATIONAL DEVELOPMENTS
- Logistics Crisis: The J4 situation is critical. UAF is fully dependent on road convoys. The lack of a technical BDA (Battle Damage Assessment) for the Kamyan’ske rail hub continues to paralyze long-term contingency planning.
- Northern Sector Defense: UAF successfully repelled 7 assaults in the Kursk and North Slobozhansky directions, confirming RF efforts to fix UAF reserves away from the critical Donbas sector.
- Deep Strike Success: UAF "Shadow Unit" confirmed destruction of RF armor and artillery, maintaining tactical morale despite the logistics squeeze.
- Rear Area Security: Operation IRON CLAW (convoy escorts) is active, but current force density is assessed as insufficient against the estimated SpN infiltration levels.
5. INTELLIGENCE GAPS
- PRIORITY 1 (NEW - HIGH): 40th OMBR Disposition. Precise OOB, specific operational objectives, and integration level with the 155th OMBR. Is this a relief-in-place or a massing of forces?
- PRIORITY 2 (CRITICAL - PERSISTENT): Kamyan’ske Rail BDA/ETR. Still no definitive engineering assessment on the time-to-repair for the rail hub. This gap is becoming operationally negligent.
- PRIORITY 3 (REFINED): Northern Air Base Activity. Determine the specific nature of the "Rising" activity at AB Monchegorsk and Pskov (aircraft staging vs. cargo loading) to distinguish between strike prep and logistics movement.
6. PREDICTIVE ANALYSIS (NEXT 24-48 HOURS)
- MLCOA (Synchronized Strangulation): (HIGH CONFIDENCE) Within 8 hours, RF SpN will execute a complex ambush on a key logistics convoy near Kostiantynivka to halt road traffic. Simultaneously, the 40th and 155th OMBR will launch high-intensity assaults on the Pokrovsk axis, timing the attack to coincide with the expected ammunition dip at the front lines.
- MDCOA (Operational Collapse): (MEDIUM CONFIDENCE) The SpN interdiction successfully closes the road for >18 hours. UAF forward units, lacking resupply, are forced into a disorganized withdrawal. RF mechanized units exploit the retreat, achieving a penetration depth of >5km and compromising secondary defensive lines.
7. RECOMMENDATIONS
- ROE Change to "Hunter-Killer" (IMMEDIATE - J3): Escalate Operation VIPER HUNT. Transition SOF/security elements in the rear area from passive convoy escort to active "Hunter-Killer" operations. Use thermal/UAS assets to preemptively engage detected signatures in the Kostiantynivka corridor. Defensive posture is no longer viable.
- Forward Logistics Caching (IMMEDIATE - J4): Direct the immediate pre-positioning of 36-hour emergency stocks (Fuel/155mm) to hardened caches forward of the vulnerable road choke points. This buffers against the MLCOA of temporary road closure.
- Targeted ISR Redirection (IMMEDIATE - J2): Task SAR and SIGINT assets specifically against AB Monchegorsk and Pskov to characterize the anomalous rising activity.
- Diplomatic/IO Counter-Action (URGENT - J2/STRATCOM): Provide evidence to Polish liaisons to counter the RF "sabotage" narrative and prevent border processing delays.
//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 17 Nov 2025, 13: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
5 visualsGeospatial Analysis
8 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 8 places with coordinates
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Kostiantynivka | Ukraine | 48.52394289999999, 37.7075811 | |
| Pokrovsk axis | Ukraine | 48.282193, 37.1847804 | |
| Volodymyrivka–Sofiivka sector | Ukraine | 47.7364372, 37.3780632 | |
| Kamyan’ske rail hub | Ukraine | 48.516033, 34.6128617 | |
| Air Base Monchegorsk | Russia | 67.943134, 32.8919562 | |
| Air Base Pskov | Russia | 57.8166994, 28.3344734 | |
| Kursk direction | Russia | 51.7482395, 36.1947023 | |
| North Slobozhansky direction | Ukraine | 49.5944382, 36.5290231 |
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.
