Daily intelligence

Daily Intelligence Report

Published Intelligence Summary & Geospatial Analysis
Report number
486

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

Machine-generated narrative. Labels inside it are written by the model. How to read these labels

SUBJECT: DAILY INTELLIGENCE SUMMARY – 2025-11-27 15:30:00Z

1. EXECUTIVE SUMMARY

(CRITICAL) IMMINENT SOUTHERN ASSAULT & ALLIANCE FRACTURE: The operational focus has shifted rapidly to the Zaporizhzhia Axis (Huliaipole), where Russian Federation (RF) forces have initiated final kinetic shaping (KAB saturation/TOS-2) for a major ground assault assessed to commence NLT 2025-11-27 2200Z. Concurrently, the Pokrovsk Axis situation has degraded to Operational Loss, with RF President Putin explicitly claiming total encirclement, weaponizing this tactical reality to issue maximalist diplomatic ultimatums. A critical fissure in the Western alliance has been exposed via leaks regarding a US-proposed peace plan, which RF Information Operations (IO) are aggressively exploiting to isolate Kyiv diplomatically.

2. CHANGES FROM PREVIOUS REPORT

  • Operational Phase (HULIAIPOLE): Escalated from "Threat of Breakthrough" to "Imminent Assault Execution." Confirmation of heavy Guided Aerial Bomb (KAB) strikes and TOS-2 (Thermobaric) deployment indicates the preparatory phase is complete.
  • Pokrovsk Status (ENCIRCLEMENT): Shifted from "Narrow Escape Corridor" to "Presumed Total Encirclement (P1 GAP)." While UAF Intelligence requires final verification, RF leadership's public validation suggests the physical corridor is closed, necessitating a shift from relief to extraction/breakout.
  • Diplomatic Landscape (FRACTURE): A significant negative shift from "Hardlining" to "Alliance Exploitation." The leak of a US peace plan without European consultation has provided RF a vector to drive a wedge between NATO allies, complicating UAF strategic sustainment.
  • Deep Strike Capability (NEW): UAF has executed confirmed deep strikes on Grozny (Chechnya), expanding the asymmetric theater beyond the immediate border regions (Belgorod/Kursk).

3. THREAT ASSESSMENT

  • Huliaipole Ground Assault (THREAT LEVEL: CRITICAL - IMMINENT): RF forces are staging for a mechanized thrust utilizing TOS-2 systems to breach UAF defensive lines west of Huliaipole NLT 2200Z. The interdiction of the Konstiantynivka Ground Line of Communication (GLOC) by RF Spetsnaz prevents rapid reserve redistribution. (HIGH CONFIDENCE)
  • Alliance Cohesion Failure (THREAT LEVEL: HIGH - RISING): The Dempster-Shafer belief mass for "Disagreement on Peace Plan negotiation process" is active (0.0338). RF exploitation of the US-EU rift threatens to delay critical aid decisions or force premature concessions. (HIGH CONFIDENCE)
  • C2/Logistics Interdiction (THREAT LEVEL: HIGH): While the strategic missile threat persists, the immediate threat has shifted to tactical interdiction. UAVs targeting Sloviansk (C2 node) and Spetsnaz on the Konstiantynivka supply route are effectively fixing UAF operational reserves.
  • Aerial Threat Evolution (SAR INDICATORS): SAR analysis of the 1488th Anti-Aircraft Missile Regiment shows a sharp activity spike (Score 13.88 - RISING*). This suggests RF is aggressively repositioning AD assets to counter UAF deep strikes (Grozny) or to cover the Huliaipole offensive concentration.

Legend: SAR Score 0-5 (Low/Baseline), 5-10 (Moderate), 10-25 (High), 25+ (Critical/Surge).

4. OPERATIONAL DEVELOPMENTS

  • Zaporizhzhia Axis: UAF Air Force confirms multiple KAB launches (14:49Z) targeting defensive works. RF 35th Army (Vostok Group) is utilizing UAVs for final targeting.
  • Pokrovsk Sector: RF President Putin claimed "complete encirclement" (14:12Z). UAF Special Operations Forces (SSO) are conducting localized delaying actions near Hryshyne, but the main GLOC is assessed as severed.
  • Northern Sector (Lyman/Sloviansk): UAF 63rd Brigade successfully countered RF "Molniya" drones. However, a new UAV threat vector from the North is tracking toward Sloviansk, threatening the logistics hub supporting the eastern defense.
  • Internal Security: A major corruption investigation in Poltava (5 million UAH scheme) was successfully prosecuted, though RF IO is attempting to spin this ("Mindichgate") as systemic state failure.

5. INTELLIGENCE GAPS

  • PRIORITY 1 (CRITICAL): TOS-2 Positioning. IMINT confirmation of Thermobaric weapon system deployment locations west of Huliaipole is required immediately to direct counter-battery fire.
  • PRIORITY 2 (FORCE STATUS): Pokrovsk Pocket Viability. Confirmation of life/combat effectiveness of units within the claimed Pokrovsk pocket to determine if Fragmented Defense Protocols (FDP) are still an option or if the force is effectively neutralized.
  • PRIORITY 3 (STRATEGIC): European Political Reaction. Assessment of German/French leadership private reactions to the US peace plan leak to inform urgent diplomatic repair efforts.

6. PREDICTIVE ANALYSIS (NEXT 24 HOURS)

  • MLCOA (Southern Breakthrough & Diplomatic Pressure): (HIGH CONFIDENCE) RF executes the Huliaipole assault NLT 2025-11-27 2200Z, achieving a tactical breach of 5-10km. Simultaneously, RF releases visual evidence of POWs/equipment from Pokrovsk (NLT 280600Z) to demoralize UAF forces and reinforce the narrative that "resistance is futile" amidst Western disarray.
  • MDCOA (Operational Collapse & Isolation): (MEDIUM CONFIDENCE) The successful Huliaipole breach links up with the southern exploitation of the Pokrovsk collapse, rolling up the UAF Southern Donbas defensive line. Concurrently, public recriminations between EU and US leaders regarding the peace plan lead to a temporary freeze in logistical aid flow, paralyzing UAF reserve generation.

7. RECOMMENDATIONS

  1. Fire Support (IMMEDIATE - J3/FIRE COMMAND): EXECUTE COUNTER-PREPARATION. All available long-range artillery and precision assets must target suspected RF assembly areas and TOS-2 systems west of Huliaipole NLT 2025-11-27 1800Z to disrupt the assault timetable.
  2. Force Management (CRITICAL - NCA/J3): AUTHORIZE FDP (POKROVSK). Proceed with the assumption that Pokrovsk is encircled. Authorize Fragmented Defense Protocols (FDP) immediately, granting unit commanders authority to execute independent breakout operations toward Myrnograd without waiting for central relief.
  3. Diplomatic Repair (URGENT - MFA/NCA): Leverage PM Shmyhal’s NATO visit (14:41Z) to issue a joint statement with European partners reaffirming unity. Explicitly reject "unilateral peace proposals" to neutralize the RF IO exploitation of the US leak.
  4. Rear Area Security (J3): Deploy Quick Reaction Forces (QRF) and thermal-equipped counter-sniper teams to the Konstiantynivka GLOC to hunt RF Spetsnaz interdiction teams fixing UAF reserves.

//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.

Report 27 Nov 2025, 15:01 UTC
Map revision comparison

Against the previous report from 26 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.

Compare on map
Frontline change measurements are unavailable for this briefing.

Report Visuals

4 visuals
Open full size
Nightwatch daily report #486: Pokrovsk area

Geospatial 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
Geocoded places in report 486
PlaceCountryLatitude, longitudeCopy
HuliaipoleUA47.6607145, 36.2732384
PokrovskUA48.282193, 37.1847804
Konstiantynivka GLOCUA48.52394289999999, 37.7075811
SlovianskUA48.8532, 37.6053
GroznyRU43.31877009999999, 45.68652429999999
MyrnogradUA48.2962118, 37.2700035
PoltavaUA49.58826699999999, 34.551417

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.