Two Systems, Two Campaigns, One Front
The record lists two campaign IDs, 112655 and 112656, and two systems, each carrying one ihub defence. At the regional level the union is those same two systems; at the alliance-front level Calculated Disorder is defending both. This is not one system's fight spilling over by implication. It is two separate defences presented as a single area of pressure, which matters because the constellation frame bundles them without turning them into one piece of work.
What an Ihub Defence Actually Costs
An infrastructure hub is not a headline object. It sits beneath indexes and upgrades, the industrial and ratting baseline that decides whether a constellation is worth basing in. Defending one is administrative warfare: entosis windows, timer arithmetic and the recurring problem of convincing pilots to sit on a node at an hour nobody would have picked. That is general context for the stakes, not a description of anything that has happened in these two systems. The record shows two defences open, not fleets, kills or contested nodes.
The Scoreboard Is Not the Map
The lead reads like a comfortable afternoon. In sovereignty terms it is an accounting position: Calculated Disorder is ahead of the attacking side in a contest that has not converted into a transfer. Nothing has moved. No system has left the defender's column, none has entered it, and no sovereignty change appears in the record for O-IOAI or QX-LIJ. The alliance is winning something without having won anything, and the atlas, unimpressed, still shows two systems whose status is being argued over rather than settled.
The Attacker With No Ticker
The attacking side is supplied only as a number: 40 across the two-system front. No alliance, corporation or ticker is attached to it, and the evidence does not break that figure into a separate standing for O-IOAI and QX-LIJ. That asymmetry is a limit of the evidence rather than a riddle to be solved with a guess, and it is worth stating plainly, because pressure without an attributable author reads as mystery when it is really just the shape of what was recorded. The record stops at the front-level figure.
Three Hours, One Snapshot
The single logged observation shows score drift at zero, steady momentum and no hottest system recorded, so the data cannot say which of the two fronts is under more strain. 'Moderate' intensity and 'defensive' momentum describe a present position, not a witnessed action. What is supported is narrow and clear: Calculated Disorder defends two Delve ihubs, leads across the pair, lost and gained nothing, and showed no score drift in the logged snapshot. Against that sits the unresolved pressure: two campaigns, three hours old, still running, and the map refusing to move.