The event type is a fixture, not a result
An ihub defence is the machinery of sovereignty being contested: the infrastructure hub is the structure that anchors a system, and putting it under campaign pressure is how a challenge gets a timer rather than a headline. What this record supplies is the label - three systems, three ihub defence events - plus the pointed absence of any notable hulls. It supplies no attendance, no losses, no outcome. Three timers on the board confirm three obligations exist in Deklein. They confirm nothing about what has been done about them, and nothing here should be read as a battle someone watched.
A wider front the record cannot explain
The two snapshots sit at 10 November 23:38 and 17 November 21:05, roughly 165 hours apart: one system in the first frame, three in the second. The record establishes that the contested footprint widened from X-Z4DA alone to X-Z4DA, 3OAT-Q and N-TFXK. It does not explain why the additional systems appeared - whether pressure spread, whether new campaigns were opened, or what happened in the interval. One detail is on the record: the three campaigns carry distinct identifiers, 112641, 112643 and 112647, which reads as three parallel contests rather than a single contest relabelled. That reading is an inference from the IDs, not a witnessed sequence of events.
One front, two momentum labels
The regional summary calls the campaign's momentum defensive. The leading front - same defender, same three systems, same 165 hours of age - calls it offensive. Both describe present position rather than anything seen on a grid, so neither is a report of a fight. A 60-40 defender's lead can be described as a hold absorbing pressure or as a hold beginning to press back, and the metadata has settled on both at once. The honest reading is that the labels disagree and the underlying numbers do not: whatever is happening in 3OAT-Q, N-TFXK and X-Z4DA has not yet resolved into either a comfortable defence or a defender's counter-push.
Forty out of a hundred, twice
Attacker pressure averages 40, the defender's 60, and recorded drift across the two observations is zero. The trend summary's own phrase is a grinding stalemate rather than a breakthrough, and it is hard to improve on: nearly a week of tracked time has moved the needle by nothing measurable. What the widening changes is the defender's workload. Three simultaneous ihub defence obligations consume attention in a way a single timer does not, and attention is not a line the scoreboard tracks. A twenty-point cushion spread across three systems is a different object from a twenty-point cushion over one.
What the record declines to say
No recent sovereignty changes are listed. Systems lost and systems gained both read zero, and no hottest system is flagged - so the three systems remain contested rather than captured, and the ihub events remain entries on a schedule rather than resolved contests. The campaign is rated moderate in intensity, is a constellation campaign, has three active campaigns all about 165 hours old, and has produced a wider footprint with an identical score. The unresolved pressure is structural: three timers across 3OAT-Q, N-TFXK and X-Z4DA, a defender holding the same lead it held when only one of those systems was in play, and no mechanism in the evidence by which that arrangement settles itself.