Chapter 13| Sable’s Theory

Chapter 13: Chapter 13| Sable’s Theory

The afternoon session started differently from the morning one.

Damian was in the cleared land behind the farmhouse running ignition drills when Sable came out with her tablet and a folding chair and set the chair down at the edge of the cleared land with the deliberate placement of someone who had decided they were staying for a while. She didn’t interrupt. She watched him work through two full sequences. Ignition, hold, release, reset and then she opened her tablet and started making notes without saying anything.

He finished the sequence and looked at her.

"Keep going," she said, without looking up. "I’m reading the output pattern."

He kept going.

[Flux: 49%]

She watched him for twenty minutes before she said anything useful, and when she did it wasn’t encouragement and it wasn’t criticism. It was data.

"You’re leading with your dominant hand every time," she said. "Left hand activates point three seconds after the right regardless of which target you’re facing. In a real engagement that’s a pattern someone with field experience reads in the first exchange and exploits in the second." She made a note. "Alternate the lead. Force yourself to initiate from the non-dominant side until the gap closes."

He switched.

It felt wrong immediately. The activation sluggish, the output slightly off, the whole sequence carrying the specific awkwardness of a body doing something it hadn’t been told to do enough times yet. He ran it anyway. Three sequences, four, the wrongness fading incrementally with each repetition the way wrongness always faded when you pushed through it long enough.

"Better," Sable said. "The output is weaker from the left but the pattern is gone. Weaker and unpredictable beats stronger and readable every time at your current level."

"At my current level," he said.

"At any level," she said. "Predictability is the thing that gets people killed more consistently than power deficit. Nexarion’s engagement records are full of high-output Subjects who lost to lower-class operatives because they fought the same way every time." She scrolled through something on her tablet. "There are fourteen documented cases in the archive where a Pyros-class Subject was taken down by an operative with a lower Flux ceiling. In eleven of those fourteen cases the post-engagement report identified pattern recognition as the decisive factor. The operative read the Subject’s sequence and positioned accordingly before the Subject realized they’d been read."

Damian ran another sequence from the left. Slightly less awkward. Marginally.

"What were the other three?" he said.

"Flux exhaustion," she said. "Two of them burned through their reserves in the opening exchange trying to end it fast and had nothing left when the operative extended the engagement deliberately." She looked up from the tablet. "Which is the second thing. Your instinct in a fight is to resolve it quickly. High output, fast finish, move on. That instinct is correct when it works and catastrophic when it doesn’t. An opponent who knows your dissipation rate can beat you by surviving your opening."

He stopped.

Looked at her.

"They just have to last long enough," he said. It’s basically a game of endurance.

"Past your comfortable operating window," she said. "Which at your current dissipation rate and without a recent refuel is somewhere between four and six minutes of active engagement. After that your output starts degrading and the pattern of degradation is visible to anyone who knows what to look for." She set the tablet on her knee.

[Flux: 46%]

The number had dropped three more percent while they were talking. Passive dissipation, steady and indifferent, the constant background drain that had defined his entire existence as Subject 07 and showed no interest in accommodating his current situation.

"So I need to end it fast," he said, "but I can’t rely on ending it fast."

"You need to end it fast," she said, "while appearing not to be trying to end it fast. Force the engagement onto your timeline without letting the opponent know you’re on one." She stood up from the folding chair and walked to the edge of the cleared land, looking at the target markers on the tree line. "There’s a concept in Nexarion’s combat documentation they call Flux Bluffing. It’s not named well but the principle is sound. A Subject who controls what their opponent knows about their Flux state controls the engagement timeline. You make them think you have more than you do and they extend. You make them think you have less and they close. Either way you’re setting the pace."

He thought about that for a moment.

It was the kind of thinking he recognized from the facility. Not the combat application, but the underlying logic. Control what the other person knows. Manage information before you manage force. He’d been doing a version of it for six years without calling it anything.

The system apparently had a name for it now.

Ding!

[Skill note: Ember Shell — secondary application identified. Sustained deployment during low Flux states masks degradation signature. Opponent threat assessment accuracy reduced by estimated 60% while active.]

He read it and looked at Sable.

"The system just flagged something," he said. "Secondary application for Ember Shell. It says sustained deployment during low Flux masks the degradation signature. Reduces opponent threat assessment accuracy by sixty percent while active."

Sable was quiet for a moment, processing that with the expression she wore when new data landed in a framework she was already building.

"That’s consistent with what the heat signature theory predicted," she said. "If the barrier suppresses the external trace it suppresses the most readable indicator of your internal state simultaneously." She made a note on her tablet. "The system is confirming the principle rather than introducing it. Which means the underlying logic is sound." She picked up her folding chair. "Keep drilling. Understanding why something works is half of making it work consistently."

She went back inside.

He stood in the cleared land for a moment and looked at the target markers and thought about information management and Flux Bluffing and the fourteen Pyros-class Subjects in the archive who had been taken down by operatives with lower ceilings and wondered how many of them had seen it coming before it happened.

He ran another sequence from the left.

Less awkward than the last one.

The evening session was Flux conservation.

Sable ran it from the kitchen table with her archive open and Damian sitting across from her and the farmhouse quiet around them in the specific way it was quiet after dark. The tree line invisible beyond the windows, the cleared land reduced to a suggestion, the world contracted to the space the light covered.

[Flux: 43%]

Conservation drills were not physically demanding. That was the deceptive thing about them. They looked like nothing from the outside, a person sitting still with their hands flat on the table, but the internal work was precise and deliberate and more exhausting in a different way than the physical sessions were. The principle was simple: Flux dissipated constantly, but the rate of dissipation was not entirely fixed. There was a baseline. His experimental baseline, the abnormal rate that had gotten him classified as unstable and then there was everything above the baseline that came from inefficiency. Tension in the pathway. Micro-activations that never completed. The low-level hum of a system that was always slightly more active than it needed to be.

The drill was about finding that inefficiency and removing it.