## Chapter 9: The Variable That Wasn't Fixed
I woke at 5:47 AM.
The alarm was set for 6. My brain had decided thirteen minutes of extra sleep wasn't worth the ROI and woke me anyway.
Thermal check.
Two fingers. Three seconds.
Six point two.
Lower than last night. The chip had continued cooling while I slept. Six point two was below threshold — technically safe, technically a green light.
I stared at the ceiling and thought about twenty-three percent per hour.
That figure had a shape to it now. Before Inspector Ao, the thermal risk had been abstract — a warning label, a thing I noted and filed. Now it was a number with a rate attached. Every hour above seven: twenty-three percent chance of cascade. Not cumulative in a simple way — the risk reset somewhat when the chip cooled, but the microfilament stress was permanent. Each overclock event left microscopic damage.
I had been above seven for portions of yesterday's session.
I did not know how many hours total.
Beta would know.
"Beta."
"Yes."
"Accumulated time above thermal threshold seven since installation."
A pause.
"Across all sessions: approximately four hours and seventeen minutes above threshold seven. Peak sustained: the PvP engagement and the Valdris fight, each approximately twenty-five minutes."
Four hours at twenty-three percent per hour was not how cascade probability worked — it wasn't simply additive. But even at a generous interpretation, I had been rolling that die repeatedly.
So far it had come up in my favour.
I got up and made rice.
---
### The Variable
The six-party awareness list was still open on my phone from last night.
I looked at it while the rice cooked.
Inspector Ao: wanted compliance. Offered removal. Could not be negotiated with — the terms were the terms.
Dev_Mitsuki: had official grounds. Could suspend the account today if they chose. Had not done so yet. That gap between *could* and *had not* was interesting.
TechDealer: nervous. Monitoring. Possibly knew more about the chip's situation than he'd said. A resource, if I could work out what he was afraid of.
Vance: protection-or-report. A door that opened inward only — walking through it meant being IronVeil's.
Unknown Process: 21% and waiting. I had stopped trying to predict it. I noted it. I moved on.
KaelVorn.
KaelVorn had offered to learn from me and had not reported me when he could have. He was Level 34 with premium hardware and sixty-three Veilmire clears and he had *asked* rather than threatened. That was either principle or strategy, and either way it created a gap.
The gap was: he wanted the routing.
What I wanted was more complicated.
I wanted the account review to go away. KaelVorn couldn't do that directly. But KaelVorn was IronVeil, and IronVeil was one of the top guilds on the server, and one of the things large guilds did — quietly, in practice — was extend political cover to players they were interested in. A guild that flagged an account for review would be listened to. A guild that vouched for an account would also be listened to.
Not a guarantee. Not even close.
But a variable.
I ate my rice.
Then I opened KaelVorn's public comm crystal frequency and sent a message.
*Your offer is still open?*
The response came in four minutes. He'd been awake.
*Yes.*
*Then meet me at the Veilmire entrance at noon.*
A longer pause. Seven minutes.
*Conditions?*
I thought about that.
*I show you the routing. You answer three questions honestly. No recording, no screenshots, no guild report.*
Another pause.
*Define "honestly."*
*To the best of your knowledge, without omission.*
The longest pause yet. Fourteen minutes.
Then: *Agreed. Noon.*
I set down my phone.
"Beta," I said.
"Yes."
"I'm going to make a deal with KaelVorn."
"I heard."
"Assessment."
"He agreed to your terms with minimal negotiation, which suggests either he genuinely wants the information or he's comfortable lying to you. His track record in public guild interactions suggests a preference for direct dealing. The omission clause you added was smart."
"What's my exposure?"
"If he breaks the agreement: guild report plus player report. Account suspension within twenty-four hours. Dev_Mitsuki review accelerated."
"And if he keeps it?"
"Unknown upside. Possibly nothing. Possibly significant."
"That's a reasonable risk profile."
"It is," Beta said. "Which is unusual for you. Your risk tolerance has been rising."
I hadn't thought about that.
"Chip," I said.
"Pardon?"
"The chip is raising my risk tolerance. The thermal damage. Small cognitive effects."
A long pause.
"That is... possible," Beta said carefully. "Sustained microfilament stress can affect signal propagation in the prefrontal—"
"I know. I'm monitoring it."
"Are you?"
"I'm noting it. That's the same thing."
"It is not the same thing."
"Log it," I said. "Flag it for review."
"Noted," Beta said, in a tone that did not sound reassured.
I logged in.
---
### The Grimoire
I had four hours before noon.
The grimoire was still in my bag.
I'd been avoiding it for two days — noting it, filing it, proceeding. The Unknown Process's domain. Bait or gift. I still didn't know which.
But the account review had changed the calculus. If Mitsuki suspended my account in the next forty-eight hours, I'd lose access to everything in it. Whatever the grimoire did or didn't do, I needed to know before it was potentially locked behind a banned account.
I sat on a bench in Irongate's central plaza — high player density, good asset load, corruption window stable at around 50% — and opened the grimoire.
**[ Valdris' Binding Grimoire ]**
**[ Rarity: ??? ]**
**[ Stats: ??? ]**
This story is posted elsewhere by the author. Help them out by reading the authentic version.
I'd seen this screen a dozen times. It hadn't changed.
I tried equipping it. Error — not equippable, no slot type defined.
I tried using it as a consumable. Error — item type unrecognised.
I tried dropping it. Error — bound to account.
I tried listing it on the marketplace. Error — cannot list items with undefined rarity.
I couldn't use it, equip it, drop it, or sell it.
It sat in my inventory like a very expensive paperweight with a developer's embarrassed note attached.
"Beta. The grimoire. Has the Unknown Process interacted with it since I picked it up?"
"No direct interaction visible. However—" A pause. "The grimoire's item record updates approximately every forty minutes. Small changes to the metadata."
"What kind of changes?"
"The internal tag sequence has been incrementing. When you first picked it up: *bind_state: pending*. Current state: *bind_state: 73%.*"
I stared at the chat window.
"It's binding to me."
"Progressively. At current rate, the binding will complete in approximately two hours and forty minutes."
"What happens when it completes?"
"Unknown. The item's function tag remains undefined. The completion of the binding process may resolve the definition."
The Unknown Process had put a two-stage item in my inventory. First stage: possession. Second stage: binding. Third stage: whatever it actually did.
*Be careful what you pull.*
I looked at the grimoire in my inventory.
I hadn't pulled it. I'd picked up a boss drop. The Unknown Process had made sure it was there to pick up.
The distinction felt important and I couldn't articulate why.
"Continue monitoring," I said.
"I always do," Beta said. Dryly.
---
### The Market
Two hours before noon.
Asset load was good. I ran the marketplace for ninety minutes — corruption window holding at 45–52%, enough to work with.
Finds:
A pair of boots listed as *Traveler's Walkers, worn condition* — hidden tag showing *{movement_type: ghost_step_v2 — deprecated}*. Ghost step was a movement ability that had been removed from the game in patch 1.4. The boots still had the function. Listed at 22 gold. I bought them and equipped them — my movement gained a faint secondary echo, a half-step of lag in my visible position that stacked with the shadow armor's desync.
My effective visual offset was now 0.9 seconds. My actual position and what anyone could see of me had almost a full second of separation.
I tested it by walking through the marketplace.
Players looked slightly past me when they glanced over.
Their eyes tracked the visual ghost.
Not me.
I wrote in the log: *Ghost Step boots — deprecated function. 0.2s additional visual offset. Total: 0.9s. Combat implications: significant. Acquisition cost: 22 gold. Notes: do not test in PvP with KaelVorn today. He will notice.*
A *[SYSTEM]* notification appeared while I was browsing.
I almost scrolled past it.
Then I saw the sender field render underneath, corrupted UI doing its work:
**[ SYSTEM — {PROXY_SENDER: UNKNOWN_PROCESS_0x77} ]**
Another message.
I opened it carefully.
One line this time.
*The grimoire is not for you. It's for what you're carrying.*
I read that four times.
*Not for you.*
*For what you're carrying.*
I was carrying the grimoire.
And the Ring of ???.
And the Dusty Warding Ring.
And two pieces of the unreleased battle mage set.
And the ghost step boots.
And the undefined health potion, empty now — I'd used it on Valdris.
And the incomplete set seed ring from the Veilmire chest.
And a level variable that was NaN.
And an Unknown Process running at 21% privilege escalation.
Which of those was the Unknown Process writing to?
I closed the message.
Logged it: *Message 2. "The grimoire is not for you. It's for what you're carrying." Ambiguous referent. Filed. Watching.*
It was currently 11:43 AM.
I had seventeen minutes to get to the Veilmire entrance.
---
### Noon
KaelVorn was already there.
No scouts. No IronVeil backup positioned at the treeline — I'd checked with wireframe on approach, out of habit. Just him, arms folded, standing exactly where he'd stood two days ago.
Waiting, not ambushing.
I filed that.
"You're early," he said.
"Routing efficiency."
A small muscle moved near his jaw. Not quite a smile. Close.
"Show me," he said.
I showed him.
Not everything. I kept the ghost step boots out of it — too new, too raw an advantage to demonstrate. But the rest: the patrol gap timing, the behavior tree reading strategy for the enrage thresholds, the stationary desync initiation, the ring regen positioning to buy two extra seconds before a kill forced.
I walked him through room three, which had the most complex patrol interaction, in real time.
He watched in silence.
His eyes moved differently from any player I'd watched fight — not tracking the visible combat, tracking the underlying mechanics. Cause and effect, a layer deeper than animation. When I hit from standing still and the triple proc fired, he tilted his head exactly 0.7 centimetres and said nothing.
When I finished he was quiet for fifteen seconds.
"The behavior tree read," he said. "That's not an Aetheria feature."
"No."
"It's hardware."
"Yes."
"Illegal hardware."
"You agreed to no report."
"I know what I agreed to." He looked at the dungeon entrance. "The patrol gap timing I can replicate. The enrage threshold strategy — obvious in hindsight, I should have seen it. The ring regen positioning — I've never thought about HP management that way." A pause. "The desync initiation I cannot replicate without your hardware situation."
"I know."
He turned to look at me directly.
"You cleared the Veilmire two hours faster than my record using mechanics I can't access and some I can. That's honest."
"Yes."
"Three questions," he said.
"Yes."
"First: are you going to be banned?"
I looked at him.
"There's an active account review," I said. "Compliance flag raised by the Ministry. I don't know the timeline."
He absorbed that. No reaction visible.
"Second: the behavior tree advantage. It reads live, in combat?"
"Always on. Passive. I can see decision trees in every enemy's info panel at all times."
"That changes every dungeon in the game."
"Yes."
"Every dungeon you can access."
"With the NaN bypass, most of them."
He was quiet for a moment.
"Third question," he said. Then stopped.
I waited.
"The thing attached to your session," he said. "The Unknown Process. I saw it suppress my scan two days ago. It's not a chip function."
"No."
"What is it?"
"I don't know. Server-side entity. Been watching since the tutorial. Helps me intermittently. Currently running a privilege escalation sequence inside the game's backend."
A very long pause.
"Privilege escalation," he repeated.
"Incrementally. Twenty-one percent as of last night."
KaelVorn looked at the Veilmire entrance for a long moment.
When he looked back, something had shifted in his expression. The calculation-machine quality was still there. But underneath it, something else.
Not fear exactly.
The particular alertness of someone who had just realised the situation they were in was considerably larger than the situation they thought they were in.
"That's not a player exploit," he said.
"No."
"That's a server-level intrusion."
"I know."
"Using your account as the vector."
"I know."
"And you've been—" He stopped. Started again. "You've been farming dungeons."
"I have debt," I said. "Eleven days. ￥85,000."
He stared at me.
For the first time since I'd met him, KaelVorn looked like a person who had run out of the appropriate algorithm for the situation.
"You have a server entity escalating admin privileges through your account," he said slowly, "a government compliance notice, a developer review, and you're worried about ￥85,000 in debt."
"The ￥85,000 has a fixed deadline. The other things are variable."
He looked at me for a long moment.
"You're insane," he said. Without heat. Almost admiringly.
"I'm constrained."
He turned back to the dungeon.
"I'm not going to report you," he said.
"I know."
"I agreed not to."
"I also know you'd have messaged Vance by now if you were going to. You haven't."
He glanced at me sidelong.
"The routing is worth the trade," he said. "For what I can replicate."
"I know that too."
Silence.
Then he said: "The account review. Mitsuki will pull your session logs."
"Yes."
"The Unknown Process interactions will be in those logs."
"Probably."
"That changes what Mitsuki sees. They won't just see illegal hardware. They'll see a server anomaly operating through a player account." He paused. "That's not a ban. That's an investigation."
I hadn't quite assembled it that way.
He was right.
The moment Mitsuki pulled my logs looking for hardware violation evidence, they'd find something considerably stranger. A process attaching itself to a player session. Privilege escalation sequence. Server-side behavior modifications. The auto-adjust on the shadow set bonus. The full behavior tree unlock during the Valdris fight.
That wasn't a player cheating.
That was something happening *in* the game, using a player as a foothold.
Mitsuki would escalate it internally.
My account would stop being a ban case.
It would become an incident case.
"How long does an incident investigation take?" I said.
"I don't know. I've never been an incident."
"Estimate."
"Weeks. Maybe longer. They'd want to preserve the account state for analysis. They might not suspend it at all — suspending it could disrupt whatever the process is doing, and if they don't understand what it's doing yet, they'd want to watch it."
I stood very still.
*They might not suspend it at all.*
The account review that I'd assumed was a countdown to losing everything might instead be a reason for the developers to *preserve* my access.
Because they'd want to study it.
Because I was no longer just a player with illegal hardware.
I was the only active interface with something that was trying to acquire admin access to their server.
"Beta," I said quietly.
"I heard," Beta said.
"Probability assessment."
"KaelVorn's reasoning is sound. Whether the development team acts on it correctly is a different question. Bureaucratic systems often don't."
"But it's possible."
"It's possible."
KaelVorn was still looking at the dungeon.
"You thought about all of this before you messaged me," I said.
"Some of it."
"Why tell me?"
He was quiet for a moment.
"Because you showed me the routing," he said. "And because whatever is running through your account is interesting, and I'd rather it be documented and studied than banned into silence before anyone understands it."
He turned to face me.
"I'm going to tell Vance," he said. "Not a report. A conversation. He'll want to know there's something active in the server architecture. IronVeil has development contacts."
"That adds another party with awareness."
"It adds a party with influence." He said it evenly. "Your choice."
I ran the numbers.
KaelVorn telling Vance: risk of IronVeil leverage increasing. Benefit of IronVeil's development contacts potentially interceding with the review. Net unknown, but probably positive if KaelVorn's read of Vance was accurate.
"Tell him," I said.
KaelVorn nodded. Clean, assessing, the same nod as before. Then he turned toward the dungeon entrance.
"I'm going to run the patrol gap timing in room three," he said. "Alone."
"It won't work without the behavior tree read."
"I know. I want to see how close I can get with approximation."
He walked into the Veilmire without looking back.
I stood outside and watched the entrance for a moment.
Then my inventory notification pinged.
**[ Valdris' Binding Grimoire — bind_state: 100% ]**
**[ Binding complete. ]**
**[ Resolving item definition... ]**
The grimoire's item window flickered.
The ??? fields began to resolve.
One by one.
**[ Valdris' Binding Grimoire ]**
**[ Rarity: Unique — Server Instance: 1 of 1 ]**
**[ Type: Vessel ]**
**[ Function: Contains. ]**
**[ Current contents: See equipped. ]**
I stared at it.
*Vessel.*
*Contains.*
I checked equipped items.
Nothing had changed.
I checked my status panel.
One new line at the bottom. Below the ring passives. Below the shadow step. Below the sync lock marker.
Small. Faint. Half-rendered, like it was running on borrowed display budget.
**[ PASSENGER: 1 ]**
The Unknown Process was not attached to my session.
It was inside the grimoire.
It had been inside the grimoire since I picked it up in the Valdris loot drop.
I had been carrying it for two days.
*The grimoire is not for you. It's for what you're carrying.*
Not the rings. Not the set pieces.
Not anything I'd accumulated.
The message had been about the grimoire itself.
The Unknown Process had been telling me what the grimoire contained.
Itself.
The wind moved through the Veilmire approach.
Behind my ear, the chip held steady at six point four.
I did not move for a long time.
Then I opened the spreadsheet.
*Day 8. Grimoire resolved: Vessel, Unique, 1 of 1. Contains Unknown Process directly. Not session-attached — item-bound. Carrying it = carrying the process.*
*Implications: if account suspended, grimoire stays in inventory. Process stays intact. Suspension does not end this.*
*If I drop the grimoire: process loses vessel. Unknown outcome.*
*If I sell it: process transfers to buyer. Unknown outcome.*
*Bound to account. Cannot drop. Cannot sell. Cannot list.*
*The Unknown Process made itself unlosable.*
I looked at the last line for a long time.
Then I added one more:
*It chose me specifically. Privilege escalation was never about the server.*
*It was about getting inside something I would never let go of.*
The chip pulsed.
Six point four.
Warm.
Patient.
Waiting.
