Daily Intel: The Huliaipole Breach & A Satellite "Red Alert"
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
Strategic Situation
The war has shifted into a brutal phase of infrastructure targeting. With temperatures locking in at -27°C, the stakes are immediate. Belgorod has lost central heating and hot water following Ukrainian strikes, and the pressure on the Kremlin to retaliate is massive. I expect them to go after Ukraine’s energy grid tonight to coincide with the blizzard warnings.
On the ground, the deep freeze has turned the mud into concrete. That’s dangerous—it means Russian mechanized units can move fast again. We aren't looking at static trench warfare right now; these are fluid encounters, and lines are buckling in the South and East.
The Front
The situation in Zaporizhzhia is genuinely alarming. Russian "Vostok" groups have reportedly breached the Huliaipole fortifications. If that holds, the stability of the entire southern front is compromised. In the Donbas, it’s not much better. Russian sources claim the 5th Guards Motorized Rifle Brigade has cleared Dymytrov (Myrnohrad). Even if fighting is still happening on the outskirts, Pokrovsk’s northern flank is now exposed.
In the north, the cold cuts both ways. Ukrainian "Phoenix" units are tearing up infantry because Russian troops stand out starkly against the snow on thermal cameras. Meanwhile, a massive drone swarm is hitting Sevastopol; Ukraine has already confirmed a kill on a Russian BK-16 transport craft and an RSP-10 radar system.
Satellite Data
I’ve been looking at the radar imagery, and one anomaly demands attention: the 1st Anti-Aircraft Missile Regiment HQ. The activity difference score hit 29.50 today—for context, the average is usually around 5. That level of movement suggests they are frantically reshuffling air defenses, likely to plug gaps or prepare for the new $15 billion NATO aid package.
Conversely, the 260th GRAU Arsenal is dead quiet. That flatline is what worries me. As I mentioned yesterday, when a logistics hub goes silent like this, it usually means the munitions have already been moved to the launch platforms.
Outlook
The next 24 hours look grim. The combination of the blizzard and the "silence" at the rocket depots suggests a coordinated strike is imminent. Russian Spetsnaz are already using thermal drones to hunt evacuation teams—at these temperatures, a human body glows like a flare.
If you are in Kyiv or Kharkiv, the incoming storm will likely be used as cover for a strike on the grid. Keep your devices charged.
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 13 Feb 2026, 18:38 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
9 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 9 places with coordinates
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Belgorod | RU | 50.5997134, 36.5982621 | |
| Huliaipole fortifications | UA | 47.6607145, 36.2732384 | |
| Dymytrov (Myrnohrad) | UA | 48.2962118, 37.2700035 | |
| Pokrovsk | UA | 48.282193, 37.1847804 | |
| Sevastopol | UA | 44.61665, 33.525367 | |
| 1st Anti-Aircraft Missile Regiment HQ | RU | 45.3453029, 34.4997274 | |
| 260th GRAU Arsenal | RU | 0, 0 | |
| Kyiv | UA | 50.4503596, 30.5245025 | |
| Kharkiv | UA | 50.00201269999999, 36.3073994 |
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.
