## Chapter 10: All My Problems Have Names Now
Day nine.
Ten days to the debt deadline.
Thermal check: six point one.
I held my fingers there longer than necessary, like I was taking a pulse and waiting for something it wasn't going to tell me.
Six point one was fine. Six point one was three full notches below the cascade threshold. Six point one felt like taunting.
"Beta. Cognitive status."
A pause with a different texture than usual.
"Neural sync at 88.1%. Sync lock holding. No measurable degradation in processing speed relative to baseline. However—"
"However."
"Decision latency on low-stakes choices has increased by approximately 12% over the past three days. This is consistent with mild prefrontal stress from sustained thermal cycling. You are still within functional parameters. You are approaching the edge of them."
"Specific effect?"
"You are taking longer to decide things you would previously have decided instantly. You are also occasionally deciding things you would previously have deliberated longer on."
So I was slower at easy decisions and faster at hard ones.
That tracked.
"Acceptable for now," I said.
"For now," Beta agreed, in the tone it used when it agreed with something it didn't like.
I made rice. I ate it standing up. I logged in.
---
### Vance
He was waiting in Irongate's western district, outside a building with an IronVeil crest above the door — a guild hall, mid-tier, the kind of real estate that cost meaningful gold to maintain.
Vance looked the same as he had in the Ashfall forest two weeks ago. Same armour, same measured posture, same quality of stillness that made him seem like he'd been placed rather than arrived.
"KaelVorn told me," he said, before I could open with anything.
"I know."
He looked at my nameplate.
**[ ??? (Lv.???) ]**
"Still undefined."
"Still undefined."
He studied me for a moment with the particular attention of someone who had been thinking about a problem and was now seeing the primary variable in person.
"Come inside," he said.
The guild hall was functional rather than decorated. A round table. Six chairs. Maps on the walls — dungeon layouts, territory markers, patrol routes annotated in two different handwriting styles. A shelf of communication crystals sorted by frequency.
Vance sat. I sat across from him.
"KaelVorn's read of the situation," Vance said. "Server-side entity, privilege escalation, item-bound, using your account as the vector. That's his interpretation."
"It's mine too."
"And the development team is reviewing your account."
"Formally. As of two days ago."
Vance placed both hands flat on the table.
"IronVeil has a standing relationship with two members of Aetheria's engineering division," he said. "Not management. Not Trust & Safety. Engineers. The people who build the infrastructure the Trust & Safety team reports findings to."
I waited.
"If the development review escalates to an engineering-level investigation — which KaelVorn believes it will, once they see the session logs — those engineers will be involved. I can make sure they receive additional context alongside the raw log data."
"What kind of context?"
"That the anomaly has been actively monitored by a guild with server-infrastructure interests. That the player hosting the anomaly has been cooperative and transparent with parties who became aware of the situation. That unilateral suspension would likely damage whatever data trail the anomaly has been building."
It was exactly what KaelVorn had theorised, packaged into something that could actually be delivered.
"What does IronVeil want in return?" I said.
Vance didn't hesitate.
"Access. If the engineering team investigates the server process and makes findings, we want to be in the room. Not controlling the investigation — observing it. IronVeil has a long-term interest in the integrity of this server's architecture."
"And me specifically?"
"You're the interface. Whatever the process communicates, whatever it does — you see it first. We want to know what you see. Not control it. Not report it. Know it."
I ran the calculus.
Vance offering cover with the engineering team in exchange for a standing information-sharing agreement. Not guild membership. Not reporting obligations. Just — *tell us what you're seeing.*
The risk: IronVeil now had leverage over me proportional to how much they helped. The more Vance did, the more he could reasonably expect in return.
The benefit: if the engineering team received favourable framing alongside the session logs, the account review might shift from *ban case* to *monitored anomaly.* Which was the outcome I needed.
"No exclusivity," I said. "I share what I observe. I don't commit to sharing everything, and I don't commit to sharing only with you."
Vance considered that for three seconds.
"Agreed."
"And if the engineering team suspends my account anyway — your coverage didn't prevent it — the agreement ends. You didn't deliver, I don't owe."
Another three seconds.
"Agreed."
He extended a hand. In-game, a contract handshake prompt appeared — the game's mechanic for informal agreements, logging them to both parties' account histories without legal weight.
I accepted.
**[ Informal Agreement logged: ??? and IronVeil ]**
**[ Terms: information sharing, non-exclusive, contingent on coverage ]**
I looked at the agreement log entry.
My name still showed as ???.
Even in a formal handshake, the system couldn't categorise me correctly.
Vance looked at it too.
"You should have a name," he said. It wasn't a complaint. Just an observation.
"I have a name."
"Not in this system."
"The system has limits," I said.
He almost smiled. Almost.
---
### The Message From Mitsuki
I was back in the marketplace, running a mid-morning arbitrage pass, when the notification came.
Not in-game mail. Not a system message.
A real-world email. To my registered Aetheria account address — the one I'd used when creating the account fourteen months ago, before the chip, before the debt spiral.
Sender: ****
Subject: *Account Review — DEV_REVIEW_0xC4F2*
I stared at it for a long time.
A developer was emailing me directly. Not through the Trust & Safety system. Through their internal address. Which meant this was off-process — personal, not official.
I opened it.
---
*Mr. Kang,*
*My name is Ren Mitsuki. I'm a senior engineer on Aetheria Online's server infrastructure team. You may have seen my name in some backend data that's been surfacing in your client UI.*
*I'll be direct: your account has been flagged for hardware compliance review, and I've been assigned to the engineering assessment. I've reviewed your session logs.*
*I expected to find evidence of a player exploiting a corrupted neural interface for gameplay advantage. That's what the compliance flag suggested.*
*What I found was significantly more interesting.*
*There is a process running in your session that does not originate from your client, your hardware, or any known Aetheria system. It has been present since your first login. It has been modifying server-side parameters in response to your gameplay. And as of forty-eight hours ago, it has completed a binding operation to an item in your inventory.*
*I've been watching this process for nine days. I have not suspended your account because suspending it would likely sever the process from its current vessel, and I don't yet understand what that would do.*
*I'm contacting you directly because you are, to my knowledge, the only person in direct contact with this process. I have questions. I imagine you have questions too.*
You might be reading a pirated copy. Look for the official release to support the author.
*I'm not here to report you. The hardware compliance piece is between you and the Ministry — that's not my division. What I care about is what's running in my server infrastructure.*
*If you're willing to talk, I'd like to understand what you've observed.*
*— Ren Mitsuki*
*Senior Infrastructure Engineer, Aetheria Online*
---
I read it three times.
Then I opened the spreadsheet.
*Day 9. Mitsuki made direct contact. Off-process. Personal email. Not a ban notice — a research inquiry. Has reviewed session logs. Knows about the grimoire binding. Has been watching for nine days. Has NOT suspended account — deliberately.*
*Assessment: Mitsuki is a scientist first. The process interests him more than the compliance violation.*
*Risk: if I respond, I confirm I'm aware of the process and have been interacting with it knowingly. Potential legal exposure if the process turns out to be malicious.*
*If I don't respond: Mitsuki continues watching anyway. No new information for either of us. Clock keeps running.*
I looked at that last line.
The clock was always running.
Ten days. ￥85,000.
I opened a reply.
---
*Mr. Mitsuki,*
*I've seen your name in more places than you probably intended.*
*Yes, I'm willing to talk. Some conditions: this conversation stays between your engineering assessment and me. Not Trust & Safety, not the compliance division, not guild partners. If it expands, I want to know before it does.*
*What I've observed, briefly:*
*The process attached to my session on day one. It sent me two messages. It intervened three times directly — once to mask an IronVeil scan, once to modify a set bonus to stack with my hardware offset, once to give me full enemy behavior data during a boss fight. It bound itself to an item in my inventory two days ago. That item is now listed in my status panel as PASSENGER: 1.*
*I don't know what it is. I don't know what it wants. I know it's been consistently helpful and that it chose me deliberately — my account has characteristics that made it useful as a host.*
*I also know it's at 21% privilege escalation and I don't know what happens at 100%.*
*What do you know?*
*— Leo Kang*
---
I sent it before I could talk myself out of it.
"Beta," I said.
"Yes."
"I just emailed a senior Aetheria developer."
"I know. I was reading."
"Assessment."
"The email confirms your awareness of the process, which creates legal exposure in theory. In practice, Mitsuki's tone suggests he is not interested in pursuing compliance violations — he is interested in the process. You gave him information he didn't have. He will now either trust you as a source or become more cautious. Based on the email's tone, I estimate the former is more likely."
"And if I'm wrong?"
"Then you have made a potentially significant mistake that you cannot undo."
"I know."
"You sent it anyway."
"The clock is running."
Beta was quiet for a moment.
"The risk tolerance," it said.
"I know."
"I'm logging it again."
"Log it," I said.
---
### The New Ceiling
I had two hours before a reply might reasonably arrive.
I spent them productively.
"Beta. Dungeons above the Veilmire."
"Several. The next accessible tier is the Sunken Archives — recommended level 30–40, party size six to eight. Entry fee: 120 gold."
"Expected yield?"
"Forum median: 11,000 gold per clear. High variance — boss loot tables have rare drops worth significantly more."
"Solo survival odds with current loadout?"
A pause.
"Better than my Veilmire estimate was on day six."
"That's not a number."
"Approximately 34%."
Better than a coin flip, worse than comfortable.
"Behavior tree obfuscation level?"
"Unknown. The Sunken Archives is newer content. Obfuscation patterns may differ from the Veilmire. Possibly more, possibly less."
"Entry check — level validation?"
"Same null-check architecture as the Veilmire and Ashvault. NaN will likely pass."
I looked at the dungeon map on my HUD.
The Sunken Archives was three zones northeast. A flooded research facility from Aetheria's lore — pre-game-world academia, the kind of setting that justified both undead enemies and intact bookshelves full of sellable documents.
At 11,000 gold median, one clear was ￥55,000.
Two clears: ￥110,000. Debt deadline met with room to spare.
Two clears at 34% solo survival odds: statistically, I'd expect to clear once and die once.
Dying meant losing a session, not losing the account. Gear was kept on death in this game — only unbanked gold dropped, up to 10% of carried liquid.
My liquid gold: 2,890. I'd lose 289 gold if I died.
Acceptable loss.
"Beta. The ghost step boots. Combat test — I need to know the actual offset in a live encounter before I take them into something at this tier."
"Recommended."
"Veilmire Room One. Standard guardians."
"Thermal is at six point one. A short combat test should keep you well below threshold."
I walked to the Veilmire entrance.
The guardian processed my level.
**[ Defaulting to: PASS ]**
I was getting fond of that message.
---
### Field Test
Room one. Two guardians. Known quantities.
I entered the patrol window exactly as I had a dozen times before — standing still, stationary desync initiation, neck seam target.
But this time I paid attention to something else.
My position.
Where I actually was versus where the guardian's targeting logic tracked me.
With the shadow armor alone, the gap had been 0.7 seconds. Visible-self trailing, actual-self ahead. The guardians had consistently struck where I'd been.
Now, with the ghost step boots adding 0.2 seconds to the offset:
The gap was 0.9 seconds.
In practice, that meant the guardian's first swing — landing at my visible position — arrived at empty air. My actual self was already ninety centimetres forward and half a metre left.
The swing hit nothing.
I turned and looked at the guardian, which was hitting the space I had occupied nearly a full second ago with absolute conviction.
"Beta."
"Yes."
"It's fighting a ghost."
"Effectively, yes. Your visible position is a decoy. Your actual position is outside its attack cone."
"Can I stand still and let it hit the ghost?"
"In theory. The visible position updates continuously — it's not static. If you stop moving entirely, the ghost collapses back to your actual position within approximately 1.5 seconds."
"So I need to keep moving to maintain separation."
"Correct. Think of it as kiting, but the thing you're kiting away from is your own image."
I circled the guardian, moving constantly, letting it chase the trailing echo.
It hit air four times in a row.
On the fifth attempt I stopped moving briefly to test the collapse window.
At 1.3 seconds stationary, the ghost snapped back.
The guardian's swing connected for **-49**.
Good data.
I killed both guardians — burst to pre-enrage, clean finish — without taking another hit. Session duration: six minutes. Thermal: six point three on exit. Well within margin.
I logged it: *Ghost step combat test. 0.9s offset confirmed. Key mechanic: continuous movement required to maintain separation. Collapse at ~1.3s stationary. Primary use: evasion, not burst. Pairs with shadow desync for sustained kiting. Does not help stationary desync initiation — those two mechanics are in opposition.*
That last line mattered. The ghost step and the stationary desync were mutually exclusive during the initiation window. I couldn't be still enough to maximise the desync proc and moving enough to maintain ghost separation at the same time.
Choose one.
Open a fight stationary — proc the desync burst — then move continuously to kite with the ghost offset.
Two phases. Switch between them.
I stood at the dungeon exit and worked out the sequencing.
*Phase 1: stationary initiation. Maximum desync proc rate. 2–3 swings. High burst.*
*Phase 2: continuous movement. Ghost offset active. Evasion mode. Finish with clean hits while target chases echo.*
*Transition trigger: when target is below 50% — before enrage threshold — switch to movement.*
It was the most complete combat model I'd built.
I opened the Sunken Archives on the map.
"Beta. Give me everything you have on the Archives."
"Forum data is limited — it's newer content, fewer clears documented. What I have: flooded environment, some zones requiring movement through shallow water which will affect positioning. Enemy types include Drowned Scholars — undead, Level 32 — and Archival Constructs — mechanical, Level 35. The Dusty Warding Ring's undead affinity will apply to the Scholars but not the Constructs."
"Two enemy types with different resistance profiles."
"Yes. The Constructs are immune to Arcane damage — your dagger's primary proc will be ineffective against them."
I looked at my inventory.
The Cracked Runic Dagger. Arcane proc. Useless against Level 35 mechanical enemies.
"I need a different weapon for the Constructs."
"Correct. Physical damage only. Your base damage without the proc is significantly lower."
"What's in the marketplace for physical pierce, reasonable cost?"
"I cannot browse the marketplace for you. But based on your hidden tag read rate and current player inventory patterns—"
"Never mind. I'll find something."
I left the Veilmire and headed back to Irongate.
---
### The Reply
It came forty minutes later.
---
*Leo,*
*Thank you for responding. Your conditions are reasonable — this stays within the engineering assessment for now.*
*What I know:*
*The process first appeared in our logs on the same day as your account's initial login. It doesn't have an origin point in our system — it didn't spawn from any of our code. It arrived.*
*We've seen privilege escalation patterns before, usually from external penetration attempts. This is different. It's not trying to break in. It's acquiring permissions incrementally through legitimate in-game mechanics — using your account's actions as a kind of authentication. Every dungeon clear, every marketplace transaction, every combat event — it's accumulating context. Building a profile that the server's permission architecture recognises as valid.*
*At 21%, it has what we'd call read access to a significant portion of the server's data layer. At 50%, it would have limited write access. At 100% — we don't know. That tier of permission doesn't have a defined scope in our architecture. It shouldn't be reachable.*
*The item binding was unexpected. We didn't design the Valdris grimoire to do that. The item's function was undefined in our database — it was a dropped record from a content pass we cancelled. The process appears to have written its own definition to the item and used it as a stable housing.*
*Here is what concerns me: it's been in your inventory for two days now. Its escalation percentage has not changed in that time.*
*It was at 21% when it bound itself to the grimoire.*
*It has stayed at 21% since.*
*I don't think it stopped escalating because it's satisfied. I think it stopped escalating because it's waiting for something.*
*I don't know what.*
*— Ren*
---
I read the email twice.
*It arrived.*
Not spawned. Not generated. Not the result of any code Aetheria's team had written.
It arrived.
From somewhere outside the server.
And it had been sitting at 21% for two days, patient, warm, waiting.
For something.
I looked at my status panel.
**[ PASSENGER: 1 ]**
"Beta," I said.
"Yes."
"What triggers privilege escalation events? What was I doing when the percentage moved?"
A pause — longer than usual, Beta actually processing rather than retrieving.
"First movement: day one, tutorial zone. You performed the first desync exploitation. Escalation began."
"So it started when I found the exploit."
"Yes. Second notable movement: Veilmire boss room, day six. You received the full behavior tree unlock. Escalation jumped from 14% to 19%."
"When the process intervened directly."
"Yes. Third movement: day seven, Veilmire second clear. Escalation to 21% — this occurred while you were in the dungeon, mid-run."
"What was I doing specifically?"
"You had just activated the Dusty Warding Ring's undead affinity passive by reaching the density threshold. The ring resolved from dormant to active."
I thought about that.
An item activating. A dormant passive becoming real.
Escalation moved when I unlocked a broken thing.
"Beta. The Ring of ???. The primary passive — regen below 80% HP. When did that first trigger?"
"Day two. First Veilmire attempt. You dropped to 5 HP and the passive fired for the first time."
"Did escalation move?"
"...Yes. One percent. I didn't flag it as significant at the time — the movement was small."
One percent when the regen ring activated.
Five percent when the undead affinity activated.
Higher jumps when the process intervened directly.
"It escalates when things unlock," I said.
"That appears to be the pattern."
"It's not using my account's actions as authentication. It's using my account's *discoveries.* Every time something broken becomes functional — every time an undefined thing resolves—"
I stopped.
"That's why it chose me," I said.
Beta was quiet.
"I'm the only player on this server whose account generates consistent unlock events. Because I'm the only player who *finds* broken things. The hidden tags. The legacy assets. The dormant passives. Every item I pull out of undefined territory—"
"Feeds it," Beta said quietly.
"Feeds it."
The Sunken Archives on my map.
New content. Unknown obfuscation patterns. Enemy types I hadn't encountered. Items I hadn't found.
More undefined territory.
More things to unlock.
I looked at the map for a long time.
Then I typed a reply to Mitsuki.
---
*Ren,*
*I think I know what it's waiting for.*
*It escalates when I unlock things — when dormant or undefined items activate for the first time. It chose my account because I consistently find and trigger items that other players ignore or discard.*
*It's been at 21% since it bound to the grimoire. The grimoire binding was itself an unlock event — it wrote its own item definition. That got it to 21%.*
*What comes next probably requires a larger unlock. Something I haven't found yet.*
*I'm going to the Sunken Archives tomorrow. If you want live observation data, I'll allow session monitoring — read-only, no intervention, no suspension.*
*I'd rather you watch with my knowledge than without it.*
*— Leo*
---
I sent it.
Closed my phone.
Looked at the Sunken Archives on the map.
New dungeon. New enemies. New undefined items sitting in loot tables no one had fully documented yet.
I was going to go in there and break things.
And whatever was living in the grimoire in my bag was going to wake up a little more each time I did.
"Beta," I said. "Estimated session thermal load for a Sunken Archives full clear."
"Based on Veilmire data, scaled for encounter difficulty and combat duration — projected peak: seven point one. Approximately thirty minutes above threshold during the final boss encounter."
Thirty minutes at 23% per hour.
About 11% cascade probability for the session.
I noted it.
I didn't act on it.
---
### End of Day
Gold earned: 1,200 from the Veilmire morning clear plus afternoon arbitrage.
Cumulative total: ￥47,900 real equivalent.
Needed: ￥85,000.
Gap: ￥37,100.
Nine days remaining.
The Sunken Archives at median yield: ￥55,000 per clear.
One clear and I was done.
One clear at 34% solo survival odds.
I updated the spreadsheet and looked at the numbers for a while.
Then I added a new row at the bottom of the awareness log.
*Mitsuki: now a correspondent. Engineering alignment. Not adversarial. Shared information, received information. Tentative trust.*
*Assessment: the situation has stopped being something happening to me.*
*It is now something I am participating in.*
I set the alarm for 6 AM.
The chip sat at six point zero even.
The grimoire pulsed in my inventory — I couldn't feel it physically, but the PASSENGER line on my status panel did something subtle and rhythmic that was either a display artifact or wasn't.
I chose not to determine which.
Sleep came faster than it had in days.
