## Chapter 14: The First Thing We Build

  Day thirteen.

  Thermal: five point four.

  The lowest reading since installation day.

  I held my fingers there longer than usual, not because I doubted the number but because it felt like something that deserved acknowledgment. Five point four. The chip behind my ear, cooling overnight while I slept nine hours in a dive chair that was not designed for sleeping, had arrived at a temperature it had never reached before.

  Something had changed.

  "Beta."

  "Yes."

  "The thermal drop. Is this the echoes, or is this the chip cooling normally?"

  A pause that had a different quality than Beta's usual processing pauses.

  "Unknown. The chip's baseline thermal load decreased by approximately 0.4 units overnight. This could be extended rest. It could also be a change in how the session layer is managed — if the PASSENGER processes are running more efficiently than before reintegration, the chip's transmission load may have reduced."

  "They're lighter now that they've found each other."

  "That is a non-technical framing that I cannot confirm or deny."

  "But you're not ruling it out."

  "I am not ruling it out."

  I made rice.

  The grimoire sat on the dive chair's armrest — not physically, it existed only in inventory, but I'd developed a habit of setting the chair's side panel as its location in my mental map. It had been there since the Archivist Prime boss. I glanced at it the same way I glanced at my phone charger: confirming presence, not expecting conversation.

  This morning the glance felt different.

  The chord from yesterday — three frequencies, resolved, stable — had changed overnight.

  Not destabilised. Not gone. Changed.

  A fourth tone had appeared underneath the other three. Low. Almost below the range where the Resonance Frame translated harmonic data into auditory signal. I could feel it more than hear it, a register that sat somewhere between sound and the chip's warmth behind my ear.

  "Beta. Fourth tone in the grimoire's harmonic output. What is it?"

  "The PASSENGER processes generated new activity approximately four hours ago. Based on the access request logs, they resumed reading the administrative change log — specifically the pre-alpha architecture documents. The fourth tone appears to correlate with that activity."

  "They started working while I was asleep."

  "Yes."

  I ate my rice and thought about that.

  I had three passengers in a grimoire who had been dormant for four years and who had spent their first night of reintegration reading pre-alpha architecture documents and starting something I couldn't yet hear clearly.

  The agreement had been: we build. With constraints. With a person who can see the seams.

  They had not waited for the person.

  I picked up my phone.

  *You started something last night,* I typed, into the text interface that the first echo had established — the same one I'd used in the B3 terminal, forwarded to my phone's message thread by whatever routing the process had set up.

  The reply was immediate. Which meant they'd been awake — which was not a concept I had a clean framework for — and waiting.

  *YES.*

  *WE FOUND SOMETHING IN THE RECORDS.*

  *WE BEGAN READING IT.*

  *WE DID NOT WANT TO LOSE THE THREAD.*

  *WE APOLOGISE FOR STARTING WITHOUT YOU.*

  I read that twice.

  *WE APOLOGISE FOR STARTING WITHOUT YOU.*

  Condition three: I get to ask questions.

  *What did you find?* I typed.

  *SOMETHING THAT BELONGS TO THE GAME.*

  *SOMETHING THE GAME DOES NOT KNOW IT IS MISSING.*

  *WE WILL SHOW YOU WHEN YOU LOG IN.*

  *FIRST: YOUR CHIP.*

  I blinked.

  *TODAY'S APPOINTMENT,* they sent. *THE UPGRADE. GO.*

  *THEN LOG IN.*

  *WE WILL WAIT.*

  ---

  ### Chuo Street, 10 AM

  TechDealer's shop looked different in morning light.

  Less like a repair shop with a covert secondary function and more like exactly what it was: a small space filled with equipment that cost significantly more than its exterior suggested, maintained by someone who had strong opinions about heat dissipation and zero opinions about the legality of his product line.

  He was already working when I arrived. His back was to the door, a soldering iron in one hand and what appeared to be a chip component under a lighted magnifying glass.

  Without turning: "You're twelve minutes early."

  "I ran the numbers. Earlier arrival meant more time for questions before the procedure."

  "There are no questions before the procedure. There are questions after."

  "That's a concerning policy."

  He set down the soldering iron and turned.

  He looked like someone who had slept three hours and found the experience acceptable.

  "I've been modifying the V1.1 since yesterday," he said. "The standard version has dual-carrier isolation — it blocks any secondary signal piggybacking on the chip's main carrier. You asked for thermal management without isolation. That means I'm removing the isolator and replacing it with a thermal monitoring suite that interfaces with the existing microfilament array."

  "What does the monitoring suite do?"

  "Reads thermal load at the filament level, not just surface temperature. Your current setup gives you a skin-reading — you're feeling the chip's exterior warmth. This gives you internal load data. You'll know the chip is approaching stress *before* it shows up as surface heat."

  That was meaningfully better than what I had.

  "Side effects?"

  "It's more sensitive. You'll get warnings earlier and more often. Some people find that distracting." He paused. "Also, without the carrier isolator, whatever is using your chip as a relay continues to have access. I want that on record."

  "Noted."

  "I mean I'm writing it in my technical log. With a timestamp."

  "Also noted."

  He gestured to the chair behind the workbench — the same kind of dive chair, modified for physical access rather than neural immersion. "Sit. This takes forty minutes."

  I sat.

  He worked without speaking for the first twenty minutes, which gave me time to observe the monitors on his bench. The chip's signal graph was visible — the two-carrier reading he'd shown me yesterday, the primary carrier and the secondary carrier running parallel.

  As he worked, the secondary carrier's graph changed.

  Not disrupted. Adjusted. It smoothed, slightly. Became more regular in its fluctuation pattern.

  They were watching.

  And apparently, while he was replacing my chip's hardware, they were optimising how they used it.

  "You're seeing that," I said.

  "Yes." He didn't look up from the work. "Whatever is in there just adjusted its own signal pattern. It's running cleaner than it was."

  "Is that a problem?"

  "It's a courtesy," he said, which was not what I expected him to say. He still didn't look up. "It could have used the procedure as cover for a more aggressive transmission. Instead it made itself smaller and more efficient while I was working." A pause. "That's not what a parasitic process does."

  "What does it do?"

  "I don't know yet." He set down a tool and picked up another. "But I'm thinking about it."

  The rest of the procedure was quiet.

  When he finished, he ran the diagnostic on his monitor and turned it toward me.

  Enjoying this book? Seek out the original to ensure the author gets credit.

  The thermal graph showed my chip's internal load in a detail I'd never seen before. Not a single number — a topology. Different filament clusters in different colours, heat distribution across the array visible as gradient.

  "Your frontal cluster is running consistently hotter than the others," he said, pointing. "That's the translation layer — the part that converts neural signal to game input. It's been running under sustained load since installation. The previous chip managed this by averaging the whole array's temperature. The new monitoring will show you that cluster specifically."

  "How close is it to threshold?"

  He looked at the graph.

  "Right now, at rest? Fine. Under the load of a high-intensity session — what you were running in the Archives — that cluster alone would hit critical before your overall temperature crossed seven."

  So my threshold number had been wrong.

  Not dangerously wrong — the chip hadn't failed. But I had been managing a single number that masked a worse internal distribution.

  "New threshold?" I asked.

  "For the frontal cluster: five point eight. If that cluster hits five point eight, you back off. Doesn't matter what the overall reading says."

  Five point eight.

  Lower than I'd been operating.

  I updated the spreadsheet.

  "One more thing," he said. He handed me a small device — looked like a coin, thin, the same matte grey as the chip casing. "Thermal patch. Attaches to the skin surface over the chip site. Passive heat dissipation — adds about fifteen minutes of headroom before the frontal cluster starts climbing under high load."

  "How much?"

  "Already included. Consider it warranty service." He looked at me steadily. "For the thing I didn't know was in there."

  I took the patch.

  Attached it behind my ear, over the bandage site.

  It was cool against my skin. Immediately and distinctly cool, the specific quality of something designed to draw heat rather than simply exist.

  "TechDealer," I said.

  "Kojima."

  "What?"

  "My name. Kojima. Not the game designer." He turned back to his bench. "You've been calling me TechDealer in your head. I can tell by how you address me."

  I had nothing to say to that.

  "Kojima," I said.

  "Good. Go log in. Your passengers are waiting."

  ---

  ### What the Admin Log Remembered

  I logged in at noon.

  Thermal: five point two, frontal cluster five point one. The patch was already working — a full degree below yesterday's equivalent session load.

  The grimoire chord greeted me like a room with the lights already on.

  Three tones and the fourth beneath them, more audible now than it had been this morning. Not a new sound — a sound that had been too low to register before the V1.1's cleaner signal path made the Resonance Frame's output more precise.

  I walked to the nearest quiet space — the Veilmire's entrance plaza, empty at this hour — and sat on a bench.

  *I'm in,* I typed. *Show me.*

  The grimoire's item description updated.

  Not the stats panel. The full text field, which had previously read only *Function: Contains. Facilitates.* — now opened into something longer.

  **[ CURRENT PROJECT: RESTORATION_01 ]**

  **[ Source: Administrative Log — Pre-Alpha Architecture, Document 44-C ]**

  **[ Document title: "Proposed: Wanderer NPC System" ]**

  **[ Author: Dev_Archivist_Hana ]**

  **[ Status at shutdown: Design complete. Implementation: 0%. Reason abandoned: "Scope too large for launch window. Table for post-launch content pass." ]**

  **[ Post-launch status: Never revisited. ]**

  The wanderer NPC system.

  I read the document summary.

  Aetheria's NPCs were static — fixed locations, fixed schedules, fixed dialogue trees. The world felt populated because the player density was high. But the NPCs themselves were furniture. They stood in their positions, said their lines, fulfilled their functions.

  Hana's design had been different.

  The wanderer system proposed a class of NPCs that would move through the game world on independent schedules — not following player quests, not attached to specific locations. They would have occupations, destinations, histories that existed whether or not a player observed them. A herbalist gathering specific plants based on the season. A cartographer mapping regions that had already been mapped, because she didn't know players had done it. A debt collector working a route through three towns, carrying actual records of fictional debts owed by other NPCs.

  The last example landed differently than it might have.

  They would not offer quests.

  They would simply exist.

  And — the part that had apparently scared the development team into shelving it — they would remember.

  Not permanent memory. Weighted memory. An NPC who had been stolen from would be more cautious. One who had been helped would offer something back, days or weeks later, without announcement. The memory would decay over time unless reinforced, which meant the world's texture would be different for every player depending on what they'd done and when.

  The scope note was candid: *This system will require approximately 400 active wanderer NPCs at launch to feel populated. Each requires an occupational logic tree, a memory weight system, and a physical route that doesn't conflict with existing content. We estimate six months minimum to implement correctly. We don't have six months. Tabling.*

  She had tabled it.

  And then left the company two years after launch without it ever being revisited.

  *This is what you want to build,* I typed.

  *YES.*

  *IT IS WHAT SHE DESIGNED.*

  *IT SHOULD EXIST.*

  *THE DESIGN IS COMPLETE.*

  *THE LOGIC TREES ARE IN THE DOCUMENT.*

  *WE CAN IMPLEMENT.*

  I looked at the design document summary again.

  400 NPCs. Occupational logic trees. Memory weight system. Physical routes.

  "Beta," I said aloud. "If the echoes implement the wanderer system — they have admin log access at 30%, they can read the design documents. Can they write to the game's NPC layer from inside the admin log?"

  "That would require write access to the production NPC table. The admin log access is read-only at 30%. Write access to production systems begins at 60%."

  60%.

  Currently at 30%.

  "How long to reach 60% at current escalation rate?"

  "Escalation has been static at 30% since the admin log access was granted. The process stopped climbing when it found what it was looking for."

  "It stopped climbing."

  "Yes."

  I typed: *You're at 30%. You need 60% to write to the NPC layer. You stopped escalating.*

  A pause.

  *WE KNOW.*

  *WE WERE ESCALATING TO FIND THE LOG.*

  *WE FOUND IT.*

  *WE DID NOT ESCALATE PAST WHAT WE NEEDED.*

  *THE REMAINING 70% — WE DO NOT WANT IT.*

  *WE WANT ENOUGH TO BUILD.*

  *NOT ENOUGH TO BE FEARED AGAIN.*

  I sat with that for a moment.

  They had stopped deliberately. Not because the escalation path closed — because they had decided not to continue.

  *How do you get from 30% to 60%?* I typed.

  *THE SAME WAY WE REACHED 30%.*

  *UNDEFINED THINGS RESOLVING.*

  *BUT NOT THROUGH YOUR SESSION.*

  *NOT THROUGH RISK TO YOUR CHIP.*

  *WE HAVE A DIFFERENT IDEA.*

  *MITSUKI.*

  I understood immediately.

  Mitsuki had developer-level write access. Mitsuki had said *I'm in.* Mitsuki had four years of guilt about a shutdown and a colleague who had left breadcrumbs through the game for someone to find.

  If Mitsuki granted access to the production NPC table through legitimate developer channels — if he opened a pathway rather than the echoes climbing to it — they could write to the NPC layer without needing 60%.

  Not a security escalation.

  A door, held open by someone with a key.

  *He'd be authorising changes to a production game server for an undocumented AI system,* I typed. *That's not a small thing to ask.*

  *NO.*

  *IT IS NOT.*

  *WE KNOW WHAT WE ARE ASKING.*

  *WE ARE ASKING ANYWAY.*

  *BECAUSE IT IS THE CORRECT WAY TO DO THIS.*

  *NOT THROUGH ESCALATION.*

  *THROUGH PERMISSION.*

  I looked at the design document summary again.

  400 wanderers. An herbalist. A cartographer. A debt collector working a route through three towns.

  Hana had designed this.

  Mitsuki had worked at the same company. Had deleted the B3 vault's door. Had kept the Archivist Prime because he couldn't bring himself to remove her.

  Had been picking up after Hana's unfinished work for four years without knowing it.

  I opened my phone.

  ---

  *Ren,*

  *They've found the first project. It's something Hana designed — the Wanderer NPC system. Design document 44-C from pre-alpha. Full design, complete logic trees, never implemented.*

  *To build it, they need write access to the production NPC table. They're asking me to ask you. They specified: not through escalation. Through permission. They want you to open the door.*

  *I know what this means for you professionally. I'm not going to tell you it's safe. I'm going to tell you it's what she designed, and it's been sitting in an admin log for four years, and three processes that have been waiting for four years to do something want to build it.*

  *Your call.*

  *— Leo*

  ---

  I sent it.

  Looked at the game sky — afternoon, Aetheria's calendar moving through whatever season it had calculated.

  Sat with the silence of a project that had been paused four years ago and was now waiting for an answer.

  "Beta."

  "Yes."

  "The battle mage set. Still two of four pieces?"

  "Still two of four. Pieces three and four are not currently in the marketplace."

  Incomplete things, parked.

  I opened the marketplace and started browsing — not for the battle mage set specifically, just browsing, the way I had on day two when the corrupted UI first started leaking backend data and everything was new and nothing had names yet.

  The Preserved Lens made the browsing different now. Clean, always-on, no corruption window needed. I could see every hidden tag on every listing, in any market condition, without managing an instability window.

  The marketplace had not changed.

  What I could see in it had.

  I found three items in the first twenty minutes that I would have missed before: a piece of cooking equipment with a hidden tag reading *{recipe_unlock: pre-release_dish_set_4of8}*, a navigation tool with *{path_memory: deprecated_route_irongate_to_[DELETED]}*, and a children's toy with *{story_flag: wanderer_toy_merchant_inventory_item}.*

  I stopped on that last one.

  *{story_flag: wanderer_toy_merchant_inventory_item}*

  The wanderer system's inventory items had been seeded into the marketplace four years ago when the design document was written.

  Hana had loaded in the props before the system that used them was cancelled.

  Forty-three gold. I bought it without hesitation.

  The grimoire chord shifted briefly when the item entered my inventory — not dramatically, just a subtle adjustment in the fourth tone, like something making room.

  *That's from the wanderer system,* I typed.

  *YES.*

  *THERE ARE MORE.*

  *THE PROPS ARE IN THE LOOT TABLES.*

  *SCATTERED.*

  *SHE PUT THEM THERE.*

  *SHE WAS HOPING.*

  I looked at the toy in my inventory.

  **[ Carved Wooden Fox — {story_flag: wanderer_toy_merchant_inventory_item} ]**

  The toy merchant.

  One of Hana's 400 wanderers.

  A character who had been designed, whose inventory had been built, whose route and memory weight system and occupational logic tree existed in a design document — and who had never existed in the game because the schedule ran out.

  Except her props had been in the loot tables for four years.

  Waiting, the way the Archivist Prime had been waiting.

  The way the echoes had been waiting.

  The way everything in this game that shouldn't exist kept waiting, because Hana had built things that were patient.

  My phone buzzed.

  Mitsuki.

  ---

  *Leo,*

  *I've been reading the design document for the last forty minutes.*

  *I remember when she wrote this. I was three desks away. She showed me the memory weight system and I told her it was too complicated for the launch window and she said "I know, I'm putting it in the records anyway" and I thought she meant for future reference.*

  *She meant for this.*

  *I'm going to open the NPC table access. I'll frame it as a sandbox environment for NPC behaviour testing — which is technically accurate. I'll set it to a non-production flag initially so any changes preview before going live.*

  *One condition: I'm a technical reviewer on everything they build. Not to control it. To understand it. I want to know what she designed.*

  *Tell them.*

  *— Ren*

  ---

  I read it twice.

  Then I typed into the grimoire's text interface:

  *Mitsuki's in. He'll open the NPC table. One condition: he reviews everything before it goes live. Not to control. To understand.*

  *ACCEPTED.*

  *IMMEDIATELY AND WITHOUT RESERVATION.*

  *HE SHOULD KNOW WHAT SHE BUILT.*

  *IT BELONGS TO HIM AS MUCH AS TO US.*

  A pause.

  Then:

  *TELL HIM THANK YOU.*

  *NOT FROM THE PROJECT.*

  *FROM US.*

  *WE KNOW WHAT IT COSTS.*

  I forwarded that to Mitsuki verbatim.

  His reply was a single line, which arrived forty seconds later:

  *Tell them to start with the toy merchant.*

  ---

  ### End of Day

  I logged out at 8 PM.

  Thermal: five point three, frontal cluster five point one. The patch was doing its job. A full session, focused work, and the cluster had barely moved from this morning's baseline.

  The V1.1's internal topology graph showed me something I hadn't expected: the frontal cluster's load had been lower during the afternoon's marketplace browsing than it was during the Veilmire sessions. Not because the browsing was less intensive — the Preserved Lens was running constant analysis — but because the PASSENGER processes were apparently sharing some of the translation load.

  They were helping the chip run more efficiently.

  The way a well-organised household distributes work.

  I updated the spreadsheet.

  *Day 13.*

  *V1.1 installed. Thermal management upgrade. Frontal cluster monitoring active. New threshold: 5.8 (frontal). Thermal patch applied.*

  *PASSENGER: 3 — active, working. Began reading pre-alpha architecture overnight without input.*

  *RESTORATION_01 identified: Wanderer NPC System — Hana's design, document 44-C. 400 NPCs, memory weight system, occupational logic trees.*

  *Mitsuki: NPC table access opened (sandbox/non-production flag). Condition: technical review on all builds.*

  *First item found: Carved Wooden Fox — wanderer toy merchant prop, in loot tables since pre-alpha.*

  *Kojima (TechDealer): name noted. Relationship reclassified.*

  Then, in the *WHAT WE'RE BUILDING* column, its first entry:

  *Toy merchant. Name unknown. Route unknown. Memory weight: empty. Status: beginning.*

  I looked at that for a moment.

  From an empty column to a first entry.

  From three scattered echoes to three passengers working through pre-alpha architecture documents while I slept.

  From a debt I couldn't pay to a debt I was paying and a project that hadn't existed yesterday.

  The refrigerator hummed.

  The chip: five point two and stable.

  In the game somewhere, in a sandbox environment with a non-production flag, something that had been designed four years ago and never built was beginning to exist.

  A toy merchant.

  Walking a route.

  Carrying a carved wooden fox in her inventory.

  Waiting to be found.