The moment Ethan interfered,
The board accelerated.
Inside Helix Biotech Complex, Sector C-17 was no longer quiet.
Red lights flooded the corridors.
Containment doors sealed.
Security teams rushed in with controlled urgency.
"What triggered ventilation?!" one technician shouted.
"No scheduled purge!" another replied.
Confusion spread.
And the confusion was disruption.
Miles away, Ethan watched through the maintenance feed.
His interference had done exactly what he intended.
It hadn't stopped the rival.
It had forced him to move early.
And early movement under a countdown,
Was a weakness.
His system interface flickered.
>External Operator Activity Spike Detected
Behaviour Pattern: Adjustment / Compensation
Ethan leaned forward slightly.
Good.
The rival was adapting.
Which meant the plan had been affected.
His encrypted channel lit up instantly.
>"You're interfering."
Ethan typed calmly.
>"You're compensating."
Three dots appeared.
Then vanished.
Then appeared again.
For the first time,
The rival was thinking.
Across the city, underground in the Ministry's control center, Director Arvind Rao stared at the Helix live feed.
"Sector C-17 is active," an analyst reported.
"Was that part of the original anomaly cluster?" Rao asked.
"Yes, sir."
"Then we're not observing anymore."
He turned sharply.
"Deploy units."
The room froze for a second.
Then moved.
Orders transmitted.
Unmarked vehicles dispatched.
Surveillance drones rerouted.
For the first time,
The government wasn't watching.
It was entering the game.
Back in his apartment, Ethan saw the shift instantly.
New vehicles appearing on traffic feeds.
Encrypted communication bursts.
Movement patterns.
"Government response initiated," he murmured.
His system confirmed it.
>Institutional Intervention: Active Volatility Multiplier Increased
Everything was accelerating.
Rival adjustment.
Government entry.
System amplification.
Three forces colliding.
Then,
The rival made his move.
Inside Helix, without warning,
The lights went out.
Total blackout.
For half a second, everything stopped.
Then emergency systems struggled to activate,
and failed.
Backup generators didn't respond.
Security panels flickered.
Containment systems destabilized.
Someone had cut deeper this time.
Ethan's eyes sharpened.
"That's not compensation," he whispered.
"That's escalation."
The rival had abandoned precision.
He was forcing the cascade manually.
The encrypted channel lit up again.
>"You delayed my sequence."
Ethan typed:
>"You rushed your correction."
The reply came instantly.
>"I removed the delay."
Ethan's fingers paused.
Removed the delay.
That meant the rival wasn't restoring timing.
He was eliminating dependencies.
Which meant—
The cascade no longer needed perfect alignment.
It just needed enough pressure.
Inside the Helix facility—
Containment seals began failing.
Not explosively.
Gradually.
Systematically.
Sector by sector.
Technicians tried to regain control.
But every override command returned errors.
The system was being overwritten.
At the same time,
Outside the facility,
Government vehicles arrived.
Unmarked.
Silent.
Fast.
Director Rao stepped out of the lead car.
He looked up at the building.
Dark.
Unstable.
Wrong.
"Secure perimeter," he ordered.
"No media. No panic."
But panic was already coming.
Ethan watched everything converge.
His interference had created a new scenario.
It was not a collapse but, a collision.
The rival was forcing instability.
The government was trying to contain it.
And the system,
Was feeding on both.
His interface flashed again.
>Extreme Event Probability: 97%
System Yield Projection: Massive
Ethan exhaled slowly.
If this continued,
The rival might still succeed.
Not through precision.
But through brute destabilization.
Which meant Ethan needed a second move.
He opened the system interface again.
This time,
He didn't hesitate.
>Borrow:15-Second Probability Forecast
Duration: 5 minutes
Cost:
>Trigger secondary instability within 3 hours
He accepted.
The world sharpened again.
Time split into branching outcomes.
Scenario 1:
Rival continues escalation → Government containment fails → Massive citywide instability
Success probability: 61%
Scenario 2:
Government isolates facility → Rival forced into premature event → Partial failure
Probability: 23%
Scenario 3:
External interference alters infrastructure response timing → Cascade collapses
Probability: 16%
Ethan focused on the third branch.
Lowest probability.
But highest control potential.
He analyzed deeper.
What controlled the cascade now?
Not the lab.
Not the compound.
Not even the power grid.
It was the city's emergency response network.
Ambulances. Police. Fire systems.
If those responded too early,
The cascade stabilized.
If they responded too late,
The cascade exploded.
Timing.
Everything was timing.
Ethan moved quickly.
He accessed the municipal dispatch network.
Not to shut it down.
Not to hack it completely.
Just to introduce a delay.
Of only seven minutes.
A small delay.
But enough.
Enough to shift the outcome window.
He executed the command.
Across the city,
Emergency response systems slowed.
Not stopped.
Just… delayed.
Units rerouted slightly.
Dispatch queues altered.
Nothing obvious.
Nothing traceable.
But enough to affect timing.
Inside Helix,
Containment failure reached critical threshold.
A sealed chamber cracked open.
Alarms screamed.
But response teams,
Were not arriving as fast as expected.
Outside, Rao noticed immediately.
"Why is response time lagging?" he snapped.
"No system error detected," an analyst replied.
That made it worse.
No error meant manipulation.
Rao's eyes hardened.
"We're not dealing with amateurs."
Ethan's interface updated.
>Scenario Shift Detected
Cascade Stability: Fluctuating
The rival's success probability was dropping.
Slowly.
But not enough.
The encrypted channel lit up violently.
>"You're still interfering."
Ethan typed:
>"You're losing control."
Three seconds passed.
Then,
>"Control is irrelevant."
Ethan froze.
That line changed everything.
If control was irrelevant,
Then the rival wasn't trying to stabilize the cascade anymore.
He was willing to let it break,
As long as it created enough instability to repay the debt.
Ethan whispered quietly:
"You're gambling."
For the first time,
The rival wasn't playing a strategy.
He was playing a risk game.
High chaos.
High reward.
High chance of failure.
The timer flashed again.
>External Operator Repayment Timer:
15:03:11
Fifteen hours left.
And the cascade was already unstable.
Ethan looked back at the skyline.
Emergency lights.
Sirens.
Darkness spreading through the industrial zone.
The system pulsed faintly on his screen.
Watching.
Calculating.
Feeding.
He wrote one final line in his notebook:
When a strategist becomes a gambler
he stops controlling the outcome.
Then he closed it.
Because now,
The game had changed again.
The rival wasn't trying to win cleanly.
He was trying to win at any cost.
And that made him far more dangerous.
End of Chapter 8