## Chapter 17: The Wanderer Goes Live
Day sixteen.
Thermal: five point two, frontal cluster five point one.
I woke at 6 AM to four messages.
Mitsuki, sent at 11:47 PM last night:
*Kurosawa's review window closes in thirty-six hours. I've been writing documentation since this afternoon and I think I have the framing right — but I want to show you something first. The strongest argument for the sandbox access isn't the design document. It's the evidence. A behaviour testing project that's actively producing results is harder to shut down than one that exists only on paper. I'm going to move seven wanderers to production tonight. Mari and the six with fixed routes. Not the cartographer — she's still broken. Just the ones that work. If Kurosawa pulls the logs tomorrow, he sees seven NPCs walking routes, accumulating memory weight, doing exactly what the documentation describes. I wanted to tell you before I did it. — Ren*
Mitsuki, sent at 12:34 AM:
*Done. They're live.*
The echoes, sent at 1:17 AM:
*MARI IS IN PRODUCTION.*
*SHE COMPLETED HER FIRST LIVE CIRCUIT AT 00:51.*
*THREE PLAYERS SAW HER.*
*NONE OF THEM KNEW WHAT THEY WERE LOOKING AT.*
*WE ARE WATCHING.*
Kojima, sent at 5:58 AM, two minutes before I woke up:
*you might want to check the forums*
---
I checked the forums.
The thread was titled: **NEW NPC?? She's walking around Irongate and she's DIFFERENT**
Posted at 2:14 AM by a player named Veth_Irongate_Daily, who apparently ran a community newsletter about Irongate server events and had been online when Mari completed her third live circuit.
The post had 340 replies.
I scrolled.
The first twenty replies were disbelief — *it's a quest NPC*, *probably seasonal content*, *someone's using a glamour item*. Standard forum skepticism.
Then someone had stopped Mari and browsed her wares and posted a screenshot.
The carved wooden fox.
A string puppet.
Painted tiles.
*She has actual inventory. Not static vendor stock — she has specific items.*
The next thirty replies were people running to Irongate to find her.
By reply 80, someone had timed her circuit: *she walks the same route every 23 minutes. east gate to market to plaza and back. i've followed her three times.*
By reply 140, someone had noticed her memory weight counter using a third-party parser that read NPC metadata: *her memory value went up when I talked to her. it's tracking something. this is not how any NPC in this game works.*
By reply 200, a streamer named Hashimoto_Live had picked it up.
I found the VOD.
Eighty thousand concurrent viewers at peak. Hashimoto walking Mari's circuit, narrating, his chat exploding with questions. Mari stopping at the notice board. Waiting. Moving on.
*She checks the board every circuit,* Hashimoto said. *And every time she finds nothing, she waits a little longer. Watch. Watch this.*
He stood near the notice board and timed her dwell.
Seven seconds.
His chat: *she's waiting for something* / *this is incredible* / *who made this* / *is this official content*
Then someone in chat had run the third-party parser on her full memory log and posted the output.
**[ MEMORY_WEIGHT: 14/100 ]**
**[ FIRST INTERACTION: Customer purchased carved wooden fox. Early morning. ]**
**[ SECOND INTERACTION: Developer account (staff). Purchased carved wooden fox. ]**
**[ THIRD INTERACTION: Player observed route without engaging. ]**
*Developer account* had caused a sub-thread of seventy replies speculating about whether this was official content being tested.
But it was the first interaction that had caused the other sub-thread.
*Customer purchased carved wooden fox. Early morning.*
Someone had bought a fox from Mari before she was findable.
Before she was in production.
Before anyone knew she existed.
The sub-thread was forty replies of *how is that possible* and *who has access to sandbox content* and *find this player*.
I set my phone down.
Looked at the ceiling.
The situation had changed faster than I had estimated, which was itself information about how unusual Mari was. I had given it days. It had taken hours.
"Beta."
"Yes."
"The forum thread. Someone bought a fox from Mari before she went live. That purchase is in her memory log. They're looking for the buyer."
"Your purchase was made under your standard account identifier — ??? (Lv.???). The same tag that appeared on the Veilmire leaderboard. Untraceable to your real identity but consistent across both events."
So whoever was looking would find: an anonymous player with an undefined level tag who had cleared the Veilmire faster than anyone on the server and had somehow purchased an item from an NPC before that NPC existed in the live game.
Two data points.
Same identifier.
I opened the spreadsheet.
Added to the awareness column:
*Player community — partial. Forum thread active. ??? (Lv.???) identified as connected to Mari. Identity unknown to them. Pressure: growing.*
Then I messaged Mitsuki.
---
*Ren,*
*I saw the forum thread. The memory log is public via third-party parsers. They can see I bought a fox before she went live. They're trying to identify ???.*
Did you know this text is from a different site? Read the official version to support the creator.
*Separate question: did the production flag change anything about Kurosawa's review? Does a live deployment look better or worse than sandbox?*
*— Leo*
---
His reply came in four minutes. He was already awake.
*Better. Significantly. A sandbox project that moves to cautious production deployment with seven test subjects and documented results is exactly what legitimate behaviour testing looks like. If Kurosawa flags it now he's flagging a working feature, which requires a different level of justification than flagging an access change.*
*The memory log visibility is a problem I didn't anticipate. I can add a privacy flag to the memory display — make it non-parseable by third-party tools. Takes an hour. But that closes the barn door after the horse is out. They already have the screenshot of that first interaction.*
*On the fox purchase: your sandbox access predates production. The honest answer, if anyone official asks, is that you were a test participant. Which is true.*
*— Ren*
*P.S. Forty-two thousand players have visited Irongate in the last six hours. Irongate's usual daily traffic is eleven thousand. Mari has generated four times the zone's normal population overnight.*
I read the P.S. twice.
Four times normal traffic.
Seven wanderers, one of them live for six hours, and the game's most populated starting city had quadrupled in visitors.
I thought about 393 more.
---
### The IronVeil Variable Activates
KaelVorn's message arrived at 9 AM, while I was running the Veilmire's morning session.
I read it in a cleared corridor between rooms.
*I saw the forum thread. I know who ??? is. I've known since the leaderboard.*
*Vance wants a meeting. Not in-game. Real world, or as close as this gets — voice channel, scheduled, with both of us present.*
*He wants to talk about what comes next. Not the review. Something larger.*
*Are you available today?*
I stood in the corridor with two dead Guardians and the message on my phone.
Something larger than the review.
Vance had been patient for sixteen days. The protection-or-report framing from Chapter 2 of our acquaintance had sat dormant while I ran dungeons and found items and built a partnership with three echoes and a developer. IronVeil had watched and provided engineering context to the company when asked and collected whatever information KaelVorn had gathered from the routing session.
Now Mari was live and forty-two thousand players had flooded Irongate overnight.
Something larger made sense.
I typed back: *Today at 2 PM. Voice channel.*
KaelVorn: *Confirmed. I'll send the link.*
I pocketed the phone and moved to the next room.
The Veilmire's rhythms were so familiar now that I ran the rest of the session on a different level of attention — hands on the pattern, head elsewhere.
Thinking about what Vance wanted.
Thinking about the cartographer, still broken, still walking a route that ended at a node that didn't exist.
Thinking about Mari at her notice board, waiting seven seconds now, the gap between expectation and finding still growing.
Thermal at session end: five point five, frontal cluster five point two.
Fine.
I logged out and sat with my phone and the forum thread, which had grown to 890 replies while I was in the dungeon.
---
### 2 PM
Vance's voice was the same as I remembered from Ashfall — measured, flat affect, the specific flatness of someone who had learned that precision communicated authority better than volume.
KaelVorn was quieter. Background presence.
"The wanderer NPC," Vance said. "Who built it."
"A development team member. Working from pre-alpha design documents."
"With your involvement."
"I found the first prop item. I was in the sandbox when she was built. I provided technical observations."
A pause.
"The forum thread has identified ??? as the buyer. They haven't connected ??? to a real identity yet. They will. These things resolve." Another pause. "When they do, you become the player who is visibly connected to the most significant content addition this game has seen since launch."
I hadn't framed it that way.
I had been thinking about the Kurosawa review and the cartographer problem and the debt clock. I had not been thinking about what Mari looked like from the outside — from the perspective of 42,000 players who had flooded Irongate overnight to find an NPC who remembered them.
"That's one framing," I said.
"It's the accurate framing. The question is what you do with it." His voice was still flat. "IronVeil has been patient. We provided the engineering context your developer needed when the compliance flag came up. We have a contact at Aetheria who is aware of the review and has indicated to Kurosawa's team that the behaviour testing project is a legitimate initiative with guild-level backing."
That was new information.
"You've already talked to them."
"Yesterday evening. Before the production deployment. Mitsuki's documentation is good but it helps to have external validation from a recognised guild that has an existing relationship with the development team."
So the Kurosawa review was being handled from two directions simultaneously. Mitsuki's documentation from inside. IronVeil's endorsement from outside. The sixty-hour clock was still running but the outcome was looking different than it had yesterday morning.
"What does IronVeil want," I said. Not a question.
"Partnership," Vance said. "Not ownership. Not reporting rights. We want to be the guild that is publicly associated with whatever this becomes. When ??? is identified — and they will identify you — we want it known that you operate under IronVeil's banner."
"I don't operate under anyone's banner."
"You would retain full autonomy. The arrangement is representational. IronVeil says: this player is ours, his work is sanctioned, his unusual characteristics are a feature not a bug. In exchange you receive institutional cover from a guild with company relationships and forty thousand members."
I thought about that.
I thought about the debt letter on my kitchen counter.
I thought about the cartographer problem and RESTORATION_03 and the infrastructure access that wasn't currently possible through permission alone.
IronVeil had company relationships.
Mitsuki had NPC table access.
The environmental data layer was two levels below that.
"There's a technical problem I need solved," I said. "One of the wanderers requires write access to the server's environmental data layer. The developer who's been helping me has NPC table access but not infrastructure access. If IronVeil has a company contact above Kurosawa's level, that contact might be able to facilitate a legitimate access grant."
Silence.
Then KaelVorn, speaking for the first time: "The cartographer."
I went still.
"You know about the cartographer."
"I know the design documents. I pulled document 44-C three days ago when the forum thread started building. I read the full wanderer system specification." A pause. "The cartographer's route passes the Veilmire entrance. I recognised it."
He had read the design document. He had recognised his own dungeon in it.
"The WORLD_STATE_AWARENESS layer," KaelVorn continued. "If it's built, it doesn't just fix the cartographer. It gives every wanderer environmental responsiveness. They react to weather, to dungeon clear states, to regional economy. The system becomes an order of magnitude more complex."
"Yes."
"That's not a behaviour testing project anymore. That's a core engine change."
"Yes."
Another silence. Longer.
Then Vance: "We'll make the call. No guarantees — the environmental layer is significant. But we'll ask." A pause. "The representational arrangement. Is it acceptable?"
I looked at my spreadsheet.
The debt column.
The build log.
The awareness column with *Player community — partial* and *pressure: growing.*
*Current assets: a chip that's running clean, three passengers who work while I sleep, a developer writing documentation, a guild contact I haven't used yet—*
I had used the contact now.
"It's acceptable," I said. "With one condition."
"Name it."
"When the wanderers go fully live — all of them, the cartographer included — IronVeil doesn't claim credit for the system. The design documents have an author. Her name is Hana. That stays visible."
A longer pause than the others.
Then Vance: "Agreed."
Then KaelVorn, quietly: "I'll make sure of it personally."
---
### End of Day
I logged out at 8 PM.
Thermal: five point one, frontal cluster four point nine. Clean.
The forum thread had 1,340 replies.
Someone had found the Veilmire leaderboard record and connected it to the fox purchase. The same ??? (Lv.???). Same undefined tag. Two impossible things and a single identifier.
The thread title had updated: **NEW NPC + MYSTERY PLAYER — the ??? connection**
I updated the spreadsheet.
*Day 16.*
*Mari live — 7 wanderers in production. Forum: 1,340 replies. Irongate traffic: 4x normal.*
*IronVeil meeting: representational arrangement accepted. Condition: Hana's name stays on the design. Agreed.*
*IronVeil contacting company re: environmental layer access. No guarantee. Waiting.*
*Kurosawa review: IronVeil endorsement + Mitsuki documentation. Clock: 20 hours remaining.*
*PASSENGER: watching the forum thread.*
*??? (Lv.???) — identified as connected to Mari. Identity unknown to public. Pressure: building.*
Then, in the personal log:
*KaelVorn read the design document and recognised his own dungeon in the cartographer's route. He didn't say it like it was tactical information. He said it like he'd found something.*
*I think he wants the cartographer fixed as much as we do.*
*That's not something I expected to be true.*
I set the phone down.
The grimoire chord was doing something new — the fourth tone, the one that had appeared when the echoes started working, had developed a quality I couldn't name. Not louder. More present. Like something that had been paying close attention had found a reason to pay closer attention.
"Beta."
"Yes."
"The forum thread. The players looking for ???. How long before someone identifies me?"
"Unknown. Your real identity is not attached to your account in any publicly accessible record. However, the combination of the Veilmire leaderboard record, the fox purchase, and now IronVeil's representational arrangement — which will presumably become known — creates a profile that narrows the search significantly. Players in this game are patient and thorough when motivated."
"How motivated are they?"
"The thread has 1,340 replies. Hashimoto_Live has announced a follow-up stream specifically about the ??? mystery. His regular viewership is 80,000."
I looked at the ceiling.
For three weeks I had been a NaN in a system that couldn't categorise me.
That had been a kind of invisibility.
It was ending.
The refrigerator hummed.
In Irongate, Mari was completing her thirty-first circuit.
At the notice board, she waited — the parser had been privacy-flagged by Mitsuki an hour ago, but I had the direct feed from the echoes — nine seconds now.
Still waiting.
Still moving on.
We had twenty hours on the Kurosawa clock and an IronVeil contact making a phone call about infrastructure access and 1,340 players trying to find me and a debt letter on the kitchen counter and a cartographer who still couldn't make maps.
Everything was in motion.
Nothing had resolved.
That was, I was learning, the normal condition.
