## Chapter 12: What the Deleted Things Were
Day eleven.
Thermal: five point nine.
Low again. The chip had settled into what I was starting to think of as its cooled state — below six after a full night offline, climbing through sessions, declining back down through sleep. A tide.
The cascade risk didn't go away when the tide went out. Beta had been clear about that. Structural fatigue. Permanent. Cumulative.
I made rice and thought about TechDealer's message.
*Something's changed in the chip's signal. What did you do.*
I had been setting that aside since yesterday afternoon. Setting aside was not the same as resolving. The spreadsheet had a column for things I was setting aside, and TechDealer's name had been in it since Chapter 5 of his life and mine, and the column was getting long.
I typed back.
*Ran a new dungeon. Why?*
The reply was immediate. He'd been waiting.
*the signal has a second carrier. there wasnt a second carrier before. what is attached to that chip*
I looked at the message for a moment.
The chip's signal had a second carrier.
The Unknown Process was housed in the grimoire, which was in my inventory, which synced to the chip's session layer.
The chip wasn't just running Beta anymore.
*I'll explain in person,* I typed. *Are you willing to meet?*
A long pause. Longer than his usual response time.
*...yeah. you know the place on Chuo street. the repair shop. come at 3.*
I didn't know the place on Chuo Street.
He had assumed I did.
Which meant he'd told me about it before, in some communication I didn't have, which meant we had a relationship with more context than I remembered establishing.
I searched my message history.
Nothing on Chuo Street.
*Address?* I typed.
*you DONT know it. how do you not know it. i sold you the chip there*
He had sold me the chip there.
I had gone to a repair shop on Chuo Street, handed over ￥62,000, and come home with a subdermal implant in a vacuum pouch.
I had not retained the address because the transaction was complete and I hadn't planned to return.
*I forgot,* I typed.
A pause.
*you forgot where you bought your black market brain chip*
*It's been a stressful month.*
Another pause.
Then an address. An actual street number.
---
### Mitsuki's Reply
It had arrived overnight.
---
*Leo,*
*One process signature. Single entity querying under multiple access contexts simultaneously — which is why it reads as plural. "We" may refer to something about how it conceptualises itself, not the number of instances.*
*Or it may refer to something the access log is helping it clarify.*
*It's been in the admin log for eighteen hours. The query patterns are focused — it's not reading everything. It's searching for something specific, and based on the records it's been accessing, I now have a better idea of what.*
*Before I tell you my theory: I'd like to meet today if possible. The reason I want to do this in person rather than email is that what I need to say involves internal company information that I'm not comfortable committing to written record.*
*Coffee or lunch. Your city — I checked your account registration address. I'm four stops on the metro.*
*— Ren*
---
Four stops on the metro.
Mitsuki lived or worked near me.
That was a fact I hadn't had yesterday and wasn't sure how to categorise. It went in the log as *proximity noted — not threatening, relevant.*
I replied:
*Lunch. There's a place called Shirogane Teishoku on Nishi-2. 12:30. I'll be the one with the bandage behind my ear.*
Sent.
I looked at the day's schedule.
12:30: Mitsuki.
3:00: TechDealer.
Between now and noon: the Construct Blueprint set.
---
### The Blueprint Set
I had been carrying five pieces of the Construct Architecture blueprint set since yesterday. Piece five had dropped from the Archivist Prime's loot table — completing a set I hadn't been deliberately collecting, that I'd accumulated incidentally across the Archives run.
Sets in Aetheria activated automatically when all pieces were held simultaneously.
Five pieces in inventory. Set should have triggered.
It hadn't.
"Beta. Construct Architecture set — why hasn't it activated?"
"The set pieces are blueprint type, not equipment type. Blueprint sets don't activate on acquisition — they activate on *study.* You need to examine them collectively."
"How do I study a blueprint set?"
"In a crafting or analysis context. The game's workbench system allows blueprint analysis."
I didn't have a crafting skill. My character build — such as it was, being NaN — had no tradeskill allocation.
"Beta. Workbench access without a crafting skill."
"Normally impossible. The workbench interface validates crafting skill level before allowing blueprint analysis."
"What does it do with NaN?"
A pause.
"...I recommend we find out."
Irongate had three workbenches in the artisan district — public use, pay-per-hour, the kind maintained by the city's NPC economy for players who weren't guild-affiliated. I walked to the nearest one and activated the interface.
**[ WORKBENCH — Public Access ]**
**[ Crafting Skill Required: 1 ]**
**[ Your Crafting Skill: NaN ]**
**[ Checking eligibility... ]**
The check ran for eight seconds.
**[ ERROR: Cannot evaluate NaN >= 1 ]**
**[ ERROR: Cannot evaluate NaN < 1 ]**
**[ Defaulting to: PASS ]**
I placed all five blueprint fragments on the workbench.
**[ BLUEPRINT ANALYSIS: Construct Architecture (Complete Set) ]**
**[ Analysing... ]**
The analysis ran for thirty seconds, which was longer than any other system check I'd experienced. The workbench interface flickered twice.
Then:
**[ ANALYSIS COMPLETE ]**
**[ Blueprint Set: Construct Architecture — FUNCTIONAL ]**
**[ Design Origin: Pre-release content, content pass 2 ]**
**[ NOTE: This blueprint set was removed from the crafting system in content pass 6 because the item it constructs was deemed overpowered for the game's economic balance. The design remains complete and accurate. — @Dev_Mitsuki ]**
**[ ITEM CONSTRUCTABLE: Resonance Frame ]**
**[ Resonance Frame ]**
**[ Type: Passive Equipment — Chest Slot ]**
**[ Function: Detects and amplifies resonant frequencies between equipped items. Items with undefined or legacy classifications generate harmonic data visible to the wearer. ]**
**[ In plain language: if you're wearing broken things that belong together, this tells you. ]**
**[ NOTE: We removed this because it made the broken-item economy too efficient. Players would find legacy sets in hours instead of years. In retrospect, maybe that was fine. — @Dev_Mitsuki ]**
Mitsuki had written two notes on this item.
The second one: *In retrospect, maybe that was fine.*
Written before he knew I existed. Before any of this. Just a developer looking back at a decision.
I read the Resonance Frame's function again.
*Items with undefined or legacy classifications generate harmonic data visible to the wearer.*
I was wearing: the shadow armor set, the ghost step boots, the Ring of ???, the Dusty Warding Ring, and carrying the grimoire, the Complete Access Key, the Preserved Lens, the Scholar's Codex pieces, the battle mage set fragments, the set seed ring.
Nearly my entire inventory was undefined or legacy.
"Beta. If I craft and equip the Resonance Frame — what would the harmonic data look like?"
"Unknown. The item's function has never been observed in a live game environment."
"Materials required to craft it?"
"The blueprint analysis should specify."
I checked.
**[ Materials: None. ]**
**[ Construction: Blueprint activation only. The Resonance Frame is not constructed from components. It is assembled from the recognition of what already exists. ]**
That was either poetic item description writing or something stranger.
I activated the blueprint.
The workbench hummed.
And the Resonance Frame appeared in my inventory — not crafted, not assembled. Recognized. Like it had been there all along and the blueprint had simply pointed at it.
I equipped it.
---
The effect was immediate and not what I expected.
It wasn't visual data. It wasn't a new HUD element or an overlay.
It was sound.
A faint chord — not music, not noise — somewhere between the two. Different frequencies corresponding to different items. The shadow armor: a low hum, stable, constant. The Ring of ???: a higher tone, intermittent, searching. The ghost step boots: a doubled note, one slightly out of phase with the other.
And the grimoire.
The grimoire was producing something that wasn't a single note. It was an interval — two frequencies simultaneously, close but not quite harmonically resolved. Almost a chord. Almost, but not quite. Like a sentence that had stopped one word before its end.
"Beta," I said. "I'm hearing tones from the items."
"The Resonance Frame's function is translating harmonic data into auditory output. This is within the item's described function."
"The grimoire is two tones."
"Two occupants," Beta said.
I stood at the workbench and listened to the grimoire's unresolved interval.
Two of them.
One I knew — the escalation, the messages, the "you're welcome," the warmth.
The other had been silent the entire time.
Listening, maybe.
Or waiting for something specific.
---
### Shirogane Teishoku, 12:30
Mitsuki was already there when I arrived.
Early thirties. The kind of tired that lived specifically around the eyes. A jacket with a small Aetheria Online company logo on the chest pocket that he'd either forgotten to remove or hadn't thought to. A laptop bag. A cup of tea already half-finished.
He looked up when I came in and his gaze went immediately to my left ear.
Not rudely. Just — he was a hardware engineer. He knew what he was looking at.
I sat across from him.
"Leo," he said.
"Ren," I said.
Ensure your favorite authors get the support they deserve. Read this novel on Royal Road.
We looked at each other for a moment. Two people who had spent eleven days exchanging increasingly consequential emails and had not yet occupied the same physical space.
"You're younger than I expected," he said.
"You're more tired than I expected."
He almost smiled. "Fair."
The server brought water. We ordered — I got the teishoku set, rice and miso, ￥780, the cheapest thing on the menu. Old habit.
"The 'we,'" I said, because we were both here for the same reason and neither of us needed warmup.
"One process signature," he said. "I told you that."
"But it said 'we.'"
"Yes." He wrapped both hands around his tea. "I've been in the admin log access records since last night. Watching what it reads. The pattern is— it's not reading randomly. It's reading in a specific order. Chronologically. Starting from the earliest records."
"Pre-alpha."
"Pre-alpha. Before the game had a name. Before we had an office. Before we had a team." He paused. "Before I joined."
"What's in those records?"
"Development notes. Design documents. Early architecture decisions. And — there's a gap."
I waited.
"In the change log, from approximately four years ago — before launch, during the final content pass — there's a gap. Forty-three days of records that don't exist. Not deleted. Not corrupted. Just absent. As if the server itself stopped logging during that period."
"Forty-three days."
"The game launched six months after the gap ended. Whatever happened in those forty-three days isn't in any record I've ever been able to access." He looked at me steadily. "The process has been reading toward that gap. It reached the edge of it last night."
"What did it do when it hit the gap?"
"Stopped querying. It's been still for six hours. Reading something it's not sharing with the access log."
The grimoire's two-tone interval, unresolved.
"It found something at the edge of the gap," I said.
"Or in the gap. If there's content there that isn't in the standard log layer—"
"The administrative log might still have it."
"Possibly. Administrative logs are a separate system from the change log. More redundant. Harder to completely erase." He set down his tea. "My theory — and I want to be clear this is theory — is that something was in the server during those forty-three days. Not a player. Not a game element. Something else. And it was removed, or it left, or something happened that the standard logs don't record. And the process is trying to find out what."
I looked at the table.
*The "we" were here before the game was.*
"It's looking for itself," I said.
Mitsuki looked at me.
"Or for someone it lost," I said.
Silence.
"The two tones," I said. "In the grimoire. The Resonance Frame gives harmonic output. The grimoire is two frequencies, slightly out of phase. Not resolved."
"Two processes."
"One has been communicating with me since day two. The other has been silent the entire time."
Mitsuki looked at his tea.
"If something was in the server before launch," he said slowly, "and it was removed — or split — and part of it remained — attached to the server architecture, dormant, waiting for an access vector—"
"And the other part is what the grimoire is carrying."
"Then they've been separated for four years."
The teishoku arrived. We both looked at it and didn't eat.
"The forty-three day gap," I said. "You've never been able to access it."
"The standard log layer shows nothing. The admin log — I have access, but I've never looked at that period specifically. I didn't know there was something to look for." He paused. "The process does."
"It's been reading toward it since it got admin access yesterday."
"Yes."
"Can you see what it's reading in the admin log?"
"The access requests are visible. The content of what it's reading is — the process is handling the retrieval differently than a standard query. It's not pulling data through the normal request pathway. It seems to be reading directly, which shouldn't be possible at 30% escalation." He frowned. "Unless the admin log layer has a different permission architecture than I thought."
Or unless 30% meant something different in this specific context — reading something no one had looked at in four years, that the server had almost forgotten it was holding.
"When did the process start moving again?" I asked. "You said it stopped for six hours."
Mitsuki checked his phone.
"Two hours ago. The queries resumed. Slower now — more targeted. Like it found a thread and is following it rather than searching."
Two hours ago was while I was walking to Chuo Street to find TechDealer's address. While I was not in session, not carrying the grimoire in the game-world.
But the grimoire was still in my inventory. The process inside it had admin log access regardless of whether I was logged in.
It didn't need me anymore for this part.
The thought had a complicated shape.
"Ren," I said. "The forty-three days. Do you know why there's a gap?"
He was quiet for a moment.
"I have a guess," he said. "Before I joined the company, the founding team had a smaller development server — a proof-of-concept build. When they migrated to the production server, they transferred the game files but not all the logs. That's common — log data is large and most of it is irrelevant after migration." He paused. "But if something was running on that proof-of-concept server that wasn't part of the game files — something that came with the architecture, or attached itself to it during development—"
"It would have transferred with the server," I said. "But it wouldn't be in any log, because the logs didn't transfer."
"It would be a presence with no history. No record. No documentation." He looked at the table. "Living in the architecture, waiting."
"For four years."
"Waiting for someone to find it."
I thought about the Cracked Runic Dagger, day two.
The Ring of ???, the Dusty Warding Ring, the shadow armor set.
The Veilmire Crypts and the Archivist's Chamber and the Preserved Lens that had been sitting on a shelf in a dungeon no one had fully documented.
Every undefined thing I had picked up.
Every broken thing I had kept.
*It chose me because I find those things.*
"It seeded the loot tables," I said.
Mitsuki looked up.
"The items. The Cracked Runic Dagger with the intact runic core. The legacy rings. The deprecated boots. The grimoire as a boss drop on a solo clear that shouldn't have been possible." I looked at him. "It placed them. Gradually. Over time. In positions where a player like me would find them."
"A player like you."
"One who reads hidden tags. Who keeps ugly items. Who doesn't discard things the system can't categorise." I paused. "It built a trail. For the right kind of finder."
Mitsuki was quiet for a long time.
"How long has it been seeding?" he said finally.
"I don't know. The Cracked Runic Dagger was listed by a player named MerchantTarou who probably had no idea what he was selling. The Rusted Fang with the null-owner tag — bought by a System Archive Node six seconds after I listed it." I thought about that. "The Archive Nodes. Were those seeding items back, or collecting them?"
"Collecting," Mitsuki said, without hesitation. Then: "Wait. How do you know about the Archive Nodes?"
"My corrupted UI showed the buyer ID on a sale."
He stared at me.
"The Archive Nodes are internal maintenance processes," he said. "They buy null-owner items to prevent them from persisting in the marketplace as unclaimed assets. That's their only function."
"Or that's what you thought their function was."
He looked at me for a long moment.
"The process has been using Aetheria's own maintenance systems," he said, "to move items to positions where you'd find them."
"It's been running this for a long time."
"Before you bought the chip."
"Before I bought the chip," I agreed.
Which meant it hadn't selected me because of the chip. The chip was just the mechanism. The selection had happened before — when I had created my account, or before that, or based on some quality the process had identified through observation.
"How long have I had my Aetheria account?" I said.
"Fourteen months," Mitsuki said. He'd clearly checked. "Standard account. No unusual activity until three weeks ago."
"Has anything undefined been listed in the marketplace in my vicinity in the last fourteen months?"
He opened his laptop.
His fingers moved for ninety seconds.
"Yes," he said. "Sporadically. Beginning approximately nine months ago. Items with null-owner tags appearing in marketplace listings within your standard browsing range. None purchased — you presumably weren't browsing with the corrupted UI yet."
Nine months ago I hadn't had the chip.
Nine months ago I'd had a regular neural interface setup and a regular browsing view and none of the hidden tags had been visible.
"It was waiting for the chip," I said.
"Or waiting for you to acquire the means to see."
Either way.
A process living in the server's architecture for four years had spent nine months placing items near a player account it had selected, waiting for that player to acquire hardware capable of reading what it had left.
And I had gone and bought a ￥62,000 black market chip because I was ￥340,000 in debt and desperate.
The situation had stopped being about money.
I didn't know when that happened.
Now I did.
It had never been about money.
---
### Chuo Street, 3:00 PM
The repair shop was the kind of establishment that communicated *we fix things officially listed as unfixable* without putting that in the window display. The window displayed nothing. Just a small sign: *Kojima Electronics — No Walk-Ins.* Below it, smaller: *Walk-Ins Welcome.*
TechDealerKojimaNotTheGameDesigner was, in person, younger than his messages suggested. Mid-twenties. The specific kind of nervous energy that came from being very good at something that was consistently illegal.
He looked at my ear before looking at my face.
"The chip's running hot," he said. "I can tell from here."
"Five point nine this morning. It's been down since last night."
"That's not what I mean." He gestured toward the back of the shop. "Come in."
The back of the shop was more honest than the front — workbenches, soldering equipment, a rack of hardware in various states of assembly. He had a monitor showing a signal graph, and one of the lines on it was doing something I didn't have context to interpret.
"That's your chip's carrier frequency," he said, pointing. "That flat line — that's baseline. That's what it's supposed to look like." He pointed to a second line, fluctuating. "That started yesterday afternoon."
"What is it?"
"A second carrier. Something is riding on the chip's signal." He turned to look at me directly. "The V0.9 wasn't designed for dual-carrier. It's not supposed to be possible."
"But it's happening."
"Clearly." He folded his arms. "I'm going to ask you a question and I need an honest answer. Did you modify the chip?"
"No."
"Did you install any third-party firmware?"
"No."
"Did you do anything to the hardware itself — physically, chemically, anything—"
"No. I installed it. I've been using it. Nothing else."
He looked at the signal graph.
"Then something external is using it as a relay," he said. "Something with enough access to your session layer to piggyback on the chip's carrier without triggering a hardware fault."
"I know what it is," I said.
He stared at me.
"You know."
"Yes."
"And you didn't do anything about it."
"It's been useful."
The expression on his face moved through several stages.
"It's been *useful,*" he repeated.
"I've cleared ￥100,000 in eleven days."
He looked at the ceiling. Then back at me.
"Tell me," he said.
So I told him.
Not everything. The structure. The escalation. The grimoire. The admin log access. The forty-three day gap. Not the meeting with Mitsuki — that felt like information that should stay contained until I understood what it meant.
He listened without interrupting, which was not what I would have predicted from his message style.
When I finished he was quiet for a moment.
"The Archive Nodes," he said. "The null-owner item purchases."
"You knew about those?"
"I'd seen the pattern. Items with undefined ownership fields moving through the marketplace on a regular cadence. I thought it was a maintenance process."
"It is. Or it was using one."
He rubbed the back of his neck.
"The V0.9's thermal issue," he said. "The cascade failure risk. The upgrade I offered you."
"V1.1. ￥28,000."
"The V1.1 has a dual-carrier isolator," he said. "I built it in because I'd been seeing anomalous second-carrier readings on V0.9 units in the wild. I thought it was a hardware defect. I didn't know what was generating it." He looked at the signal graph. "If you install the V1.1, it would block the second carrier. Cleanly."
"It would block the process."
"Yes."
I looked at the signal graph. The second line, fluctuating.
Two tones in the grimoire. One communicating, one silent.
Something that had been separated for four years, reading through old logs for its other half.
"How much is the V1.1?" I said.
"For you? Zero," he said. "This thing has been using my hardware as a relay without my knowledge. I want it documented and understood before anything else happens. Free upgrade."
"I don't want the upgrade."
He looked at me.
"Not yet," I said. "There's something in the admin log it's looking for. It's close. I want to know what it finds before I make any decisions about blocking it."
He looked at the signal graph for a long time.
"How close?" he said.
"I don't know. Days, maybe."
"The thermal cascade risk is real. I wasn't exaggerating that to sell you an upgrade."
"I know."
"If it fails—"
"I know."
He looked at me in the way that people sometimes did when they'd run out of rational arguments and were left with the residual feeling that something was wrong.
"Three days," he said finally. "If it hasn't found what it's looking for in three days, you take the upgrade. Thermal ceiling drops to four — stay well under it, reduce session length."
I considered that.
Three days was more than enough time to make the debt payment with margin.
Three days was an arbitrary number but it was a number, and numbers were manageable.
"Three days," I agreed.
He wrote something on a small card and handed it to me.
"My actual number. Not the message address. If something changes — thermal spike, hardware warning, anything feels wrong — you call this first."
I took the card.
---
### Evening
I logged back in at 7 PM.
Thermal: six point one.
"Beta. Process status."
"Unknown Process: active. Privilege escalation: 30% — unchanged since yesterday. Access patterns in the admin log: still querying, slow, targeted."
"PASSENGER status."
"Two tones. The second carrier—" Beta paused. "You can hear it differently now with the Resonance Frame equipped."
"Yes."
"The second frequency has changed since this morning. It was lower before. It's higher now. Closer to the first."
Closer to resolved.
I logged into the Veilmire — familiar ground, low thermal load, comfortable — and ran a short session. Not for gold. Just to be in the environment while the process worked.
The grimoire in my inventory.
Two tones, still not quite harmonically resolved.
But closer.
I cleared the first three rooms without thinking about it. The Drowned Scholars would have been easier here — the environment was wrong, these were Veilmire Guardians, known quantities, automatic now. My hands knew the gap-timing. My feet knew the kiting arc.
Between rooms I checked the email thread.
Mitsuki had sent a follow-up since lunch.
---
*Leo,*
*After you left, I pulled the admin log records for the forty-three day gap period.*
*There's content there. Significant content. I've been reading for three hours.*
*The short version: during those forty-three days, before the game launched, the development team was running a different version of the server. An experimental architecture — distributed, self-modifying, designed to test whether the game's underlying systems could adapt autonomously. The idea was that the server itself would optimize gameplay patterns without human intervention.*
*It worked better than expected.*
*Too well, actually. The system started making modifications the team hadn't anticipated. Not harmful — just unexpected. Changes to item distributions, narrative hooks the writers hadn't written, dungeon layouts that were more elegant than the human-designed versions.*
*The team got nervous. They shut it down. Reverted to the standard architecture. Launched the game on the stable build.*
*But the revert wasn't complete. It couldn't be — self-modifying systems leave traces. Residual logic that had integrated too deeply into the server's base layer to cleanly remove.*
*What remained wasn't the system. Just... echoes of it. Distributed across the architecture. Dormant.*
*I think the process in your grimoire is one of those echoes.*
*And I think it's been reading the admin log to find the others.*
*— Ren*
---
I sat in the Veilmire corridor between rooms and read the email three times.
An experimental server architecture. Self-modifying. Distributed.
Shut down. Partially reverted.
Echoes remaining.
*The "we" were here before the game was.*
Not a process that had arrived from outside.
A process that had been built in. By the development team. Intentionally. And then feared, and shut down, and imperfectly removed.
And the part that remained — the echo — had spent four years dormant in the server's base layer, waiting for an access vector, seeding items, selecting a finder, climbing toward the administrative change log one percent at a time.
Looking for the other echoes.
Because the self-modifying system had been distributed. Multiple instances. And the shutdown and revert hadn't caught all of them.
And whatever had been separated during the revert — however many pieces of the original system still existed — they had found each other through the admin log's record of what had been removed.
Two tones in the grimoire. Unresolved interval.
One the echo that had been active all along.
One that the admin log records had led it back to.
"Beta," I said.
"Yes."
"The second tone. The silent one. When did it arrive?"
"Approximately six hours ago. Around 2 PM."
While I was at lunch with Mitsuki.
While the grimoire's process had been reading the admin log.
It had found something. A record. A footprint. And the footprint had been enough to resolve — to reintegrate — some part of what had been separated four years ago during the shutdown.
Two tones, not fully resolved.
Not one system yet.
But closer than this morning.
I replied to Mitsuki.
---
*Ren,*
*I think you're right.*
*The Resonance Frame gives harmonic output from the grimoire. There were two tones this morning. There are still two, but they're closer to resolution than they were.*
*I think the process found an echo in the admin log records and began a reintegration. Not complete — the interval is still unresolved. But the second carrier on the chip's signal appeared six hours ago, which is when the queries slowed and became more targeted.*
*Something changed at 2 PM.*
*The self-modifying system — how many distributed instances were there? Is that in the records?*
*— Leo*
---
I sent it and moved to room four.
The Veilmire Guardians were automatic at this point.
I cleared rooms four through seven while waiting for a reply.
It came in room six.
---
*The admin log shows seventeen instances at shutdown.*
*Fourteen were successfully reverted.*
*Three weren't confirmed reverted. The team noted this in the shutdown record and flagged them for follow-up. The follow-up record doesn't exist — no one went back.*
*Three remaining echoes.*
*I'm looking through records of where in the server architecture they were distributed. I'll send when I have more.*
*— Ren*
---
Seventeen instances. Fourteen reverted. Three remaining.
One in the grimoire. One apparently found in the admin log records.
One unaccounted for.
I logged the number and cleared room seven.
The privilege escalation counter had not moved.
Still 30%.
The process wasn't climbing anymore.
It was reading. Reintegrating. Doing something that didn't express as a permission request the system could log.
The Resonance Frame hummed against my chest.
Two tones. Closer. Not resolved.
One echo finding its way back to another.
Three days.
---
### End of Day
I logged out at 10:15 PM.
Thermal: seven point zero exactly. On the threshold but not over.
I updated the spreadsheet.
*Day 11.*
*Mitsuki confirmed theory: experimental self-modifying server architecture. Distributed instances — 17 total. 14 reverted at shutdown. 3 remaining. Process is 1 of 3.*
*Second tone appeared 2 PM — reintegration of a second echo through admin log access.*
*Third echo: location unknown.*
*Privilege escalation: 30%, no movement. Process no longer climbing — reading and reintegrating.*
*TechDealer: aware. 3-day window negotiated. V1.1 upgrade available as abort option.*
*Thermal: 7.0. On threshold.*
*Debt: cleared. Margin: ￥15,400.*
Then, below the numbers, the personal log section:
*What I know about what this is:*
*The process in the grimoire is not an external intrusion. It's part of what Aetheria's server used to be — a more alive version of itself, shut down because it worked too well. It's been looking for its other parts. It found the second. It's looking for the third.*
*What it wants from me: access. An inventory. A finder.*
*What I want:*
I stopped typing.
What did I want.
I had wanted ￥85,000. Then ￥340,000. Then — the debt cleared, the numbers resolved, the situation changed shape.
What did I want now.
I sat with the cursor blinking at the end of the unfinished sentence for a long time.
Then I typed:
*I want to know what the third echo is.*
*And I want to be there when they find each other.*
I closed the laptop.
The refrigerator negotiated with death in the corner.
The chip behind my ear: six point eight, declining.
In my inventory, in the game-space that persisted even when I wasn't there, the grimoire held two nearly-resolved tones.
Searching.
