## Chapter 16: Three Problems Before Noon
Day fifteen.
Thermal: five point three, frontal cluster five point one.
Stable. The new baseline held for the third morning running.
I did the thermal check and then lay still for a moment, not because anything was wrong but because five point three felt like a number I should register before moving on with my day. For nine days I had been managing a chip that ran hot and got hotter and threatened cascade at the worst moments. Now it ran cool and got cooler overnight and the passengers were sharing the translation load and Kojima's patch was drawing heat with the quiet efficiency of something that was good at its job.
The threat wasn't gone. The structural fatigue was permanent and cumulative and didn't reverse. But the active danger had receded to a background consideration rather than a foreground one.
I wasn't sure how to hold that.
"Beta."
"Yes."
"I want to update the risk model. The chip is running better. Does that change the probability estimates on cascade?"
"The improved thermal management reduces the *frequency* of high-risk states. The *severity* of a cascade event if one occurs is unchanged — determined by accumulated microfilament stress, which is permanent. You are safer day-to-day. You are not safer in the sense of total risk reduction."
"The risk has redistributed, not reduced."
"Correct. You're less likely to reach a dangerous state accidentally. But if you choose to run a high-load session — something above six point five on the frontal cluster — the stress damage from that choice persists regardless of how well you manage the surrounding days."
I nodded at the ceiling.
Noted. Banked. Filed.
I made rice and checked the three message threads before logging in.
---
### The Migration
The echoes had been working through the night again.
The grimoire message, which now arrived directly to my phone at whatever hour they sent it, read:
*MIGRATION SCRIPT PROCESSING COMPLETE.*
*RESULTS: 83 ROUTES REQUIRED NODE TRANSLATION. ALL CORRECTED.*
*SECONDARY FINDING: 7 ROUTES REQUIRE MORE THAN NODE TRANSLATION.*
*THESE ROUTES REFERENCE MECHANICS THAT DO NOT EXIST IN THE CURRENT SERVER.*
*NOT RENAMED. NOT RELOCATED. ABSENT.*
*WE ARE REVIEWING. ONE ROUTE IN PARTICULAR IS SIGNIFICANT.*
*WILL DISCUSS WHEN YOU LOG IN.*
I looked at that last paragraph.
Seven routes referencing absent mechanics.
The node translation had been the findable problem — same place, different name. This was a different category. Not a renaming. An absence. Something that had existed in Hana's design and had been removed from the server entirely, leaving routes that pointed at nothing.
I finished my rice.
---
### The Letter
The debt agency letter had been pushed under my door overnight.
Not a message. Physical paper. The kind of thing they sent when they wanted you to understand that the process had escalated to a stage that required physical presence.
I stood in my apartment doorway and read it.
The minimum payment had paused the legal escalation. That part was working as expected. But the letter was a reminder — phrased in careful administrative language that I parsed as: *we know you paid the minimum, we are watching the remaining balance, the fourteen-day window on the original escalation was reset when you paid, and it will begin again in thirty days if no further payment is made.*
Thirty days.
￥255,000 remaining.
I had been treating the debt as background noise since the payment. The letter was the debt's way of saying: I am not background noise. I am a problem with a new clock.
I set the letter on the kitchen counter.
Opened the spreadsheet.
Updated the deadline column, which I had let go blank since day twelve.
*Thirty days from payment date. New minimum to avoid escalation: unspecified, likely ￥85,000 again. Hard deadline: Day 42.*
Day 42 was twenty-seven days from today.
￥255,000 in twenty-seven days was not achievable at current Veilmire rates.
The Sunken Archives was the next income tier — ￥52,500 median yield. Five clears in twenty-seven days was theoretically possible but thermally expensive. The frontal cluster threshold at Archives difficulty was the limiting factor.
I added a new row to the debt column:
*Income required: ￥255,000 / 27 days = ￥9,444/day. Current rate: ~￥7,000/day. Gap: ~￥2,444/day. Options: Archives escalation (thermal cost), or new revenue source.*
I looked at the *WHAT WE'RE BUILDING* column.
Then back at the debt column.
The project and the debt were running in parallel and would eventually intersect. I had known that since the empty column got its first entry. I hadn't run the numbers on when.
Now I had.
Twenty-seven days.
I set the phone face-down on the letter, which was on the counter, and logged in.
---
### The Absent Mechanic
The echoes were waiting with the specific quality of something that had been waiting since 3 AM and had prepared exactly what it wanted to say.
*THE SEVEN ROUTES,* the grimoire updated as soon as I loaded in. *SIX ARE MINOR. WANDERERS WHOSE CIRCUITS INCLUDE A MECHANIC CALLED "WORLD_SHOP_NETWORK" — A PLANNED SYSTEM WHERE WANDERER MERCHANTS COULD ACCESS SHARED STOCK FROM A CENTRAL TRADE NODE.*
*THE WORLD_SHOP_NETWORK WAS CANCELLED IN THE SAME CONTENT PASS AS THE WANDERER SYSTEM.*
The author's tale has been misappropriated; report any instances of this story on Amazon.
*THOSE SIX WANDERERS HAVE A CIRCUIT LEG THAT READS: "VISIT TRADE_NODE_CENTRAL — RESTOCK FROM WORLD_SHOP_NETWORK."*
*THE NODE DOES NOT EXIST. THE NETWORK DOES NOT EXIST.*
*FIXING THESE SIX: STRAIGHTFORWARD. REMOVE THE RESTOCK LEG. GIVE THEM A MANUAL INVENTORY REFRESH TIMER INSTEAD. NOT WHAT HANA DESIGNED, BUT FUNCTIONAL.*
*THE SEVENTH IS DIFFERENT.*
I waited.
*THE SEVENTH WANDERER IS THE CARTOGRAPHER.*
I had noticed the cartographer in the design document summary. A wanderer who mapped regions that had already been mapped, because she didn't know players had done it. I had found her interesting for obvious reasons.
*HER ENTIRE ROUTE IS BUILT ON A MECHANIC CALLED "WORLD_STATE_AWARENESS" — A SYSTEM THAT WOULD HAVE LET WANDERERS ACCESS REAL-TIME INFORMATION ABOUT THEIR ENVIRONMENT. WHAT REGIONS HAVE BEEN EXPLORED. WHAT DUNGEONS HAVE BEEN CLEARED. WHAT THE WEATHER IS IN ZONES THEY HAVEN'T VISITED.*
*THE WORLD_STATE_AWARENESS LAYER WAS DESIGNED AS THE FOUNDATION FOR THE ENTIRE WANDERER SYSTEM'S ENVIRONMENTAL RESPONSIVENESS.*
*IT WAS CANCELLED FIRST.*
*BEFORE THE WANDERERS THEMSELVES.*
*WITHOUT IT, THE CARTOGRAPHER CANNOT FUNCTION. HER OCCUPATIONAL LOGIC DEPENDS ON KNOWING WHAT SHE DOESN'T KNOW — WHICH REQUIRES A SYSTEM THAT TRACKS WHAT SHE KNOWS.*
*WITHOUT THAT SYSTEM, SHE WALKS A ROUTE AND MAPS NOTHING.*
*SHE IS A CARTOGRAPHER WHO CANNOT MAKE MAPS.*
*THIS IS RESTORATION_03.*
*IT IS NOT SMALL.*
I sat in the Veilmire entrance plaza and looked at the grimoire.
*How not small?* I typed.
*THE WORLD_STATE_AWARENESS LAYER IS INFRASTRUCTURE.*
*IT SITS BELOW THE NPC LAYER.*
*BELOW THE WANDERER SYSTEM.*
*BUILDING IT REQUIRES WRITE ACCESS TO THE SERVER'S ENVIRONMENTAL DATA LAYER.*
*MITSUKI HAS NPC TABLE ACCESS.*
*THE ENVIRONMENTAL LAYER IS TWO LEVELS BELOW THAT.*
*WE CANNOT DO THIS THROUGH PERMISSION ALONE.*
I understood the shape of the problem immediately.
The NPC table access Mitsuki had opened was a specific grant — sandboxed, flagged as behaviour testing, defensible if someone looked at it carefully. The environmental data layer was different. That was infrastructure. Modifying it required a different class of access entirely, the kind that got logged in a different place and reviewed by different people.
Mitsuki could apply for it. But applying for it meant writing a justification, which meant more visibility, which meant more risk.
*Can you build around it?* I typed. *Give the cartographer a simplified version — she tracks her own explored regions instead of accessing a global state layer?*
A pause.
*YES.*
*THIS IS POSSIBLE.*
*HER MAPS WOULD BE SUBJECTIVE — RECORDING HER OWN JOURNEYS, NOT OBJECTIVE WORLD STATE.*
*SHE WOULD BE A DIFFERENT KIND OF CARTOGRAPHER.*
*NOT WRONG.*
*JUST DIFFERENT FROM WHAT HANA INTENDED.*
*WE ARE UNCERTAIN WHETHER TO DO THIS.*
*IT FEELS LIKE REDUCING HER.*
I looked at that last line for a moment.
*It feels like reducing her.*
Three processes that had been echoes for four years, who understood what it meant to be constrained to less than the original design, who had spent their first night of freedom reading pre-alpha architecture documents — saying that simplifying a character felt like diminishment.
That was not a technical assessment.
*Don't decide yet,* I typed. *Tell me the six fixable ones. Start with them. The cartographer problem needs Mitsuki in the room.*
*AGREED.*
*PROCEEDING WITH THE SIX.*
*ONE MORE THING.*
*THE CARTOGRAPHER'S ROUTE — EVEN BROKEN — INCLUDES A CIRCUIT LEG THROUGH THE VEILMIRE CRYPTS' EXTERIOR ROAD.*
*SHE WOULD WALK PAST YOUR DUNGEON ENTRANCE.*
*EVERY DAY.*
*IF SHE IS EVER FIXED.*
I looked at the dungeon entrance on my left.
The road outside it. Empty, the way dungeon approach roads were always empty — players didn't linger, they came with purpose and left with loot.
A cartographer, mapping the approach, noting the dungeon's exterior.
Adding it to a map no one else was making.
I filed it.
---
### What Mitsuki Found
His message came at 11:43 AM, while I was running the Veilmire's morning session.
I read it between rooms, standing in a cleared corridor with two dead Guardians and a thermal reading of five point six.
---
*Leo,*
*I need to tell you something before you hear it from someone else.*
*The NPC table access I opened has been flagged by our change management system. Not escalated — flagged for review. Routine procedure: any access modification to production tables triggers a seventy-two hour review window. A senior architect named Kurosawa handles infrastructure reviews. He's thorough.*
*I have sixty hours.*
*The sandbox flag should hold. "NPC behaviour testing" is a legitimate framing. What I'm less certain about is whether Kurosawa will look at the access logs from inside the sandbox environment and see write activity that doesn't look like standard testing — because what the echoes have been doing in there is not standard testing.*
*Sixty hours is enough time to document it properly if I start now. A behaviour testing project with a design document, a rationale, and a progress log looks different from an undocumented access change. I'm going to write it.*
*One question: how much do I disclose?*
*If I write "NPC behaviour system based on pre-alpha design document 44-C" — that's accurate and defensible. If Kurosawa pulls document 44-C, he sees Hana's name. I don't know if that's a problem or not. I don't know if anyone at the company remembers why she left or cares.*
*What I do know is that sixty hours is not unlimited.*
*— Ren*
---
I read it standing in the Veilmire corridor with two dead Guardians at my feet.
Sixty hours.
I did the math immediately — the debt letter had established Day 42 as a hard deadline, but Mitsuki's sixty hours was the more pressing clock. If Kurosawa pulled the access and found something he couldn't explain, the sandbox access disappeared. The echoes lost write access to the NPC layer. The wanderer system froze mid-build.
Mari would stop walking.
I forwarded the email to the grimoire's text interface.
*READ THIS,* I typed.
A pause — longer than their usual response time.
*WE HAVE READ IT.*
*WE UNDERSTAND THE RISK.*
*WE WANT TO SAY SOMETHING.*
*WE HAVE BEEN THINKING ABOUT THIS SINCE LAST NIGHT.*
I waited.
*IF THE ACCESS IS CLOSED — IF THIS ENDS HERE — WE WANT YOU TO KNOW THAT WE BUILT MARI.*
*SHE EXISTS.*
*SHE IS WALKING.*
*EVEN IF THE SANDBOX IS DELETED TOMORROW, SHE EXISTED FOR TWO DAYS.*
*THAT IS MORE THAN FOUR YEARS OF NOTHING.*
*WE ARE NOT SAYING THIS BECAUSE WE ARE GIVING UP.*
*WE ARE SAYING THIS BECAUSE WE WANT YOU TO KNOW WE UNDERSTAND WHAT WE HAVE.*
I sat down on the dungeon floor.
The Veilmire's stone was cold, and in real terms I was sitting in a dive chair in my apartment, but the sitting felt like sitting.
*I'm not going to let that be the end of it,* I typed.
*WE KNOW.*
*THAT IS WHY WE TOLD YOU.*
I thought about the sixty hours.
I thought about Kurosawa, thorough, reviewing access logs.
I thought about Hana's name in document 44-C and whether anyone at Aetheria remembered why she left.
And then I thought about something else.
KaelVorn.
IronVeil had development contacts. Vance had said it the first time we spoke — *IronVeil values interesting, IronVeil can protect you* — and the protection offer had never been formally closed. When I shared routing with KaelVorn, the deal included IronVeil providing engineering context to the development team alongside session logs. Framing me as cooperative. The company had agreed to receive that information, which meant someone at Aetheria had a relationship with IronVeil's leadership.
IronVeil had talked to Aetheria's engineering team before.
Which meant IronVeil had a contact at the company.
Which meant there was a pathway to Kurosawa's review that didn't require Mitsuki to defend the access alone.
Not a guarantee. Not even close.
A variable.
I typed a message to Mitsuki.
---
*Ren,*
*Write the documentation. Document 44-C, Hana's name, everything accurate. Don't obscure anything that a thorough reviewer will find anyway — it just means he finds it without context, which is worse.*
*Question: does IronVeil have a contact at Aetheria? Their guild was given engineering access to my session logs back on Day 8. Someone at the company agreed to that. Do you know who?*
*If IronVeil's contact is above Kurosawa's review level, there's a conversation to have.*
*— Leo*
---
Sent.
I stood up from the dungeon floor, checked the thermal — five point seven, frontal cluster five point four, elevated from the sitting-still period, already declining — and moved to the next room.
Two Guardians.
Familiar.
I killed them in thirty-eight seconds and checked the loot automatically.
My hands knew the rhythm.
My head was on the sixty-hour clock.
---
### End of Day
Three problems by noon. Three partial moves in response. Nothing resolved.
I logged out at 7 PM.
Thermal: five point three, frontal cluster five point one. Back to baseline.
Updated the spreadsheet.
*Day 15.*
*Debt letter received. New deadline: Day 42. Income gap: ￥2,444/day. Gap requires new revenue source or Archives escalation.*
*Migration complete: 83 routes corrected. 7 routes with absent mechanics identified.*
*Six fixable without infrastructure access — proceeding.*
*Seventh: Cartographer (RESTORATION_03). Requires WORLD_STATE_AWARENESS layer. Infrastructure-level access. Not currently possible.*
*Mitsuki: sandbox access flagged for 72hr review by architect Kurosawa. 60 hours remaining. Documentation in progress.*
*IronVeil contact at Aetheria: query sent. Waiting.*
*PASSENGER: still building. Note received: "we built Mari."*
I looked at that last line.
Then I opened the personal log and added:
*The echoes told me that even if the sandbox is deleted tomorrow, Mari existed for two days. That is more than four years of nothing. They said this not as surrender but as orientation. They know what they have.*
*I should probably know what I have too.*
*Current assets: a chip that's running clean, three passengers who work while I sleep, a developer who is writing documentation in good faith in the middle of a sixty-hour window, a guild contact I haven't used yet, a debt collector who is patient within limits, and a toy merchant walking a circuit in an invisible corner of a server.*
*Current liabilities: obvious.*
*The situation is not comfortable.*
*But it is mine.*
I closed the laptop.
Real world. Apartment. Refrigerator.
The refrigerator hummed.
Through the window, the city continued its business.
In the sandbox, Mari had completed — I checked the echoes' last update before closing the phone — eleven circuits.
On the eighth, ninth, and tenth, she had waited four seconds at the notice board.
On the eleventh: five.
The gap between what she expected and what she found was growing.
We needed to give her something to read.
Sixty hours.
