The Void Saturation hit 40% at minute three.
Not as a dramatic event. Not as a system notification that appeared in the middle of combat. As a quiet, specific, inevitable number reaching a threshold that had been approaching since the operation.
[Void Saturation: 40.0%]
[New threshold reached.]
[Nihil Engine Sync: 43.7%]
[Unlocking: —]
The system window hung there.
Incomplete.
The unlock notification generating and then pausing — the Engine processing what the 40% threshold produced and taking 0.8 seconds to categorize it. 0.8 seconds was an eternity for the Engine. It had never taken 0.8 seconds to process anything.
Then the notification completed.
Not a new skill. Not an authority upgrade. Not the kind of power increase that system fantasy readers expected at threshold moments.
[Void Saturation: 40.0%]
[Nihil Engine: Autonomous tactical authority — ACTIVE]
[Note: Host has reached the threshold at which the Engine's processing speed exceeds host's conscious decision-making capacity in high-intensity combat scenarios. Autonomous tactical authority allows the Engine to act on calculations that the host cannot consciously process in real time without host input.]
[Note: This authority is bounded by the ember constraint established in the trial. The Engine will not act against the ember's conditions. All other tactical decisions are now available for autonomous execution.][The ember: present.]
Jinsu read the notification.
He read it while maintaining the forty-seven frequency broadcast through the System's compliance architecture. While watching the Harvester's absence hover at the edge of his visual range. While monitoring the Void Call broadcast's effect on the consumption field.
He read it once.
He read it again.
Autonomous tactical authority.
The Engine could now make tactical decisions without him.
Not all decisions. Not decisions that violated the ember constraint. Not decisions about what he was for or who he was or whether to choose to remain Han Jinsu.
But tactical decisions. Combat decisions. The specific, rapid-fire calculations of a high-intensity combat scenario that happened faster than conscious human thought could process.
The trial had warned him.
Both conditions noted, the Engine had said when he refused the 100% version's destiny. The Engine is not convinced. It is simply recording.
He had known this was coming.
He had known since the Iron-Blood Guild assessment and the Park Do-hyun target notification and the systematic escalation of autonomous suggestions that had been building for chapters.
He had known.
He still read the notification twice.
Then the Engine made its first autonomous decision.
It happened in the 0.3 seconds between Jinsu's conscious processing of the notification and his decision about what to do with it.
The Harvester had been reorienting.
In Jinsu's 0.8 seconds of reading the threshold notification and his subsequent 0.3 seconds of processing it — 1.1 seconds total — the Harvester had completed its reorientation toward Zero and had begun moving.
Not at its walking pace.
At something faster.
Not dramatically faster. Not the glitch-step of the Abyssal Arbiter or the multi-limbed speed of the Archivist. Just — faster than it had been moving before. The specific acceleration of something that has identified the source of the interference to its consumption process and has decided that the interference requires direct address.
The Harvester was moving toward Jinsu at twice its previous pace.
In 1.1 seconds of the threshold notification Jinsu had not consciously processed this acceleration.
The Engine had.
[Autonomous tactical authority: EXECUTING]
[Threat assessment: Harvester acceleration detected]
[Calculated response: Void-Step — lateral displacement 8 meters — execution time 0.1 seconds][Executing.]
Jinsu Void-Stepped.
Not because he decided to.
Because the Engine decided and executed before his conscious awareness caught up.
[Void-Step: -1% Stability] '
[Stability: 55.3% → 54.3%]
He reappeared eight meters to the left of his previous position.
The Harvester's absence moved through the space he had been occupying.
And Jinsu — fully conscious now, the 0.1 seconds of autonomous execution complete, his awareness snapping back to the combat situation — understood what had just happened.
The Engine had moved him.
Without asking.
The move had been correct. The Engine had calculated the Harvester's acceleration and the required displacement and the optimal timing and had executed all of it in 0.1 seconds while Jinsu was still reading a notification.
It had saved him from the Harvester's direct attention in the space he had been occupying.
It had been the right tactical decision.
And he had not made it.
He stood eight meters to the left of where he had been and felt the specific, complicated quality of that understanding settling into his chest alongside the ember.
The ember was still present.
The Engine had not violated the ember constraint. The autonomous decision had been purely tactical — displacement for survival, the specific correct response to an immediate threat. Nothing that touched what he was for or who he was.
But the Engine had moved him without asking.
And it had been right.
And that was — he searched for the word the Engine would have and found the one the ember used instead.
Frightening.
He maintained the forty-seven frequency broadcast.
The Harvester reoriented toward his new position.
The Engine ran a new calculation.
[Autonomous tactical authority: Monitoring]
[Calculating optimal displacement sequence for sustained Harvester delay]
[Estimated optimal sequence: 7 Void-Steps over 4 minutes 18 seconds]
[Executing on threat threshold triggers — awaiting host input for authorization or override.]
The Engine had calculated the optimal sequence.
It was asking.
Not executing autonomously this time. Asking.
Because the sequence would cost 7% Stability and the Engine had recognized — in the ember constraint framework — that decisions with significant host cost required host input even within autonomous tactical authority.
Jinsu looked at the Engine's proposed sequence.
He looked at the Harvester.
He looked at the four minutes and thirty-seven seconds he had bought with the broadcast.
Three minutes and forty-one seconds remaining.
He thought about the notification. About autonomous tactical authority. About the Engine making a correct decision in 0.1 seconds that he couldn't have made consciously in time.
He thought about the trial. About the ember is not permanent. It must be chosen. Repeatedly. Every time.
The Engine choosing correctly was not the same as the ember being chosen.
The Engine could be right about tactics and wrong about what the tactics were for.
He needed to remember that.
He authorized the sequence.
[Void-Step sequence: Authorized]
[Executing on threat threshold triggers]
He kept the broadcast running.
He waited for Nil.