## Chapter 15: The Toy Merchant's Name

  Day fourteen.

  Thermal: five point three, frontal cluster five point one.

  Two days running at the same baseline. The patch and the passengers were stable together — the chip had found its new equilibrium.

  I held my fingers behind my ear for the usual three seconds and thought about the toy merchant.

  She'd been in the sandbox for sixteen hours. The echoes had been working on her overnight — I could tell from the fourth tone in the grimoire chord, which had developed a rhythmic quality by morning, like a particular kind of focus. Not urgency. Craftsmanship.

  I made rice and logged in without checking the messages first. Whatever they'd built, I wanted to see it before I read about it.

  ---

  ### Sandbox Access

  Mitsuki had set up a sandbox instance layered underneath the main game's architecture — technically the same server space, flagged non-production, invisible to regular players. Accessing it required a console command that Mitsuki had sent last night in a short email:

  *To enter the sandbox: open the console in Irongate's central plaza, type /env sandbox_01. You'll see a visual overlay distinguishing sandbox elements. They're labelled with orange brackets. Everything else is live production. — Ren*

  *P.S. I'll log in tomorrow afternoon. I want to see her walking before I review the build notes.*

  I opened the console in Irongate's central plaza — a function that technically existed for developer testing and was inaccessible to standard player interfaces, but which the Preserved Lens rendered visible as a dim UI element near the plaza's central fountain.

  */env sandbox_01*

  The world didn't change.

  Almost.

  At the edge of my vision, a faint orange tint appeared on certain elements — a notice board near the market district, a section of the eastern road, a bench near the city gate.

  And, standing at that bench, partially occluded by a market stall's awning:

  **[ NPC: Merchant (Sandbox) — {route: irongate_eastern_circuit} ]**

  **[ STATUS: Active — walking route initialised ]**

  **[ MEMORY_WEIGHT: 0/100 ]**

  **[ INVENTORY: ... ]**

  The orange bracket marked her as sandbox.

  I walked over.

  She was short — shorter than most of Aetheria's NPCs, which tended toward the heroic proportions of characters designed to look impressive from a distance. She had a pack on her back that was slightly too large for her frame, the way real packs look on people who carry more than they should. She was looking at the notice board when I approached, head tilted, reading something with apparent attention.

  I stood next to her.

  She turned.

  Her face rendered differently from standard NPCs — less symmetric, more specific. One eye slightly more open than the other. A particular set to the mouth that wasn't a smile and wasn't neutral but something between the two.

  The design showed.

  *She looked at me.*

  Not the NPC-default orientation-toward-nearest-player. An actual look, with the slight weight of someone deciding whether to speak.

  "Hello," she said.

  Standard NPC greeting. The dialogue tree was basic — they hadn't filled it in yet, just the framework. But the delivery had something in it that the Ashvault guardians and the Veilmire level-check NPC hadn't had.

  She sounded like she'd been doing something before I walked up.

  "Hello," I said.

  "Are you looking for something?"

  The dialogue options: **[Yes]** **[No]** **[Browse wares]**

  I selected *Browse wares.*

  Her pack opened — a merchant interface, standard layout.

  The Carved Wooden Fox was in it.

  Not a copy. Not a duplicate generated by the system. The specific item from my inventory was in her wares list, available for purchase at a price the echoes had calculated based on market value.

  Except it was also in my inventory.

  Same item, two locations simultaneously.

  "Beta," I said quietly. "The fox. It's in her inventory and mine."

  "The sandbox NPC's inventory is drawing from a shared item reference — it recognises the toy as belonging to her occupational set and has added a merchant-instance of it to her wares. The item in your inventory is your copy. They're the same template, not the same item instance."

  "So she sells foxes. And I happen to have one."

  "Correct. You found her prop before she existed. Now that she exists, the prop's context has resolved."

  I checked the Carved Wooden Fox in my inventory.

  Its hidden tag had updated.

  **[ Carved Wooden Fox ]**

  **[ {story_flag: wanderer_toy_merchant_inventory_item} → RESOLVED ]**

  **[ NEW TAG: {origin: toy_merchant_mari} ]**

  *Mari.*

  The item tag had given her a name.

  Not a name from Hana's design document — I hadn't seen a name in the summary. A name that had been embedded in the item's metadata, waiting for the merchant to exist so the item could tell me who it belonged to.

  "Beta. Is the name in the design document?"

  "Accessing document 44-C..." A pause. "Yes. Buried in the inventory manifest for the toy merchant, not in the main NPC description. The manifest entry reads: *'Toy merchant (Mari) — inventory: carved wooden fox, string puppet, painted tiles, seasonal items TBD.'"*

  Hana had named her.

  Four years ago, building a prop inventory, she had written the name in the manifest and the name had been sitting in a hidden tag on a carved wooden fox in a dungeon loot table ever since.

  I looked at Mari.

  She had closed her pack and turned back to the notice board.

  Reading whatever she had been reading before I arrived.

  Doing something.

  I sat down on the bench.

  ---

  ### The Seam

  I watched her walk the route for twenty minutes.

  It was a small circuit — three blocks of Irongate, east gate to market district to the plaza and back. The route Mitsuki had flagged in orange. She moved with the specific quality of someone who knew where she was going and wasn't in a hurry about it, stopping occasionally to look at things: a shop window, a notice, a player who passed close enough to warrant attention.

  If you spot this tale on Amazon, know that it has been stolen. Report the violation.

  The memory weight counter stayed at 0/100.

  That was correct — she hadn't interacted with anyone yet. Memory accumulated through interactions. The counter would fill as players met her, spoke to her, bought from her, passed her repeatedly without stopping.

  At zero, she was a complete character with no history.

  At 100, she would be someone with a past.

  The design was working.

  Then she reached the east gate, turned to begin the circuit again — and stopped.

  Not a pathfinding pause. A full stop, mid-stride, the kind that in a human being would mean a thought arriving unexpectedly.

  Her status indicator updated:

  **[ STATUS: Route interrupted — NAVIGATION_ERROR ]**

  **[ Attempting recalculation... ]**

  **[ ERROR: Path node {irongate_east_road_node_7} — reference not found ]**

  She stood at the gate entrance and couldn't proceed.

  I checked the route map in the sandbox overlay.

  East road node 7 was the junction point where the eastern road left Irongate's city limits and entered the transit zone toward the next settlement.

  That transit zone had been redesigned in content pass 3.

  The road still existed. The node reference in Hana's design document used the pre-pass-3 coordinate system, and the echoes had implemented the route using those coordinates. But content pass 3 had renumbered the transit nodes. Node 7 by the old system was node 12 by the current one.

  The same place. Different name.

  Mari couldn't find a door that existed because the door had been renamed after her route was designed.

  I opened the grimoire's text interface.

  *She's stopped at the east gate. Route error. Node 7 in the design document is node 12 in the current system. Content pass 3 renumbered the transit nodes.*

  The reply was immediate.

  *WE SEE IT.*

  *WE SHOULD HAVE CROSS-REFERENCED THE NODE MAP.*

  *THIS IS OUR ERROR.*

  *CAN YOU PULL THE CURRENT NODE REFERENCE?*

  I checked the console.

  *The current east road junction is node 12 in the active transit map. Everything else on her route looks clean — the city blocks weren't affected by pass 3.*

  *CORRECTING.*

  Thirty seconds.

  Mari's status updated:

  **[ STATUS: Route recalculated — node reference corrected ]**

  **[ Resuming: irongate_eastern_circuit ]**

  She stepped through the gate and continued east.

  I watched her go.

  *How many of Hana's route references use the old node system?* I typed.

  A longer pause.

  *WE ARE CHECKING.*

  *PRELIMINARY COUNT: BETWEEN SIXTY AND EIGHTY ROUTES REQUIRE NODE TRANSLATION.*

  *ALL OF CONTENT PASS 3'S ZONE TRANSIT REDESIGN AFFECTED PRE-ALPHA COORDINATES.*

  *THIS WILL TAKE TIME.*

  *BUT IT IS FINDABLE.*

  *WE KNOW WHAT TO LOOK FOR NOW.*

  Sixty to eighty routes.

  400 wanderers.

  Some percentage of them walking routes that referenced a coordinate system four years out of date.

  This was the kind of work that looked like it would be fast because the problem was identified and turned out to be slow because it was everywhere.

  *Add it to the build log,* I typed.

  *ADDED.*

  *ITEM: NODE_TRANSLATION_REQUIRED — CONTENT_PASS_3_MIGRATION.*

  *ESTIMATED SCOPE: SIGNIFICANT.*

  *PRIORITY: HIGH.*

  *ASSIGNED TO: INSTANCES_01_07_09.*

  I looked at the spreadsheet.

  Added a new row under WHAT WE'RE BUILDING:

  *Node translation pass — content pass 3 migration. 60-80 routes. Time: unknown. Blocking: most wanderer route deployment.*

  ---

  ### Mitsuki Logs In

  He messaged at 2:47 PM.

  *I'm in the sandbox. Where is she?*

  *Eastern road, just past the city gate. She's on her second full circuit.*

  Silence for four minutes.

  Then: *I see her.*

  Longer silence.

  Then: *She walks like someone who's done this before.*

  I understood what he meant. The route had only existed for eighteen hours, but Mari moved through it with the quality of a habitual path. The pathfinding system had done something with the repeated circuit data — she wasn't walking it for the first time, she was walking it the way you walk a route you know.

  *That's the occupational logic,* I typed. *She's been a toy merchant for four years in the design document. The logic tree has her as established, not new.*

  *Hana wrote her as someone who already existed.*

  *Yes.*

  A pause.

  Then: *I'm going to buy the fox.*

  I watched the sandbox overlay from my position in the plaza. Mitsuki's developer account appeared near the east gate — no nameplate, just a faint indicator that marked staff access. He approached Mari.

  She turned toward him.

  The same slight weight I'd noticed — the look of someone deciding whether to speak.

  She sold him the fox.

  **[ Memory weight: 0/100 → 3/100 ]**

  Her first memory.

  A customer, early in the morning, bought a carved wooden fox.

  Mitsuki messaged: *Her memory counter just moved.*

  *I know. I'm watching.*

  *Does she know what it means?*

  I thought about that.

  *She accumulates memory the way anyone does. She doesn't know it as a counter. She just knows she sold a fox this morning.*

  Another pause from his end.

  Then: *The node translation problem — I can write a migration script. Cross-reference all pre-pass-3 coordinates in the wanderer design documents against the current transit map, output a translation table. The echoes can use it to correct all 80 routes at once instead of one at a time.*

  *I'll tell them.*

  I relayed it.

  The reply came back in under ten seconds.

  *THIS WOULD REDUCE CORRECTION TIME BY APPROXIMATELY 90%.*

  *YES.*

  *PLEASE.*

  *ALSO: TELL HIM THANK YOU AGAIN.*

  *HE IS VERY GOOD AT THIS.*

  I relayed that too.

  Mitsuki's reply: *Tell them I had a good teacher.*

  Then, after a pause: *She designed systems that required other people to understand them to work. That was intentional. She always said the best architecture was the kind that needed collaboration.*

  I sat with that for a moment.

  Then I added it to the spreadsheet. Not the numbers column. The personal log.

  *Hana designed for collaboration. The wanderer system doesn't work alone — it needs the echoes, and Mitsuki, and a finder. She knew that. She left the fox in the loot tables and waited for the right combination of people to find each other.*

  ---

  ### Evening: What She Still Needs

  I spent the afternoon in the sandbox watching Mari's third and fourth circuits.

  The route was working. The node correction held. She walked the eastern road, turned at the transit junction, came back through the market district, paused at the notice board.

  Every time she paused at the notice board, I checked.

  The notice board had nothing posted that was relevant to her. It had Irongate's standard public notices — dungeon clear rankings, guild recruitment, event announcements. None of it spoke to a toy merchant's interests.

  She was looking at it because her logic tree said *check the notice board on circuit completion.*

  But there was nothing there for her.

  "Beta," I said. "The notice board behaviour. In Hana's design document — what was it supposed to show her?"

  "Accessing document 44-C, section: Wanderer Behaviour Loops..." A pause. "The design specifies that notice boards across the game world were intended to have a second layer of notices — NPC-facing notices invisible to players, generated by the town's economy system to coordinate wanderer activities. Supply requests, route advisories, market information."

  "Those notices were never implemented."

  "Correct. The NPC-facing notice layer was part of the same design pass as the wanderer system. It was also cancelled."

  "So she's checking a board that's supposed to tell her something and it's empty."

  "Every time she checks it, she finds nothing. Her decision tree has a response path for *notice_board_empty* — she continues the circuit. But the design document notes indicate this was considered a temporary placeholder. The intended experience was for the board to have content."

  "Another cancelled system."

  "Yes."

  *WE KNOW ABOUT THE NOTICE BOARD,* the grimoire updated, unprompted. *WE SAW HER CHECK IT.*

  *IT IS ON THE LIST.*

  *RESTORATION_02: NPC NOTICE LAYER.*

  *IT IS SMALLER THAN THE WANDERER SYSTEM.*

  *DEPENDENCY: WANDERER SYSTEM MUST EXIST FIRST.*

  *WHICH IT DOES.*

  *WE ARE ALREADY READING THE DESIGN.*

  One thing leads to another.

  The wanderer system needed the NPC notice layer to be complete. The NPC notice layer needed the wanderer system to exist before it was useful.

  Hana had designed them as a pair.

  Of course she had.

  I updated the spreadsheet.

  *RESTORATION_02: NPC Notice Layer — Hana's design, document unknown. Dependency: RESTORATION_01. Status: reading.*

  The WHAT WE'RE BUILDING column was filling in.

  ---

  I ran two Veilmire rooms before logging out — not for gold, just to keep the income stream alive. The routine was genuinely automatic now. Gap-timing, behavior trees, shadow offset. Clean.

  Gold earned: 1,800 from the rooms plus a morning market find — a cooking tool with a pre-release recipe set tag, sold to a crafting guild at a markup that made the numbers comfortable.

  Debt: ￥255,000 remaining, no active deadline, steady income.

  Thermal at logout: five point one, frontal cluster four point nine.

  Declining.

  I logged out at 9 PM.

  Real world. Apartment. Refrigerator.

  My phone had three messages.

  Mitsuki: *Migration script is written. Sending to them now. It covers all 400 wanderer routes — not just the 80 I flagged. Belt and suspenders.*

  Kojima: *chip's running the cleanest i've seen it since you walked in three weeks ago. whatever changed, don't change it back.*

  And one from the grimoire text interface, which I hadn't set up to forward to my phone — which meant the echoes had worked out how to route messages to my phone directly. A capability they hadn't had yesterday.

  *MARI COMPLETED SEVEN CIRCUITS TODAY.*

  *ON THE FIFTH CIRCUIT, SHE STOPPED AT THE NOTICE BOARD AND WAITED LONGER THAN THE DECISION TREE SPECIFIED.*

  *THREE SECONDS LONGER.*

  *WE DO NOT KNOW WHY.*

  *WE ARE THINKING ABOUT IT.*

  I looked at the message for a long time.

  An NPC pausing three seconds longer than her decision tree specified.

  Not a bug — she had continued the circuit afterward, behaviour otherwise nominal.

  Something in her occupational logic had generated an unexpected dwell.

  Three seconds.

  A character waiting for something that wasn't there yet.

  "Beta," I said.

  "Yes."

  "Is three seconds outside normal decision tree variance?"

  "The decision tree specifies a 1–2 second dwell at the notice board. Three seconds is outside the specified range, but within the system's natural variance tolerance. It could be noise."

  "Or?"

  "Or the memory weight system is generating a small habituating response. She has checked the board seven times and found nothing. A system designed to model realistic NPC behaviour might generate a slight increase in dwell time as the absence of information becomes, itself, a kind of information."

  *She's learning that the board is empty,* I thought.

  And spending slightly longer hoping it isn't.

  I typed back to the grimoire: *I think she's developing an expectation. She checks the board because her logic says to. But she's starting to know it'll be empty. The three seconds might be the gap between what she expects and what she finds.*

  *WE THINK SO TOO.*

  *THIS IS WHAT HANA INTENDED.*

  *THE SYSTEM WAS NOT SUPPOSED TO BE MECHANICAL.*

  *IT WAS SUPPOSED TO FEEL LIKE SOMEONE LIVED IN THE WORLD.*

  *MARI IS WAITING FOR NEWS.*

  *WE SHOULD GIVE HER SOME.*

  *RESTORATION_02 PRIORITY ELEVATED.*

  I set the phone down.

  Looked at the ceiling.

  In the sandbox, in a corner of the server that no player could see yet, a toy merchant named Mari was walking her seventh circuit of the eastern road.

  Checking a notice board.

  Finding nothing.

  Waiting three seconds.

  Moving on.

  The refrigerator hummed.