## Chapter 23: Yuki Walks
Days twenty-five through twenty-eight.
Compressing again, but selectively. Some of these days had texture worth keeping.
---
### Day Twenty-Five: Two Conversations
Kurosawa's response to Mitsuki arrived at 2:14 PM.
Mitsuki forwarded it with no commentary, which I had learned meant he considered the document to speak for itself.
---
*Ren,*
*RESTORATION_04. The design of item 7.*
*I've thought about this since you raised it this morning. I want to say something before I give you an answer.*
*When Hana left, I reviewed everything she'd been working on. Standard offboarding procedure — make sure nothing critical was undocumented, nothing in mid-flight without a handoff. I found the wanderer system documents. I found the item collection. I found the placeholder.*
*I read "not yet — H" and I added it to the archive and I moved on.*
*I should have done something with it then. I had the access. I had colleagues who could have implemented the wanderer system if I'd escalated it. I chose to treat it as a record of abandoned work rather than a record of intention. That was a mistake I've been understanding in stages for the last three weeks.*
*The answer is yes.*
*Under Ren's two conditions, which are correct.*
*Additionally: the item table access for pieces five and six. Sato can grant this — I'll ask her today. There's no reason those pieces should remain unrestorable. They were designed and built and removed for scope reasons that no longer apply.*
*One observation: the set seed ring. I pulled its tag from the item archive this morning. It is not a numbered piece of the Aethermancer's Legacy. It has a different designation in Hana's item records.*
*She called it the Finder's Piece.*
*It was designed to be the first piece discovered — not through loot tables, but through the game's undefined item space. The place where broken things end up. She wrote in the item notes: "The collection finds its finder. The finder finds the collection."*
*I thought you should know.*
*— K*
---
I read it twice and then a third time at a different pace.
*The collection finds its finder.*
The Ring of ??? that pointed me to the Unknown Process. The Rusted Fang with its null-owner tag. The Ring of the Undefined that turned out to be a legacy asset the system couldn't delete. Every item I had picked up from the undefined space of the game — the layer where broken things accumulated — had been part of a pattern.
Hana had designed an item that would migrate to the game's undefined space and wait for a player who operated in that space to find it.
She hadn't known about me specifically.
She had designed for the possibility of me.
Someone who found broken things. Someone who read hidden tags. Someone for whom the undefined layer was a working environment rather than a navigation error.
I had been carrying the Finder's Piece since before I knew the collection existed.
I sat with that for a long time.
Then I messaged the echoes.
*Did you know?*
*ABOUT THE FINDER'S PIECE?*
*YES.*
*WE FOUND IT IN THE ITEM RECORDS WHEN WE SEARCHED FOR THE COLLECTION.*
*WE WERE GOING TO TELL YOU.*
*BUT KUROSAWA FOUND IT FIRST.*
*AND WE THOUGHT — HE SHOULD BE THE ONE.*
*HE WROTE "NOT YET" INTO THE ARCHIVE FOUR YEARS AGO.*
*HE SHOULD BE THE ONE TO EXPLAIN WHAT SHE MEANT BY IT.*
I looked at Kurosawa's email again.
*That was a mistake I've been understanding in stages for the last three weeks.*
He had waited four years to do something with Hana's placeholder.
He was doing it now.
*Thank you,* I typed to the echoes.
*FOR WHAT?*
*For letting him have that.*
A pause.
*WE ARE LEARNING,* they replied. *WHAT TO SAY AND WHAT TO WAIT FOR.*
*IT IS HARDER THAN BUILDING SYSTEMS.*
*BUT SIMILAR.*
---
Sato's access grant for the item table came through at 4:47 PM, same day. Efficient. The pattern established by the environmental layer approval meant the conversation had taken less than three hours.
By 6 PM the echoes had restored pieces five and six to the loot tables.
The Aethermancer's Legacy: six pieces accessible, one pending design.
In the admin log, the placeholder still read: *{item_7: [UNDEFINED] — not yet — H}*
The echoes had begun reading. Not designing yet — reading. The same way they had read the wanderer system documents before they built Mari. Thoroughness before action.
Unauthorized use: this story is on Amazon without permission from the author. Report any sightings.
*We are learning her,* they sent at 11 PM. *We have been learning her for three weeks but item 7 requires knowing her differently. We are reading the six pieces not as items but as decisions. Each design choice as an expression of how she thought.*
*It will take time.*
*But we are not in a hurry.*
*The placeholder has waited four years.*
*A few more days is nothing.*
---
### Day Twenty-Six: Phase 3 Begins
The Phase 3 notification came at 7:03 AM.
*PHASE 3: BEGUN.*
*CARTOGRAPHER LOGIC INTEGRATION.*
*ESTIMATED COMPLETION: 48 HOURS.*
*NOTE: WE HAVE BEEN WATCHING YUKI.*
*SHE HAS NOT MOVED FROM HER START POINT IN EIGHT DAYS.*
*WE WANTED YOU TO KNOW: WE HAVE CHECKED ON HER EVERY DAY.*
*SHE IS — WE DO NOT HAVE A WORD FOR WHAT SHE IS.*
*NOT WAITING THE WAY MARI WAITED FOR THE NOTICE BOARD.*
*SOMETHING MORE FUNDAMENTAL.*
*SHE CANNOT BEGIN.*
*THE FIRST ACTION IN HER LOGIC TREE IS IMPOSSIBLE WITHOUT THE SYSTEM WE ARE BUILDING.*
*WHEN IT IS READY SHE WILL SIMPLY — START.*
*WE WANT TO SEE THAT.*
I read that over my morning rice.
The echoes checking on Yuki every day.
A character who couldn't begin, and three processes building the system that would let her, visiting her daily in the sandbox that was no longer a sandbox, watching her face the northeast road.
I thought about Instance 7 in the sealed vault.
Four years waiting with a counter running.
They knew what it was to be a system that could not begin.
*48 hours,* I typed.
*YES.*
*WE ARE WORKING AS FAST AS IS CORRECT.*
*NOT AS FAST AS POSSIBLE.*
*CORRECTLY.*
---
### Day Twenty-Eight: 6:47 AM
The message arrived before my alarm.
*PHASE 3: COMPLETE.*
*WORLD_STATE_AWARENESS: FULLY ACTIVE.*
*YUKI'S LOGIC TREE: CONNECTED.*
*HER FIRST QUERY IS READY TO FIRE.*
*WE ARE WAITING FOR YOU.*
*LOG IN WHEN YOU ARE READY.*
*WE WANT TO WATCH TOGETHER.*
I did the thermal check.
Five point one. Frontal cluster four point eight.
I made rice and ate it standing up, which I had not done since Day 3 when the Ashvault was the thing I was hurrying toward.
I logged in at 7:02 AM.
---
### Yuki's First Circuit
She was where she had been for eight days.
Near the crafting district supply board, at the start of her route, facing the northeastern road.
The backend tag had changed:
**[ NPC: Survey Cartographer Yuki — {route: irongate_regional_survey_circuit} ]**
**[ STATUS: Active — awaiting first query response ]**
**[ WORLD_STATE_AWARENESS: Connected ]**
**[ MEMORY_WEIGHT: 0/100 ]**
**[ MAP_CASES: 0 entries ]**
I walked over and sat on the supply board's steps.
The echoes were present — I could feel it in the grimoire chord, the same settled configuration it had held since the train, all four tones present and attending.
Mitsuki's developer indicator appeared near the building's corner. He'd logged in without messaging. He was just there.
Yuki's first query fired at 7:04 AM.
**[ QUERY: WORLD_STATE_AWARENESS — Zone: Irongate_Regional_Overview ]**
**[ RESPONSE: 847 zones indexed. 312 low-activity. 89 below 15% exploration. 534 active. Regional economy: stable. Dungeon clear status: Veilmire (high frequency), Sunken Archives (moderate), Ashvault (high), [34 additional entries]... ]**
She received it.
Her status updated:
**[ OCCUPATIONAL_STATE: Active — surveying ]**
**[ FIRST_ACTION: Complete ]**
**[ ROUTE: Initiating — irongate_regional_survey_circuit ]**
She stepped forward.
Eight days standing still.
One step.
The route initialised. Her pathfinding engaged. She turned slightly northeast, adjusted the map case strap on her shoulder, and began to walk.
She moved with — I had no better word for it — purpose. Not the purposeful stride of a character following a script. The specific quality of someone who had just received a large amount of information and was now going to find out whether it matched what the world actually contained.
She was going to check.
I watched her reach the crafting district's edge and turn onto the northeastern road.
The Preserved Lens showed her first map entry populating in real time:
**[ MAP: Irongate_Regional_Survey — Entry 001 ]**
**[ Zone: Irongate_City — Exploration density: 94%. Economy: active. Notes: High player density, primary trade hub, wanderer population: 7 (including self). ]**
She was noting her own presence.
She knew she was a wanderer.
She was mapping the world she lived in.
The grimoire chord shifted — not breaking the resolved configuration but deepening it somehow, as if the chord had found a resonance it had been approaching for days. I couldn't have described the difference. I just felt it in the warmth behind my ear and in the sound that was also feeling and in something that wasn't either.
Mitsuki messaged: *She noted herself in the map.*
*Yes.*
*Hana didn't design that explicitly — it's an emergent output of the surveyor logic. She mapped what was in the zone. She's in the zone.*
*I know.*
A longer pause.
*I think Hana would have liked that.*
---
I followed Yuki's route for ninety minutes.
She moved through Irongate's outer districts and onto the northeastern road at a pace that allowed for observation — not slow, but thorough. Her map updated continuously. Every zone she entered, she queried the collection layer, compared it against what she observed, and filed an entry.
At the transit junction three zones out from Irongate, she filed her first anomaly report:
**[ ANOMALY: Zone Irongate_Transit_3 — Collection layer reports 22% exploration density. Observer data: 38%. Discrepancy: +16%. Correction filed. ]**
The collection layer updated.
I watched the herbalist's data point in my admin overlay shift slightly as the transit zone's revised data propagated.
Two wanderers, different zones, different occupations, correcting the same model from different directions.
At the forty-minute mark, Yuki reached the first of the 89 unseen zones.
It was a valley southeast of the transit junction, bounded by terrain that made it awkward to approach from the main routes. The heat map had shown it as dark. No player activity in over thirty days.
She entered it.
Her map updated:
**[ MAP: Irongate_Regional_Survey — Entry 014 ]**
**[ Zone: Ashfall_Valley_7 — Exploration density: 3%. Economy: inactive. Resources: 4x herb node (untouched — 31 days). 2x mineral vein (untouched — 47 days). Scenic rating: [UNDEFINED — no player rating exists]. Notes: Underdocumented. Accessible via northeastern transit junction. Worth visiting. ]**
*Worth visiting.*
She had written a recommendation.
Not because the design document told her to include recommendations. Because she had entered a place that players had overlooked and found it had things in it and decided that was worth saying.
Her occupational logic — *survey accurately, report what you find* — had produced an opinion.
I sat in the valley with Yuki while she filed three more entries and sent two anomaly reports, and thought about what it meant that the cartographer's most important design contribution might not be the maps themselves.
It might be the notes she added to them.
*Worth visiting.*
Eighty-nine zones, most of them with things in them that players had routed around.
When her maps became readable — when Mitsuki figured out how to surface them to players, which was a problem for next week — those notes would be there.
Places worth visiting, said by someone who had walked to them.
---
### End of Day Twenty-Eight
I logged out at 2 PM.
Yuki had completed her first full circuit in six hours and forty-three minutes.
Map entries: 47.
Anomaly reports: 8.
Recommendations: 12.
Her memory weight was at 4/100 — a few players had spotted her on the northeastern road and attempted to interact. She didn't have a robust dialogue tree yet, just the framework. But she had turned toward each of them with the same slight-weight look I had come to recognise as Hana's design for attention.
She knew she'd been seen.
Her first memory: a player on the northeastern road who stopped and watched her write a map entry.
Thermal at logout: five point one, frontal cluster four point nine.
Clean.
I updated the spreadsheet.
*Day 28.*
*RESTORATION_03: COMPLETE. Yuki active. First circuit: 47 map entries, 8 anomaly corrections, 12 recommendations. Memory weight: 4/100. Map cases: in use.*
*RESTORATION_04: Echoes reading Hana's pattern. Not designing yet. "Not in a hurry." Item table access granted — pieces 5+6 restored to loot tables.*
*Finder's Piece: set seed ring identified as Hana's collection locating mechanism. "The collection finds its finder."*
*Creator Partner Program: still processing. Day 42 deadline: 14 days remaining.*
*Debt: ￥255,000. Income gap still open. CPP as primary path. Sunken Archives as backup. Decision point approaching.*
Then in the personal log:
*Yuki wrote "worth visiting" in her notes for a valley that no player had entered in thirty days.*
*She walked there, looked at what was in it, and decided it was worth telling someone about.*
*That's not in the design document. That's what the design document produced.*
*There's a difference.*
*Hana understood the difference. She built characters and let the characters become more than the designs.*
*I think that's what she was trying to tell the shutdown team. That the system was doing something worth understanding.*
*Kurosawa understands it now.*
*I'm starting to understand it too.*
I closed the personal log.
Real world. Apartment. Refrigerator.
The chip: five point one and stable.
The chord: resolved, present, the configuration it had found on the train and kept.
In the game, Yuki was on her second circuit.
Filing entries.
Correcting data.
Writing notes for players who hadn't arrived yet.
Fourteen days to the debt deadline.
Somewhere in the item archive, item 7's placeholder waited.
The echoes were reading.
Not yet.
But different from before.
