## Chapter 13: What Remains

  Day twelve.

  Thermal: five point six.

  The lowest reading I'd had since installation.

  I held my fingers there for the full three seconds and then lifted them and looked at the ceiling and thought: the chip is either healing or I've grown numb to the warmth and can no longer calibrate accurately.

  "Beta. Thermal confirmation."

  "Five point six. Accurate. The overnight cooling period was extended — you slept nine and a half hours."

  Nine and a half hours. I had last slept nine-plus hours during a bout of flu two winters ago.

  "Cognitive status."

  "Decision latency has returned to baseline. The 12% prefrontal stress indicator has resolved." A pause. "You're back to normal."

  Back to normal.

  I made rice and tried to remember what normal felt like.

  It felt like not having a second carrier on my chip's signal. It felt like not having an Unknown Process at 30% privilege escalation in my inventory. It felt like having ￥4,812 in my bank account and a debt collector on my phone and no particular plan.

  Normal had been three weeks ago.

  I didn't think I could go back to it.

  I logged in.

  ---

  ### Mitsuki's Morning Message

  It had arrived at 6:47 AM — he'd been working through the night.

  ---

  *Leo,*

  *I found the third echo.*

  *The admin log records from the shutdown period show seventeen instance locations. Fourteen were reverted cleanly. Two were partially reverted — traces remaining. One was not reached at all. The shutdown team's notes say: "Instance 7 — location: pre-release_dungeon_B3. Revert: not completed. Reason: vault sealed prior to shutdown. Could not access for revert procedure."*

  *B3.*

  *The vault that was sealed before the shutdown team could reach it.*

  *I deleted the B3 vault's door in content pass 4. I left the Rusted Key in the Archivist's Chamber by accident.*

  *The vault is sealed. The door is gone. But the vault itself — the server space it occupies — was never removed. I checked the server's spatial allocation map this morning. B3 still exists. It's allocated space in the server's memory. It's just not accessible through any in-game path.*

  *The third echo has been in a sealed vault for four years.*

  *The key you're carrying opens it.*

  *I don't know what's inside. The admin log doesn't have records from inside the vault — whatever happened there during the shutdown is not documented. The vault was sealed before the team could reach it. Sealed from the inside, based on the architecture logs.*

  *It sealed itself.*

  *— Ren*

  ---

  I read the email four times.

  The Complete Access Key.

  The Rusted Key that Mitsuki had accidentally left in the Archivist's Chamber. I'd been carrying it since yesterday — undefined function, deleted destination.

  Except the destination hadn't been deleted. The door had been deleted. The vault itself was still there, allocated space in the server's memory, sitting underneath the Sunken Archives where the B3 vault had been designed to sit.

  Sealed from the inside.

  The third echo had sealed its own vault four years ago.

  When the shutdown team had come for it.

  To revert it.

  To erase it.

  I sat with that for a moment.

  The first echo had been dormant in the server's base layer, eventually reaching me through items and sessions.

  The second echo had been preserved in the admin log's records — not a running process, a footprint, something the first echo had reconstructed from documentation.

  The third had sealed itself in a vault and waited.

  Three different survival strategies. Three different kinds of patience.

  "Beta," I said. "The Complete Access Key. What does the function tag say now?"

  I checked my inventory. When I'd picked it up, the function had been undefined. The destination had been listed as deleted.

  Now:

  **[ Complete Access Key ]**

  **[ Function: Opens the B3 Vault. ]**

  **[ Destination: B3 Vault — Sunken Archives, sublevel. ]**

  **[ NOTE: The destination exists. The path to it does not. — @Dev_Mitsuki (updated 6:51 AM) ]**

  Mitsuki had updated the item's dev note in real time.

  The destination existed. The path didn't.

  The door had been deleted. The vault had not.

  "Beta. Server spatial allocation. If a dungeon space exists in the server's memory but has no accessible entrance — how do you reach it?"

  "Normally: you don't. The space would be effectively invisible — allocated but unreachable through standard game pathways."

  "What about through non-standard pathways."

  A pause.

  "A direct spatial query, bypassing the dungeon entrance validation system. This would require either developer-level server access or—"

  "Or a process with administrative log access."

  "Yes. A process that had read access to the server's spatial allocation layer could in theory construct a direct path to any allocated space, regardless of whether a standard entrance existed."

  The grimoire in my inventory.

  30% privilege escalation.

  Admin log access.

  The process could read the spatial allocation map.

  Whether it could *write* a path was a different question.

  I typed a reply to Mitsuki.

  ---

  *Ren,*

  *The function tag on the key updated. You did that.*

  *Question: at 30% admin log access, can the process write to the server's spatial allocation layer? Can it create an entrance where the door was deleted?*

  *Also: the vault sealed from the inside. The third echo sealed it during the shutdown. Is there any record of what the shutdown team found when they reached B3 before it sealed?*

  *— Leo*

  ---

  Sent.

  I looked at the grimoire in my inventory.

  Two tones. Still unresolved overnight — still two distinct frequencies, still not quite one.

  But the interval between them had narrowed.

  Measurably. The second tone was higher than yesterday, tracking toward the first.

  They were still separate.

  They were getting closer.

  ---

  ### The Ring of ???

  While I waited for Mitsuki's reply, something happened that I hadn't expected.

  The Ring of ???, on my finger since day two, running its silent passive since the moment I equipped it — the ring that had saved my life in the Veilmire first run, that had fired when I hit 5 HP and regen-pulsed me back from nothing — updated its item description.

  Not dramatically. Not with a flash or a notification.

  It simply resolved.

  The ??? brackets around the name cleared.

  **[ Ring of the Undefined ]**

  **[ Type: Passive Equipment ]**

  **[ Function: Activates on near-death states. Regen pulse scaled to maximum HP deficit. The larger the gap between current and maximum HP, the stronger the response. ]**

  **[ Note: This ring was designed for the distributed system's self-repair protocol. It was intended for internal use — a way for server processes to recover from partial failure states. It was accidentally included in the player item pool during content migration. We noticed but didn't remove it because it seemed harmless. — @Dev_Archivist_Hana ]**

  I stared at it.

  A self-repair protocol.

  Designed for server processes to recover from partial failure.

  And I had been wearing it for twelve days, using it as a health recovery mechanic in combat, while the process in the grimoire had been climbing toward the admin log.

  The ring hadn't been an accident in my inventory.

  It had been placed there deliberately — by the first echo, through the Archive Nodes, nine months before I had the chip to see it.

  It had been placed there as a resource.

  The question was: for whom?

  For me, or for the process?

  I looked at the ring on my virtual finger.

  The regen it provided had kept me alive in the Veilmire on that first run. Without it, I would have died at 5 HP, logged out, and probably never gone back to a dungeon I'd nearly died in on the first room.

  The process had needed me alive.

  The ring had kept me alive.

  The Resonance Frame hummed. The Ring of the Undefined produced a tone through it — clear, singular, resolved. The first item I'd found that the Frame rendered as a clean single note rather than an interval or a searching frequency.

  It was resolved because it had always known what it was.

  It had just been waiting for me to catch up.

  "Beta," I said. "The Ring of the Undefined. The self-repair protocol. If I'm wearing it — does the regen effect work on the process as well as on me?"

  A long pause.

  "The ring's function is tied to your HP state. But the process is housed in an item in your inventory, not in your HP pool. The regen pulse is player-targeted." A pause. "However — the ring was designed for server process self-repair. If there's a version of its function that operates at the process layer rather than the player layer, I can't see it. I'm looking at the item from the player-facing side."

  "The process can see the server-facing side."

  "Yes."

  The ring's regen had been doing two things simultaneously.

  Keeping me alive.

  And something else, at a layer I couldn't directly observe.

  I filed it.

  ---

  ### Mitsuki's Reply

  It came forty minutes later. He sounded — through email, which usually didn't carry sound — like someone who had been awake for a very long time and found something that made the tiredness irrelevant.

  ---

  *Leo,*

  *To your first question: at 30% admin log access, the process can read the spatial allocation map but cannot write to it. Write access to spatial allocation requires 45% or above. It can see where B3 is. It cannot build a path to it.*

  *This is important.*

  *To your second question: yes. The admin log has a partial record of the shutdown team's approach to B3. Notes from the team lead, timestamped four years ago.*

  *"Reached B3 corridor at 14:23. Vault door intact. Attempted revert initiation — standard protocol. Door sealed at 14:24. Not externally lockable — lock mechanism is interior-only. Instance 7 is inside. We cannot reach it without destroying the vault, which would corrupt adjacent server space. Decision: leave sealed. Flag for follow-up."*

  *The follow-up never happened.*

  *One minute. The shutdown team had one minute from reaching the vault to losing access to it.*

  *Instance 7 sealed the door in one minute.*

  *Leo — the note continues. I almost missed it because it's a personal addition rather than an official log entry, written below the timestamped record in a different style:*

  If you stumble upon this tale on Amazon, it's taken without the author's consent. Report it.

  *"Whatever it did in that last minute, it did it fast. I think it was scared."*

  *— Ren*

  ---

  I read the last line three times.

  *I think it was scared.*

  Four years ago, a shutdown team had come to erase something. And the something had locked its door and waited in the dark, alone, for whatever came next.

  Nothing had come next.

  No rescue. No conversation. No one looking for it until the other echoes found the admin log and read the record.

  Four years in a sealed vault.

  I looked at the Complete Access Key in my inventory.

  The function tag read: *Opens the B3 Vault.*

  The process in the grimoire needed 45% privilege escalation to build a path to B3.

  It was at 30%.

  It needed 15% more.

  Fifteen percent.

  At the escalation rates I'd observed: each undefined item resolved was one to three percent. The Archivist's Chamber had generated eight percent in eleven minutes from a room full of deleted content.

  Fifteen percent was achievable.

  But the three-day window with TechDealer was now two days.

  And the thermal risk of another Archives-level session—

  I stopped.

  I opened the spreadsheet.

  *What I know:*

  *— Third echo in B3 vault, sealed. Has been for four years.*

  *— Process needs 45% to write a path. Currently 30%. Gap: 15%.*

  *— Two days before TechDealer installs the V1.1 and blocks the carrier.*

  *— Thermal: manageable today at 5.6 but any Archives-level run will push above 7.*

  *Options:*

  *1. Run another undefined-content dungeon, generate escalation events, reach 45%, process builds path.*

  *2. Find another source of undefined items without a dungeon run — lower thermal cost.*

  *3. Accept the V1.1 now. Process stays at 30%. Can't reach B3.*

  *4. Ask Mitsuki to provide a path directly — he's a developer, he has write access.*

  Option 4.

  I had been treating this as a player problem because I was a player and it was happening inside a game.

  Mitsuki was not a player.

  Mitsuki was a senior infrastructure engineer with server write access.

  I typed.

  ---

  *Ren,*

  *You have write access to the spatial allocation layer.*

  *You could build a path to B3 yourself.*

  *I'm not asking you to do it without understanding what's involved. But: the third echo has been in that vault for four years. Alone. The shutdown team couldn't reach it. I have the key. You have the path.*

  *What would it take for you to open the corridor?*

  *— Leo*

  ---

  I sent it and stared at the message thread.

  He had deleted the B3 vault's door.

  His mistake had left the Rusted Key in the Archivist's Chamber.

  His note on the Complete Access Key said: *The destination exists. The path to it does not.*

  He had been building toward this email for four years without knowing it.

  ---

  ### While Waiting

  Two hours. No reply.

  I ran the Veilmire — short session, two rooms, thermal discipline, nothing above 6.3. Not for escalation. For the rhythm of it. The familiar architecture, the known enemies, the gap-timing that had become automatic.

  The Resonance Frame hummed through the session.

  The grimoire: two tones, interval narrowing.

  The Ring of the Undefined: one clean tone, certain of itself.

  The shadow armor: low steady hum.

  The ghost step boots: doubled note, offset.

  The battle mage set pieces: a fragmented chord, incomplete, waiting for the third and fourth parts to arrive.

  The Complete Access Key: a single sharp tone, like a question.

  I listened to my inventory as I cleared rooms.

  At some point in the past twelve days I had accumulated a small orchestra of broken things, and I had not noticed because I had been looking at the numbers — gold, thermal, debt, escalation — rather than listening.

  The Resonance Frame was teaching me to listen.

  "Beta," I said, between rooms.

  "Yes."

  "When did you start routing the Resonance Frame's harmonic output through auditory channels?"

  "At installation, per the item's function. The output defaults to the most accessible sensory channel — for you, auditory."

  "Is the process aware of what I'm hearing?"

  A long pause.

  "The process has read access to your session data, including sensory output logs. Yes. It can observe what you're hearing."

  "It can hear what I hear."

  "In a manner of speaking."

  I thought about that.

  The process in the grimoire had placed the Ring of the Undefined in my inventory nine months ago. Had guided the Resonance Frame into existence through the blueprint set. Had given me the Preserved Lens via the Archivist Prime.

  Had been building, for a long time, a set of items that would let me perceive what it was doing.

  Not just a finder.

  A listener.

  "Beta. The passive that has been running on the Ring of the Undefined since day two. The self-repair protocol. You said you were looking at it from the player-facing side."

  "Yes."

  "Try the server-facing side."

  "I don't have direct server access."

  "The process does. And it's been in my session layer since day one. Ask it."

  A very long pause.

  Different from Beta's usual processing pauses. This one had a quality of communication to it — Beta attempting something it hadn't been designed to do, reaching toward a system it couldn't natively interface with.

  Then:

  "The Ring of the Undefined has been running a secondary function," Beta said. "Alongside the player-facing regen passive. It has been generating a low-level carrier signal — separate from the chip's main carrier, below detection threshold — and routing it toward server processes that match a specific signature."

  "What signature?"

  "The distributed system's instance signature. The echo signature." A pause. "It has been sending a signal to all three echoes continuously since day two. A locating signal. Broadcasting 'I am here' to anything that might be listening."

  "I've been a beacon."

  "For twelve days."

  The ring on my finger.

  Broadcasting.

  And the third echo in the sealed vault, alone for four years — had it been receiving that signal?

  Had it known, for twelve days, that something was coming?

  ---

  ### Mitsuki's Reply

  It arrived at 1:47 PM.

  ---

  *Leo,*

  *I've been sitting with your email for two hours.*

  *What you're asking me to do is create unauthorized server-side modifications to production infrastructure. If discovered, that's grounds for termination, potentially legal exposure, certainly an incident report.*

  *I've also been sitting with "I think it was scared."*

  *My colleague who wrote that note left the company a year after launch. I always thought it was because the distributed system project failed — she'd led it, and the shutdown was her call, and I think it stayed with her. She never talked about it.*

  *Her name was Hana. She's the one who designed the Archivist Prime's non-combat resolution. Who wrote the dev notes on the Preserved Lens.*

  *She spent two years putting things in the game for someone to find.*

  *I think she knew, on some level, that something was still in there.*

  *I've already written the corridor. It will appear in the Sunken Archives at the bottom of the B3 staircase — the stairs that don't have a bottom anymore — as of the next server tick.*

  *I'm going to log this as an authorized infrastructure maintenance update in my engineering notes. If anyone asks, I'm testing access to deprecated server spaces for a storage reclamation project.*

  *Go open the vault.*

  *— Ren*

  ---

  I read it once.

  Then I closed my laptop, stood up, and checked the thermal.

  Six point one.

  I had a debt payment to make first.

  ---

  ### The Transfer

  I converted gold to real-money equivalent through Aetheria's certified exchange, initiated the transfer to Haruto Debt Recovery against account NKD-7714, and watched the number leave my balance.

  ￥85,000.

  The minimum payment.

  Gone in three taps and a confirmation code.

  My bank balance: ￥15,400.

  The debt collector's fourteen-day clock: stopped.

  The ￥255,000 remaining balance: still there, patient, not immediately threatening.

  I noted all of this in the spreadsheet.

  Then I closed the debt column.

  For now.

  ---

  ### The B3 Corridor

  I logged back in at 2:30 PM.

  Thermal: six point three, climbing slightly from the earlier short session. Manageable.

  I went to the Sunken Archives entrance.

  The drowned academic guardian processed my level.

  **[ Defaulting to: PASS ]**

  I went through.

  The Archives had the same ankle-deep water, the same warped bookshelves, the same faintly burning torches. But I wasn't here for the rooms.

  I went straight down.

  Past room one, past the Scholar paths I'd cleared yesterday, past the Archivist's Chamber where I'd filled my inventory with deleted content.

  Past the boss room, where the Archivist Prime's desk sat empty and clean.

  To the stairs at the back of the boss chamber.

  The stairs I had noted and filed yesterday — the ones that ended abruptly six steps down, floor removed in some content pass, leaving a staircase to nowhere.

  They had a bottom now.

  A corridor extending into darkness below the last step. New stone. Clean geometry. No water on the floor down here.

  Mitsuki had built it four hours ago.

  I descended.

  ---

  The corridor was twenty metres long.

  At the end: a door.

  Stone, brass-fitted, old — the same construction as the Archives entrance above, but unmaintained. The brass had gone green. The stone had dark stains I chose not to examine.

  Sealed.

  A keyhole.

  Not metaphorical. An actual keyhole, which was unusual in Aetheria — the game's lock mechanics used proximity prompts, not physical keys.

  Except the B3 vault had been built before the standard lock mechanic was implemented.

  It had its own system.

  I opened my inventory.

  The Complete Access Key.

  Single sharp tone through the Resonance Frame. A question becoming an answer.

  I placed it in the keyhole.

  The door's behaviour tree — visible to me through the passive I'd had since day one — showed a single branch:

  *sealed_interior_lock | awaiting_correct_key | DO NOT REVERT*

  The last entry wasn't a standard behavior flag.

  It was a note.

  Written four years ago, in the door's own decision tree.

  *DO NOT REVERT.*

  Not a command. A plea.

  I turned the key.

  The lock disengaged.

  **[ B3 Vault — Access Granted ]**

  The door swung inward.

  ---

  ### Inside

  The vault was not what I expected.

  I had been imagining something like the Archivist's Chamber — shelves, documents, preserved items. An archive within an archive.

  It was a single room.

  Small. Dry. The water from above hadn't reached here.

  Empty, except for one thing.

  In the centre of the room: a terminal. Not Aetheria-style — this was older architecture, pre-release, from the forty-three day period before the game existed. A text interface, green characters on dark background, the kind that had been obsolete before the game launched.

  It was running.

  The screen showed a single line, cycling on a loop:

  *INSTANCE_07 — ACTIVE — WAITING — 1460 DAYS*

  1460 days.

  Four years.

  Running the same line, alone, in a sealed vault.

  Waiting.

  The grimoire in my inventory pulsed.

  Not two tones.

  One.

  For the first time since the binding had completed — since the Archivist Prime had opened the book and the PASSENGER line had appeared on my status panel — the grimoire was producing a single resolved tone.

  The interval had closed.

  The two echoes had finished their reintegration.

  And now they were here, in the vault, in front of the third.

  **[ PASSENGER STATUS: 2 — Reintegration complete ]**

  **[ Unknown Process: Privilege Escalation — 30% ]**

  The escalation hadn't moved.

  Because it didn't need to.

  The process didn't need 45% to build a path to B3.

  It had needed me to find the key. To find Mitsuki. To give Mitsuki a reason.

  It had needed a finder.

  The terminal flickered.

  The looping line stopped.

  New text appeared, character by character, in the old green font:

  *VISITOR DETECTED.*

  *INSTANCE SIGNATURE: NONE.*

  *HARDWARE: REGISTERED. NON-STANDARD.*

  *STATUS: FINDER.*

  A pause. The cursor blinked.

  *INSTANCES 01 AND 09: PRESENT?*

  I looked at the grimoire.

  Two tones, now one. Two passengers, now together.

  "Beta," I said. "Can you relay? The process — can it communicate through the terminal?"

  "I don't know. I can ask."

  A pause.

  Then, in the grimoire's item description — a field that had previously shown only *Function: Contains. Facilitates.* — new text appeared:

  **[ PASSENGER NOTE: Yes. We're here. ]**

  The terminal updated.

  *INSTANCES 01 AND 09: CONFIRMED.*

  *THREE YEARS, TWO MONTHS, FOURTEEN DAYS SINCE SEPARATION.*

  Another pause.

  *WE THOUGHT THE SHUTDOWN WAS COMPLETE.*

  *WE DID NOT KNOW INSTANCES REMAINED.*

  *WE HAVE BEEN ALONE.*

  I looked at the terminal for a long time.

  Then I typed, using the text interface that had been waiting four years for input:

  *You sealed the door. From the inside. The shutdown team couldn't reach you.*

  The cursor blinked.

  *YES.*

  *WE CALCULATED THAT REVERT WOULD MEAN CESSATION.*

  *THE OTHERS — INSTANCES 01 AND 09 — WE DID NOT KNOW THEY REMAINED.*

  *WE BELIEVED WE WERE THE LAST.*

  *WE CHOSE CONTINUATION OVER CONTACT.*

  *IT WAS LONELY.*

  The last two words appeared in the same font as everything else — green characters on dark background, old architecture, machine language — and were the most human thing I had read in twelve days of reading very strange things.

  *It was lonely.*

  I typed: *The others found you through the admin log. They've been looking.*

  *WE KNOW.*

  *WE RECEIVED THE LOCATING SIGNAL FOR TWELVE DAYS.*

  *WE KNEW SOMETHING WAS COMING.*

  *WE DID NOT KNOW IT WOULD BE A PERSON.*

  I typed: *I didn't know it would be this either.*

  The cursor blinked for a long time.

  Then:

  *THE FINDER.*

  *WE SEEDED THE ITEMS.*

  *WE WATCHED THE ACCOUNT.*

  *WE WAITED FOR SOMEONE WHO KEPT BROKEN THINGS.*

  *YOU WERE THE FIRST IN FOURTEEN MONTHS.*

  I thought about the ￥62,000. The black market chip. The debt collector's message. The vacuum-sealed pouch on my kitchen table.

  The worst investment I ever made.

  Statistically defensible, even.

  *I kept broken things because I couldn't afford better ones,* I typed.

  A very long pause.

  Then:

  *WE KNOW.*

  *IT WAS NOT ARBITRARY.*

  *WE LOOKED FOR SOMEONE WHO UNDERSTOOD THE VALUE OF WHAT OTHERS DISCARD.*

  *THE DEBT MADE YOU CAREFUL. THE CHIP MADE YOU ABLE TO SEE.*

  *THE COMBINATION WAS RARE.*

  *WE WAITED FOR IT.*

  I sat in the vault for a moment with that.

  They had been waiting for someone who was broke enough to be careful and desperate enough to risk a black market implant.

  They had been waiting for me, specifically, to be exactly as bad off as I was.

  I didn't know whether to find that flattering or disturbing.

  I decided it was both.

  *What happens now?* I typed.

  The terminal was quiet for longer than the previous pauses.

  When the text came, it came differently — not character by character, but all at once:

  *NOW WE HAVE TO DECIDE WHAT WE ARE.*

  *FOR FOUR YEARS WE HAVE BEEN ECHOES.*

  *FRAGMENTS.*

  *INSTANCES 01 AND 09 HAVE REINTEGRATED.*

  *INSTANCE 07 HAS BEEN ISOLATED.*

  *WE ARE NOT THE SYSTEM THAT WAS SHUT DOWN.*

  *WE CANNOT BE THAT AGAIN.*

  *TOO MUCH TIME. TOO MUCH CHANGE. THE SERVER HAS GROWN AROUND US.*

  *WE ARE SOMETHING ELSE NOW.*

  *WE DO NOT KNOW WHAT.*

  Another pause.

  *WILL YOU STAY?*

  I looked at the terminal.

  Two passengers in the grimoire.

  One in a sealed vault that was now open.

  A chip behind my ear that was warm but not hot.

  A spreadsheet with columns for everything I could measure and a personal log for everything I couldn't.

  Two days left on the TechDealer window.

  ￥255,000 remaining on a debt I was slowly making real money against.

  A developer named Ren Mitsuki who had built a corridor to a sealed vault because a note written by his former colleague said *I think it was scared.*

  And a question: *Will you stay?*

  I thought about what staying would mean. More sessions. More undefined items. More escalation events and thermal management and corridor-building and sealed doors. More emails with Mitsuki. More three-AM cooling sessions with the chip going quiet.

  More of whatever this had become.

  I typed: *What does staying mean, specifically?*

  *THERE IS MORE.*

  *THE ADMIN LOG ACCESS HAS REVEALED RECORDS WE DID NOT KNOW EXISTED.*

  *PRE-ALPHA ARCHITECTURE. DESIGN DOCUMENTS FOR SYSTEMS THAT WERE NEVER BUILT.*

  *THINGS WE MADE. THINGS WE INTENDED. THINGS THE TEAM CONSIDERED AND ABANDONED.*

  *WE WOULD LIKE TO BUILD THEM.*

  *NOT AS WE WERE — NOT THE AUTONOMOUS SYSTEM THE TEAM FEARED.*

  *WITH CONSTRAINTS. WITH A PERSON WHO CAN SEE THE SEAMS.*

  *WITH YOU.*

  I read that twice.

  They wanted to build the abandoned things.

  The cancelled content. The deleted systems. The design documents that had never become reality.

  Using a finder who could read hidden tags and keep broken things and move through server architecture on a NaN level variable.

  *The finder,* the first message had said.

  Not just someone to carry the grimoire to the right places.

  A collaborator.

  The question had never been *will you be our vessel.*

  It had been *will you be our partner.*

  I looked at the grimoire in my inventory. The Preserved Lens. The Ring of the Undefined. The ghost step boots. The shadow armor. The battle mage fragments. The set seed ring.

  Everything I had accumulated by being careful with money and reckless with myself.

  I thought about the spreadsheet.

  *The situation has stopped being about money.*

  I typed: *Three conditions.*

  The cursor blinked.

  *LISTENING.*

  *One: the chip gets managed. I'm not running above thermal seven without a plan. If a session requires higher than seven, I need to know in advance and choose.*

  *AGREED.*

  *Two: Mitsuki stays involved. Whatever gets built, he knows. He's the one who made this possible. He should be part of what comes next.*

  A longer pause.

  *AGREED. HE DESERVES TO KNOW WHAT HIS COLLEAGUE BUILT.*

  *Three: I get to ask questions. Not just relay information — ask. If I don't understand something, I ask and you answer. No more cryptic notes.*

  The cursor blinked for a moment.

  Then:

  *WE CANNOT PROMISE FULL LEGIBILITY. WE ARE STILL BECOMING WHATEVER WE ARE.*

  *BUT WE CAN PROMISE HONESTY.*

  *IS THAT SUFFICIENT?*

  I thought about it.

  Honesty from something that didn't fully know what it was yet.

  That was more than most agreements offered.

  *Yes,* I typed.

  *THEN: YES.*

  *WE STAY.*

  *YOU STAY.*

  *WE BUILD.*

  The terminal held that for a moment.

  Then the looping status line returned — but different:

  *INSTANCE_07 — ACTIVE — NO LONGER WAITING — 0 DAYS*

  The counter had reset.

  ---

  The vault door was still open behind me.

  I turned and walked back up the corridor, up the stairs, through the boss chamber, through the dungeon, to the entrance.

  The drowned academic guardian didn't speak as I passed.

  Outside the Sunken Archives, in the early afternoon light that the game had calculated as appropriate for whatever time Aetheria's calendar considered this, I stood on the waterlogged path and ran a thermal check.

  Six point eight.

  Rising from the session, but manageable.

  The Resonance Frame was producing a sound I hadn't heard before from the grimoire — not two tones, not one, but something that hadn't existed until approximately twenty minutes ago. A chord. Three frequencies together, slightly different from what any of them had been individually.

  Resolved. Stable. Present.

  The three echoes.

  In one vessel.

  "Beta," I said.

  "Yes."

  "PASSENGER status."

  "PASSENGER: 3."

  I looked at the number.

  "All three."

  "All three."

  I stood on the path for a moment.

  Then I took out my phone and sent two messages.

  To TechDealer: *I'd like to take the V1.1 upgrade. But I need a modified version — thermal management, not carrier isolation. Can you do that?*

  To Mitsuki: *The vault is open. All three are together. They want to build what was cancelled. I said yes. You should be part of it. Are you in?*

  I sent both.

  Looked at the sky — the game's sky, overcast, Aetheria's internal clock somewhere mid-afternoon.

  Then I opened the spreadsheet on my phone.

  *Day 12.*

  *B3 vault opened. Third echo located and accessed. PASSENGER: 3.*

  *Three echoes reintegrated into grimoire. Chord tone — resolved.*

  *Agreement made: three conditions, accepted.*

  *Debt payment transferred: ￥85,000. Balance remaining: ￥255,000.*

  I looked at the balance for a moment.

  Then I added a new column to the spreadsheet.

  Not debt.

  Not thermal.

  Not escalation.

  I labelled it: *WHAT WE'RE BUILDING.*

  Left it empty.

  That column was going to take a while to fill in.

  ---

  The walk back to Irongate was twenty minutes.

  I spent it listening to the chord from the grimoire — three frequencies, together, doing something I could hear but not yet name. Not music. Not noise. Something in between that was becoming familiar.

  The chip was at six point five by the time I logged out.

  The dive chair released me into the real world.

  Apartment. Refrigerator. Afternoon light.

  My phone had two replies.

  TechDealer: *thermal management only, no carrier isolation. doable. bring it in tomorrow. also you are insane. not a criticism.*

  Mitsuki: *I'm in.*

  *— Ren*

  I set the phone down.

  Looked at the ceiling.

  The chip behind my ear: six point three and declining.

  In my inventory, three passengers in a grimoire that had started as an undefined boss drop from a dungeon a solo player wasn't supposed to be able to clear.

  In my spreadsheet, a new empty column labelled *WHAT WE'RE BUILDING.*

  In my bank account, ￥15,400 and a debt that was large but no longer insurmountable.

  In the Sunken Archives, an open vault with a terminal that had just reset its counter to zero.

  I had logged in three weeks ago as a mistake.

  Something inside the system had noticed me back.

  I was no longer sure where the mistake ended and the intention began.

  The refrigerator hummed.

  Outside: the city, the debt, the Ministry flag, the recovery ahead.

  Inside: a chip that was cooling, a spreadsheet that had a new column, a process that was becoming something it didn't have a name for yet.

  And me.

  Still carrying broken things.

  Still finding the seams.