Aegis overheld one side route and had to reopen it under protest. Clarion sent one update late because the correction chain took longer than expected. Tessera lost a crate of food to a blocked alley. Oratory approved a temporary flow that confused two new arrivals until Narthex corrected it. Pyxis hid one broken-seat file too well, and Quorovyr had to demand its return before review could name it safely.
The house recorded these failures in the same after-count as the successes.
That was one of the reasons the city could not regain the clean narrative. A system willing to publish its own errors is harder to accuse of hiding the larger truth. Not impossible. Harder.
The most painful mark came from Rhythmos.
Cut hour held, but one relay line was missed by the main room because the holder expected the old route to carry it. The mark arrived valid through a side channel and sat unread until after the window closed.
The line was not counted for that window.
The house logged the miss and repaired the route.
No one enjoyed that. Marvovyr least of all. But the repair proved the same point as the whole war: survival without an honest damage count becomes a victory story, and victory stories rot faster than wet wood when used as structure.
The counter sweep therefore ended without a clean song.
It ended with a repair queue.
Witness board: Counter sweep.
"Threshold restored." "Cut hour held through pressure." "Archive relay maintained." "Barrier line moved back." "Orders narrowed under public scrutiny."
Old engine note: Apollo Guidance Computer.
Under pressure, survival belongs less to grand capacity than to disciplined distinction between what may fail gracefully and what must stay live at any cost.
House gloss.
Counter sweep means hostile systems lose the ability to describe their own operation as mere maintenance. After that, they must retreat a little or reveal themselves fully.
Fragment 8.
The best counterattack against tidy violence is making it show its real floor plan.
Counter-sweep rule.
Do not polish the survival until the damage has been allowed to speak.
Cascade in the side route.
Cascade did not arrive as policy. It arrived as failure repeated too neatly to ignore.
One side hatch jammed. Then the alternate runner path flooded. Then the backup slate moved to a room that lost its lamp. Then the agent who knew the alternate route got redirected by a false notice. Each failure was plausible. Together they formed a falling pattern.
Apollo logic helped name it.
Do not admire the accident chain. Route around it before it becomes your floor.
Oratory drafted a temporary flow while Aegis watched for capture. Gravamen braced the hatch with a cabinet leg. Rhythmos marked which failures touched cut hour and which did not. Pyxis received two records that were too vulnerable to carry through the falling route.
Cascade wanted the house to spend all night proving each failure was not chance.
The house did not need that proof before action could begin.
It only needed the pattern named clearly enough to stop feeding it.