Daily intelligence

Intel Update: "Negotiation by Fire" & The Breach at Staritsa

Published Intelligence Summary & Geospatial Analysis
Report number
544

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

Strategic Context

The trilateral talks in Abu Dhabi wrapped up with the usual vague statements about "parameters for ending the war." I wouldn't put much stock in that diplomatic language just yet. If you look at the map, Moscow is executing a strategy of "negotiation by fire." They are smashing the energy grid and pushing for maximum territory before anyone can draw a freeze line.

While the delegates talk, the north is bleeding. The loss of a key village and the warning of a "difficult two weeks" for the power grid suggest the Kremlin is trying to force concessions through exhaustion.

The Ground Reality

Kharkiv Sector: The situation here has gotten ugly. We're confident that Staritsa has fallen to the Russian "Sever" group. This isn't just a dot on a map; it creates a tactical bulge that threatens the supply lines north of Kharkiv city. It looks like UAF forces are falling back to secondary lines to keep Vovchansk from getting encircled.

Donbas Sector: It's just brute force here. The Russian "Yug" group is hammering Kostiantynivka with FAB-3000 glide bombs. If you haven't seen the craters these things leave, they crack bunkers like eggshells. In Novopavlivka, we saw a shift back to heavy armor—a mechanized daylight assault rather than the infantry waves we've seen recently.

Kyiv & The Rear: Water is back on the Left Bank, but the outlook is grim. Energy experts are bracing for a critical two-week window for the grid. As I write this, Shahed drones are already moving through the Borodyanka district.

What the Satellites See

The radar data is what actually worries me. We track logistics by "activity scores," and the Missile Arsenal (59.97, 29.31) just flatlined to 0.00.

In military logistics, silence is usually bad news. It means the depot is empty because the munitions have been loaded onto trains and trucks. Combined with a drop in activity at Voronezh Malshevo airbase, this suggests the reload cycle is done. They aren't packing up; they are staging for a major strike wave, likely within 48 hours.

Tech and Losses

  • Robotic Warfare: The Russians are deploying "Kurier" robotic platforms equipped with mortars. There is something distinctly unsettling about watching automated systems handle indirect fire support.
  • Armor: The Ukrainian "Lazari" unit in Lyman claims to have destroyed 14 Russian armored vehicles.
  • Unconfirmed: There are rumors of a lost Ukrainian AS-90 "Braveheart" howitzer near Rayske, but I've only seen that from a single Russian source, so treat it with skepticism.

The Bottom Line

Ignore the "constructive" rhetoric coming out of the UAE. The logistics tell the real story: empty arsenals and a captured village mean Russia intends to punctuate these talks with violence. Expect a significant missile or drone wave tonight to test exactly how much fight is left in Kyiv's grid.

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 24 Jan 2026, 15:02 UTC
Map revision comparison

Against the previous report from 23 Jan 2026, 15:03 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 #544: Lyman Area of O... area

Geospatial Analysis

12 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 12 places with coordinates
Geocoded places in report 544
PlaceCountryLatitude, longitudeCopy
StaritsaUA50.244348, 36.7862764
KharkivUA50.00201269999999, 36.3073994
VovchanskUA50.284234, 36.9329429
KostiantynivkaUA48.52394289999999, 37.7075811
NovopavlivkaUA47.558712, 37.4402512
KyivUA50.4503596, 30.5245025
Borodyanka DistrictUA50.64450309999999, 29.9146299
Missile Arsenal (59.97, 29.31)UA50.0529506, 30.7667133
Voronezh Malshevo airbaseRU51.6237435, 39.1650677
Lyman Area of OperationsUA48.9897585, 37.8049964
RayskeUA0, 0
Kyiv Left Bank Water SystemUA50.0529506, 30.7667133

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.