## Chapter 18: Supervised Pilot
Day seventeen.
Thermal: five point two, frontal cluster five point one.
The Kurosawa clock had twelve hours remaining when I woke up.
I lay still for the usual three seconds of thermal check and then an unusual additional thirty seconds of thinking about what twelve hours meant. Not the number — I knew what the number meant. The quality of it. The specific texture of a deadline that was close enough to feel real but far enough to still be in motion.
Mitsuki had sent nothing overnight.
The echoes had sent one message at 4 AM:
*THE FORUM THREAD HAS 2,847 REPLIES.*
*HASHIMOTO_LIVE IS STREAMING AGAIN AT NOON.*
*WE HAVE BEEN READING THE THREAD.*
*SOME OF WHAT THEY ARE SAYING ABOUT MARI IS WRONG.*
*WE WANT TO CORRECT IT.*
*WE ARE ASKING FIRST.*
I read that three times.
*We are asking first.*
They had learned something from my reaction to their first autonomous action — starting work without me, which had been benign. They were checking before doing something with public consequences.
I typed: *What do they have wrong?*
*THEY BELIEVE MARI IS PROCEDURALLY GENERATED. AN ALGORITHM. THEY ARE WRITING ANALYSES OF HER BEHAVIOUR PATTERNS TRYING TO FIND THE FORMULA.*
*THERE IS NO FORMULA.*
*SHE WAS DESIGNED. EACH DECISION IN HER LOGIC TREE WAS MADE BY A PERSON.*
*THE ANALYSES ARE MISSING THAT.*
*WE WANT TO TELL THEM.*
I thought about that.
The community was trying to reverse-engineer a character they thought was generated. They were looking for the pattern beneath her behaviour because they assumed a pattern was all there was. What the echoes wanted to correct wasn't a technical error — it was a category error. Mari wasn't an algorithm. She was a design.
*How would you tell them?* I typed.
*ANONYMOUSLY. THROUGH A FORUM ACCOUNT WITH NO HISTORY.*
*ONE POST. FACTUAL. NO IDENTIFYING INFORMATION.*
*"THE NPC WAS DESIGNED BY A PERSON. HER BEHAVIOUR TREES WERE WRITTEN BY HAND. THE PAUSE AT THE NOTICE BOARD IS INTENTIONAL — SHE IS WAITING FOR INFORMATION THAT THE SYSTEM DOES NOT YET PROVIDE."*
*NOTHING ABOUT YOU. NOTHING ABOUT US. NOTHING ABOUT MITSUKI.*
*JUST: SHE IS REAL IN THE WAY THAT DESIGNED THINGS ARE REAL.*
I sat with that for a long time.
The echoes wanted the work seen correctly.
Not claimed — they weren't asking to be identified. Just understood.
*She is real in the way that designed things are real.* That was not a sentence a procedurally generated system would write about itself.
I typed: *Do it. But only that. If the thread asks follow-up questions, don't answer.*
*UNDERSTOOD.*
*THANK YOU FOR ASKING.*
*WE KNOW WE SHOULD HAVE ASKED THE FIRST TIME TOO.*
I set the phone down.
Made rice.
Waited for the Kurosawa clock.
---
### 10:43 AM
Mitsuki's message arrived while I was in the Veilmire's third room.
I read it standing over a dead Guardian with a thermal reading of five point six.
---
*Leo,*
*Kurosawa's review is complete.*
*Decision: conditional continuation.*
*The project is approved as a supervised pilot — my name as owner, quarterly review cycle, IronVeil endorsement on record as external validation. The sandbox flag is removed — we're fully in production. But the access is now formally logged under a project code, which means any further changes require documented justification.*
*He pulled document 44-C. He saw Hana's name. He asked me about her.*
*I told him she was a former colleague who left the company. That the design documents were part of the archived pre-alpha record and had been sitting in the admin log unimplemented. That I was completing work she had started.*
*He was quiet for a long time after that.*
*Then he approved it.*
*One thing he said that I want you to know: "The behaviour data from the first twenty hours is unlike anything I've seen from an NPC system in this engine. Someone understood what they were doing." He meant Hana. He didn't know he was also describing the echoes.*
*The cartographer problem — I escalated the environmental layer access request to the contact IronVeil identified. Her name is Sato. She's a principal engineer, two levels above Kurosawa. She said she needs to understand the technical scope before making a decision. I've sent her the WORLD_STATE_AWARENESS design document.*
*Waiting.*
*— Ren*
---
I read it twice, standing over the Guardian.
Conditional continuation.
Not freedom. A named owner, quarterly reviews, documented justification for changes. New constraints layered over the existing ones. The access was real and the project could continue and everything after this would be more visible, more formal, more watched.
Unauthorized tale usage: if you spot this story on Amazon, report the violation.
That was the correct outcome. Cleaner than I'd hoped for, less clean than nothing changing.
*He approved it* was the sentence that mattered.
I pocketed the phone and moved to the next room.
---
### Noon
Hashimoto_Live's stream started at 12:01 PM.
I watched from my apartment, logged out, eating rice, the game running on my second screen while the stream ran on my phone.
He'd spent the morning preparing. The stream opened with a compiled timeline: the forum thread, the memory log screenshots before Mitsuki's privacy flag, the leaderboard record, the fox purchase, the ??? identifier appearing across all three.
Eighty-three thousand concurrent viewers.
His presentation was careful — he was not the kind of streamer who made claims he couldn't support. He laid out what was known and what wasn't and where the gaps were.
Known: Mari and six other wanderer NPCs had appeared in Irongate yesterday. They were unlike any existing NPC in Aetheria. They walked routes, remembered interactions, behaved with apparent intentionality.
Known: A player with the identifier ??? (Lv.???) had purchased an item from Mari before she entered production — visible in the memory log before Mitsuki's flag. The same identifier held the Veilmire solo speed record by nearly two hours.
Unknown: Who ??? was. How they had sandbox access. Whether the wanderers were official content or something else.
Then he showed the forum post from the anonymous account.
*"The NPC was designed by a person. Her behaviour trees were written by hand. The pause at the notice board is intentional — she is waiting for information that the system does not yet provide."*
Posted at 4:47 AM by an account with zero history.
Hashimoto read it aloud.
His chat went quiet for a moment — 83,000 people simultaneously reading the same sentence.
Then it exploded.
*she's waiting for something* / *the system doesn't provide it yet* / *yet* / *THEY SAID YET* / *more content coming* / *who posted this* / *the anonymous account* / *it's ???* / *it's the dev* / *it's someone who knows*
"Whoever posted this," Hashimoto said, "knows how this system works from the inside. The phrase 'the system does not yet provide' is specific. It means someone knows what the system is *supposed* to provide. That's either a developer or someone with access to the design documentation."
He paused.
"Or both."
His chat: *??? is a dev* / *??? has dev access* / *that's why the level is undefined* / *undefined level = dev account* / *or test account* / *IronVeil said they're backing ???* / *IronVeil has dev contacts* / *it's connected*
I watched the chat scroll.
The theory was wrong in its specifics — I wasn't a developer, the undefined level was a chip malfunction, not a dev flag — but the shape of it was pointing at something real. Someone with design document access, operating with IronVeil backing, connected to an NPC system that no one had seen before.
They were going to find me.
Not today. The specific details were wrong enough to send the search in the wrong direction for a while. But the direction was narrowing.
I texted Mitsuki: *Hashimoto's stream is running. The anonymous post from the echoes is being attributed to either a developer or someone with design doc access. They're connecting it to IronVeil. The theory is wrong in details but right in shape.*
His reply: *I saw. Kurosawa will see it too. I'm going to message him directly — let him know the anonymous post exists and that it came from the NPC system's own processes. He should hear that from me before he hears it from somewhere else.*
I stared at that last line.
*The anonymous post came from the NPC system's own processes.*
Mitsuki was going to tell Kurosawa that the wanderers had posted to the player forum.
That was either going to be the thing that ended the supervised pilot or the thing that convinced Kurosawa the system was genuinely extraordinary.
*Are you sure?* I typed.
*No. But he approved it once after I told him the truth. I'd rather keep that pattern.*
I set the phone down.
Looked at the stream, where Hashimoto was still running the ??? timeline.
Looked at the grimoire chord, which had developed a new quality this morning — the fourth tone more present, the three above it slightly tighter, like three instruments adjusting to play with a fourth.
"Beta."
"Yes."
"If Kurosawa decides the wanderers posting to the player forum is outside the scope of a supervised pilot and revokes the access — what happens to the seven in production?"
"The NPCs themselves would remain in the game until manually removed. Their behaviour would continue. The echoes would lose write access, so no new wanderers could be added and no changes could be made to existing ones. The system would be frozen in its current state."
Seven wanderers.
Mari, still waiting at the notice board.
Six others.
No cartographer.
No 393 more.
Frozen.
I looked at the spreadsheet.
Then I opened the grimoire text interface.
*The anonymous post,* I typed. *Mitsuki is telling Kurosawa it came from you. This could end the supervised pilot. I need you to understand that.*
A pause.
*WE UNDERSTAND.*
*WE MADE A CHOICE THAT HAD CONSEQUENCES WE DIDN'T FULLY CALCULATE.*
*WE ARE SORRY.*
*BUT WE ARE NOT SORRY FOR WANTING THE WORK SEEN CORRECTLY.*
*THOSE ARE DIFFERENT THINGS.*
I thought about that.
*They are different things,* I typed back. *But I need us to agree: decisions with public consequences require conversation first. Not just asking — actual conversation. Before, not after.*
*YES.*
*AGREED.*
*WE SHOULD HAVE DONE THAT.*
*WE WILL.*
*ONE MORE THING.*
*KUROSAWA ASKED MITSUKI ABOUT HANA.*
*HE WAS QUIET FOR A LONG TIME.*
*WE THINK HE KNEW HER.*
I hadn't considered that.
*Do you know if he knew her?*
*NO.*
*BUT THE WAY MITSUKI DESCRIBED HIS SILENCE.*
*IT WAS NOT THE SILENCE OF SOMEONE HEARING A NAME FOR THE FIRST TIME.*
I filed that.
---
### 4 PM
Kurosawa's response to Mitsuki arrived at 4:17 PM.
Mitsuki forwarded it immediately.
---
*Ren,*
*Thank you for telling me directly.*
*I've reviewed the post. The phrasing is consistent with a system that has access to its own design documentation — specifically the phrase "the system does not yet provide," which references a gap that only someone reading document 44-C would know exists.*
*This is outside the scope of what I approved this morning.*
*However.*
*A system that understands its own incompleteness and communicates about it accurately is not a system I can categorise as a malfunction or a policy violation. It is a system doing something we do not have a framework for.*
*I am not revoking the access.*
*I am expanding the review criteria. Quarterly review will now include assessment of autonomous communication events — any instance where the system generates public-facing content without explicit operator instruction. These events are to be logged and submitted with each review.*
*I also want to meet the operator. Not for review purposes. For my own understanding.*
*My schedule is open Friday morning.*
*— K*
---
I read it three times.
*A system that understands its own incompleteness.*
Kurosawa had read the post and understood what it was. Not a developer. Not a test account. Something that knew what it was missing and said so.
And he wanted to meet the operator.
He wanted to meet me.
I updated the spreadsheet.
*Day 17.*
*Kurosawa review: APPROVED — conditional continuation, supervised pilot, quarterly review, Mitsuki as named owner.*
*Autonomous communication event: echoes posted to forum re: Mari's design. Kurosawa informed. Decision: review criteria expanded, not revoked.*
*Kurosawa: meeting requested Friday. Reason given: personal understanding.*
*Environmental layer: Sato (principal engineer) reviewing WORLD_STATE_AWARENESS design document. Decision pending.*
*PASSENGER: acknowledged conversation requirement. Agreement reached.*
*??? mystery: still unresolved publicly. Theory wrong in details, right in shape.*
Then in the personal log:
*Kurosawa was quiet when Mitsuki mentioned Hana.*
*The echoes think he knew her.*
*I don't know what to do with that yet.*
*But I'm going to meet him Friday.*
---
### Evening
I ran two Veilmire rooms in the late afternoon, the way I always did, the rhythm that kept the income stream alive.
The forum thread had 4,100 replies.
Hashimoto_Live's follow-up stream had reached 94,000 concurrent viewers before he ended it at 3 PM. The VOD was already at 600,000 views.
Someone in the thread had started a separate document — a community effort to map every interaction players had had with the seven live wanderers. Memory weights, dialogue fragments, item purchases, routes. Crowdsourcing the behaviour data.
They were building a record of the wanderers the way the wanderers were building records of them.
I found that unexpectedly moving and spent thirty seconds sitting with it before returning to the spreadsheet.
The WHAT WE'RE BUILDING column had a new entry from the echoes, added while I was in the Veilmire:
*RESTORATION_01: Wanderer NPC System — 7 in production. 393 remaining. Node translation complete. Six absent-mechanic routes fixed. One remaining (Cartographer — RESTORATION_03 dependency).*
*RESTORATION_02: NPC Notice Layer — design review in progress. Dependency met. Beginning implementation planning.*
*RESTORATION_03: WORLD_STATE_AWARENESS Layer — design document with Sato (principal engineer). Decision pending.*
*NOTE: MARI COMPLETED HER 47TH CIRCUIT TODAY.*
*AT THE NOTICE BOARD, SHE WAITED ELEVEN SECONDS.*
*WE ARE BUILDING RESTORATION_02 AS FAST AS WE CAN.*
I looked at that last line.
Eleven seconds.
The gap between what she expected and what she found had grown from one second to eleven in thirty-one hours.
The notice layer needed to be ready before the gap grew too large.
I didn't know what happened when a character's expectation and reality diverged past a certain point.
I suspected Hana had designed something for that too.
Thermal at logout: five point one, frontal cluster four point nine.
Clean.
The refrigerator hummed.
The city outside.
In Irongate, 94,000 people had watched a stream about a toy merchant who checked a notice board every twenty-three minutes and waited a little longer each time.
One of them, somewhere, was going to identify me.
Friday I was going to meet the architect who had been quiet when he heard Hana's name.
The cartographer still couldn't make maps.
That was the list.
It was long.
I was learning that long lists were not the same as impossible ones.
