## Chapter 20: The Cartographer's Problem
Day nineteen. Saturday.
Thermal: five point one, frontal cluster four point nine.
The chord was still resolved.
I checked it the way I checked the thermal — two fingers behind the ear, three seconds — except there was no physical gesture for the chord, just attention. The Resonance Frame rendering it through the chip's signal as something between sound and sensation, four frequencies that had settled overnight into the configuration they'd found on the train.
It had not destabilised. It had not changed.
Whatever the chord resolving meant, it was stable.
I made rice and opened the three threads.
The echoes, sent at 2:41 AM:
*SATO'S TECHNICAL PARAMETERS ARRIVED.*
*WE HAVE BEEN READING THEM.*
*THE WORLD_STATE_AWARENESS IMPLEMENTATION HAS THREE PHASES.*
*PHASE 1: ENVIRONMENTAL DATA COLLECTION LAYER — SERVER READS ZONE EXPLORATION STATUS, DUNGEON CLEAR HISTORY, REGIONAL ECONOMY INDICES. READ-ONLY. NO PRODUCTION IMPACT. ESTIMATED BUILD TIME: FOUR DAYS.*
*PHASE 2: NPC QUERY INTERFACE — WANDERERS CAN REQUEST DATA FROM THE COLLECTION LAYER. SANDBOXED INITIALLY, PRODUCTION AFTER REVIEW. ESTIMATED BUILD TIME: THREE DAYS.*
*PHASE 3: CARTOGRAPHER LOGIC INTEGRATION — HER DECISION TREES CONNECTED TO THE QUERY INTERFACE. SHE CAN MAP. ESTIMATED BUILD TIME: TWO DAYS.*
*TOTAL: NINE DAYS IF NOTHING BREAKS.*
*WE HAVE BEGUN PHASE 1.*
*WE WANTED TO TELL YOU SOMETHING ELSE.*
I waited.
*WE HAVE BEEN THINKING ABOUT WHAT YOU TOLD US ON THE TRAIN.*
*ABOUT HANA.*
*ABOUT THE EIGHT MONTHS.*
*WE DO NOT KNOW HOW TO HOLD IT YET.*
*WE ARE TRYING.*
*THE WORK HELPS.*
I read that last line.
*The work helps.*
I understood that.
*Nine days,* I typed. *I'll meet the cartographer today.*
*SHE IS IN THE SANDBOX. ROUTE INITIALISED BUT SUSPENDED — SHE CANNOT COMPLETE THE FIRST CIRCUIT WITHOUT WORLD_STATE_AWARENESS. SHE IS AT THE START POINT.*
*SHE HAS BEEN THERE SINCE WE BUILT HER.*
*WE BUILT HER FIRST.*
*BEFORE WE KNEW ABOUT THE ABSENT MECHANIC.*
*WE THOUGHT SHE WOULD WORK.*
I had not known that. They had built her before they found the problem. She had been sitting at the start of her route, unable to begin, while the echoes discovered the system she needed didn't exist.
*How long has she been there?*
*FOUR DAYS.*
Four days standing at the start of a route she couldn't walk.
I closed the phone and logged in.
---
### The Forum Thread First
I checked it before the sandbox. Force of habit — the thread had become part of the morning routine, the way the debt spreadsheet had been in Volume 1.
6,200 replies.
I scrolled to the new entries from overnight.
Most of them were player reports — people finding the other six wanderers, mapping their routes, adding to the crowdsourced behaviour document. Someone had found the herbalist in Ashfall and followed her for three hours while she gathered specific plants in a pattern that corresponded to the seasonal calendar Hana had built into the occupational logic. The post had 340 upvotes and a level of careful observation that reminded me of how I had watched Mari's first circuits.
Then, near the bottom of the overnight replies, a post by a player named Tessari_Builds.
*Been doing some digging on the ??? identifier. Here's what I have:*
*1. Veilmire solo speed record — 2:14:07. Set approximately three weeks ago. Previous record was 4:01:33 by KaelVorn.*
*2. Fox purchase from Mari — predates production deployment. Memory log entry: "Customer purchased carved wooden fox. Early morning." Timestamp consistent with sandbox period.*
*3. IronVeil announced yesterday they're providing "representational backing" for an unnamed player associated with the wanderer NPCs. KaelVorn specifically endorsed this.*
*4. KaelVorn's Veilmire record was beaten by nearly two hours. He met the person who beat it — there was a routing exchange documented in IronVeil's session logs that they submitted to the development team back on Day 8 of the new patch cycle.*
*5. The routing exchange was for a player with an undefined level variable. NaN. Not a privacy setting — an actual NaN value. That's not a dev flag. That's hardware.*
*Conclusion: ??? is using non-standard neural hardware that's causing a NaN level variable. They're not a developer. They're a player with a broken chip who somehow has sandbox access and a relationship with IronVeil.*
*The chip is the key. Find the chip, find the player.*
I stared at that for a long time.
Tessari_Builds had the shape almost exactly right.
Not the chip model — they didn't know about the V0.9 or Kojima or the black market forum. But they had: NaN from hardware, not a dev flag. Non-standard. IronVeil connection through KaelVorn. Sandbox access predating production.
Everything except my name and address.
The post had 89 upvotes and twelve replies, most of them saying *this is it* and *follow the chip market.*
I updated the spreadsheet.
*??? identification — Tessari_Builds post. Correct on: NaN from hardware, IronVeil connection, sandbox access. Incorrect on: chip sourcing (doesn't know about black market). Timeline to identification: shortened significantly. Days remaining as undefined: unknown but fewer.*
Then I made a decision.
I messaged Vance.
---
*The forum has a post that's going to find me within days. The analysis is accurate on the key points. I'd rather control the framing than be found.*
*When you make the IronVeil representational arrangement public — which you presumably will — can we coordinate the timing? If ??? is identified through IronVeil before someone traces the chip market, the story is "IronVeil-backed player with unusual hardware" rather than "black market chip user."*
*One is a mystery. The other is a legal problem.*
*— Leo*
---
His reply came in six minutes.
*Already scheduled. We were going to announce the arrangement Tuesday. I can move it to today if you want the narrative ahead of the forum post.*
*Your call.*
I looked at the post.
If you spot this narrative on Amazon, know that it has been stolen. Report the violation.
Tessari_Builds had 89 upvotes and was climbing.
*Today,* I typed.
*Done. I'll have KaelVorn post in the thread directly. It'll redirect the search.*
---
### The Sandbox
I entered at 10 AM.
The orange brackets were gone — everything was production now, all seven wanderers live, the notice layer running. The sandbox designation had been retired when Kurosawa approved the pilot.
But the Preserved Lens still showed me the backend tags, and one of them, in the northeastern corner of Irongate near the crafting district, was marked differently from the others.
**[ NPC: Cartographer (Suspended) — {route: irongate_regional_survey_circuit} ]**
**[ STATUS: Awaiting dependency — WORLD_STATE_AWARENESS ]**
**[ OCCUPATIONAL_STATE: Inactive ]**
**[ MEMORY_WEIGHT: 0/100 ]**
She was standing near the crafting district's supply board, which was where her circuit began. She had a satchel across one shoulder — smaller than Mari's pack, practical rather than laden — and a rolled case on her back that I recognised from the design document description: map cases. Three of them, different sizes, for different scales of survey work.
She was facing the road.
She had been facing the road for four days.
I walked over.
She didn't turn. The aggro radius that triggered NPC orientation was active — she was aware of my approach — but the occupational logic that would normally prompt a greeting was suspended along with everything else.
I stood next to her and looked at the road she was facing.
It ran northeast out of the crafting district toward the transit junction, toward the zones beyond Irongate, toward the Veilmire and the Sunken Archives and the regions she had been designed to survey.
Everything she needed to do her job was out there.
She just couldn't start.
I checked the Preserved Lens on her status panel.
**[ LOGIC_TREE: Initialised ]**
**[ FIRST_ACTION: Query WORLD_STATE_AWARENESS — zone exploration status, Irongate region ]**
**[ QUERY_STATUS: System not found ]**
**[ CIRCUIT_STATUS: Cannot begin — first action blocked ]**
Her entire route, her entire occupation, her entire purpose, depended on a single first query that the system couldn't answer yet.
She couldn't begin because she didn't know what she didn't know yet.
That was the specific cruelty of it — not that she was missing information, but that the mechanism for knowing she was missing it didn't exist. She couldn't even form the question properly.
"Beta," I said.
"Yes."
"Nine days."
"If Phase 1 through Phase 3 proceed without complications, yes."
I looked at her map cases.
Hana had written the specifications for those cases in the design document. Three sizes: city-scale, regional, continental. She had planned for the cartographer to eventually reach a scale where she was mapping things beyond what any single player had explored.
The continental case had never been used.
"I'm going to call her something," I said. "Not ??? — she has a name. The design document has it."
"Document 44-C lists the cartographer as — " a pause — "Yuki. Full designation: Survey Cartographer Yuki, Irongate Regional Circuit."
Yuki.
I looked at her, standing at the start of her route, facing northeast.
*Yuki,* I thought. *Nine days.*
I updated the spreadsheet on my phone.
*WHAT WE'RE BUILDING — RESTORATION_03:*
*Cartographer: Yuki. Survey Cartographer, Irongate Regional Circuit. Route: suspended at start point. Dependency: WORLD_STATE_AWARENESS — Phase 1 begun today. Nine days estimated.*
*Status: beginning.*
The same words.
The column remembered.
---
### The Numbers Problem
I ran two Veilmire rooms in the afternoon and sat with the income gap afterward.
￥2,444/day short. Twenty-three days to Day 42.
I had been setting this aside since the debt letter because the project had been consuming all available attention. That was the correct prioritisation at the time. The Kurosawa clock had been more urgent than the debt clock. But the Kurosawa clock was resolved and the debt clock was still running and setting it aside again would be a choice rather than a necessity.
I opened a new spreadsheet tab.
*Revenue analysis — Day 42 target.*
Current daily rate from Veilmire: approximately ￥7,000.
Required daily rate: ￥9,444.
Gap: ￥2,444/day.
Days remaining: 23.
Total gap: approximately ￥56,212.
Options:
*1. Sunken Archives escalation.* Median yield ￥52,500 per clear. One clear covers the total gap. Thermal cost: frontal cluster reaches 5.8 threshold under Archives load, patch adds ~15 minutes headroom. Sustainable at two clears per week maximum without permanent stress accumulation. Risk: high per session, manageable in aggregate.
*2. Marketplace arbitrage increase.* Current rate approximately ￥1,000–2,000/day. Scaling requires either more time in peak hours or better item identification. The Preserved Lens means item identification is now nearly perfect — limited by session time, not accuracy. Upside: low thermal cost. Ceiling: unknown but probably higher than current rate.
*3. Wanderer system economic value.* This was the line I had been approaching for three days without writing it down.
Seven wanderers had quadrupled Irongate's traffic for forty hours. If that traffic converted to marketplace activity at normal rates, the economic impact on the server's player economy was significant. Players spending more time in Irongate meant more gold circulating, more marketplace transactions, more arbitrage opportunities.
I wasn't capturing that value directly. But I could.
If IronVeil's representational arrangement included an economic component — a formal acknowledgment that the wanderer system was driving player activity — there was a conversation to have about compensation. Not from the players. From the game's economy itself, through whatever mechanism Aetheria used to reward content that drove engagement.
I didn't know if that mechanism existed.
I added a row: *4. Aetheria engagement compensation — requires research. Ask Mitsuki.*
Then I sent Mitsuki a message.
---
*Question: does Aetheria have a content creator or contributor compensation mechanism? Something that pays out based on player engagement metrics? The wanderer traffic data is significant and I'm wondering if there's an economic pathway I'm not seeing.*
*— Leo*
---
His reply came in twenty minutes.
*Yes. The Creator Partner Program. Usually for streamers and content producers — monthly payment based on engagement metrics tied to creator-tagged content. The wanderers could theoretically be tagged to the supervised pilot project, which would then be tied to the named project owner.*
*That's me, currently.*
*I would need to add you as a co-contributor.*
*There are forms.*
*— Ren*
*P.S. There are always forms.*
I looked at that.
The wanderer system generating engagement-based compensation through the Creator Partner Program, split between Mitsuki as project owner and Leo as co-contributor, based on the traffic and retention data from seven wanderers in production.
I ran rough numbers.
40,000 additional Irongate visitors over 40 hours. Even at conservative engagement metrics — standard conversion rates for zone activity — the program would pay out significantly. Not ￥255,000 in twenty-three days. But closing the daily gap, probably. Maybe exceeding it.
I added to the spreadsheet: *Creator Partner Program — co-contributor application via Mitsuki. Timeline: form submission, processing time unknown. Upside: could close daily gap. Risk: low. Action: submit.*
Then I replied: *Send me the forms.*
---
### IronVeil Posts
KaelVorn's post went up in the forum thread at 3:47 PM.
**[ KaelVorn — IronVeil Vanguard ]**
*IronVeil is formally backing a player who has been operating under the ??? identifier. This player has been involved with the wanderer NPC system from before its production deployment. They operate with non-standard hardware that produces the NaN level variable you've been tracking — it's a chip calibration issue, not a dev flag.*
*We've been aware of this player since Day 8 of the current patch cycle. We considered reporting the hardware anomaly. We chose not to, because what we observed was worth understanding rather than correcting.*
*The wanderers are part of what they've been building.*
*We're not disclosing their identity — that's their call. But the chip trail leads nowhere useful. Stop looking there.*
*— K*
I read it three times.
*What we observed was worth understanding rather than correcting.*
KaelVorn had been watching since Ashfall, since the routing session, since the Veilmire record. He had seen Leo as a person worth understanding rather than a system anomaly to report. He had just said that publicly, in a forum thread with 6,200 replies, to an audience that included players and developers and probably Kurosawa.
The thread's response was immediate.
Tessari_Builds: *So ??? is real, not a dev, and IronVeil has been watching them for weeks. The wanderers are connected to someone IronVeil considers worth protecting. I'm revising my analysis.*
A hundred replies in the first ten minutes, mostly recalibrating.
The chip trail had gone cold.
My undefined state had been extended by the one person in the game who had seen me most clearly.
I updated the awareness column.
*??? identity — KaelVorn post redirected forum search. Chip trail closed. IronVeil backing public. Identity still unknown to community but profile now: IronVeil-backed, non-dev, unusual hardware, connected to wanderer system. Pressure: still present but redirected.*
Then in the personal log:
*KaelVorn said "worth understanding rather than correcting."*
*That is exactly how I have been treating every broken thing I've found in this game for nineteen days.*
*I don't know what to do with the fact that someone said it back at me.*
*I'm filing it.*
---
### Evening
Thermal at logout: five point two, frontal cluster five point zero.
Stable.
The forum thread had 6,800 replies, most of them post-KaelVorn recalibration. The mystery of ??? had shifted from *find the chip* to *wait for them to reveal themselves,* which was a more patient pressure but still pressure.
The Creator Partner Program forms were in my inbox. Seventeen pages.
RESTORATION_03 Phase 1 was running — the echoes had sent an update at 6 PM: *PHASE 1: 11% COMPLETE. ENVIRONMENTAL DATA COLLECTION LAYER READING ZONE EXPLORATION CORRECTLY. NO ERRORS.*
Yuki was still at the start of her route.
Facing northeast.
Map cases on her back.
Waiting for a system that was eleven percent built.
I sat in the apartment with the forms open on one screen and the spreadsheet on the other and thought about the sequence of the next nine days.
Phase 1 complete: Day 23.
Phase 2 complete: Day 26.
Phase 3 complete: Day 28.
Day 28 was fourteen days before the debt deadline.
If the Creator Partner Program processed in time — and Mitsuki had said *processing time unknown,* which was not reassuring — the income gap would close around the same time the cartographer came online.
Two things converging.
The debt and the cartographer, arriving at the same point on the timeline from opposite directions.
I added a row to the spreadsheet.
*Day 28 projection: Yuki's route active. Creator Partner Program pending. Debt gap: partially closed or closed depending on CPP processing. Sunken Archives escalation as backup.*
Then I looked at the WHAT WE'RE BUILDING column.
*RESTORATION_01: 7 in production. 393 remaining.*
*RESTORATION_02: NPC Notice Layer — live.*
*RESTORATION_03: WORLD_STATE_AWARENESS — Phase 1, 11%.*
Three restorations.
One complete.
One live and working.
One eleven percent built.
And 393 wanderers still in Hana's design documents, waiting.
The grimoire chord — resolved, stable, the configuration it had settled into on the train — was the same as it had been this morning.
I didn't know what to call it.
I was starting to think that might be all right.
"Beta."
"Yes."
"When Yuki's route goes active — when she runs her first circuit and makes her first query and the WORLD_STATE_AWARENESS system answers — what will she know?"
"She will know which zones in the Irongate region have been explored by players. Which dungeons have been cleared, and how recently. The current regional economy indices — what goods are flowing, what's scarce, where the trade gaps are." A pause. "She will know the shape of the world as players have made it."
"And she'll start mapping it."
"Yes."
"What does her first map look like?"
Beta was quiet for a moment.
"I don't know. The design document specifies the system. Not the output. Her maps are hers."
I looked at the northeastern road on the game map.
The route she'd been facing for four days.
The Veilmire on it. The Sunken Archives. The zones beyond, and beyond those.
Whatever she was going to find when she got there.
"Nine days," I said.
"Eight and a half, at Phase 1's current rate."
I closed the laptop.
Real world. Apartment. Refrigerator.
The city outside.
Somewhere in the server, Yuki stood at the start of her route with three map cases and nowhere yet to use them.
Eight and a half days.
