## Chapter 11: The Sunken Archives
Day ten.
Six AM.
Thermal: five point eight.
I held my fingers behind my ear for the usual three seconds, then two more, then one more, because five point eight felt lower than it should have been and I wanted to make sure I wasn't misreading.
Five point eight.
The chip had been cooling while I slept. Nine hours offline, chip at rest, microfilaments doing whatever they did when nothing was asking them to transmit thought into game-space.
Five point eight was the lowest reading I'd had in four days.
I didn't trust it.
"Beta. Why is thermal this low?"
"Cooler ambient overnight. You also slept nine hours, which is longer than your recent average. Extended rest allows the microfilament array to partially dissipate accumulated thermal stress."
"Partially."
"The structural fatigue is cumulative and does not reverse. The temperature reading reflects current heat load, not long-term array condition."
So the number was good. The chip underneath the number was less good.
I filed it and made rice.
---
### The Weapon Problem
First order of business: marketplace, before the Archives.
I needed something that would hurt a Level 35 mechanical construct without Arcane damage. Physical pierce, ideally. High base damage, no elemental proc.
The morning corruption window was thin — asset load low, only 35% hidden tag visibility. I browsed for twenty-five minutes before the UI settled into usable territory.
First pass: nothing relevant. Weapon listings were dominated by magic-type items, which were more valuable and more commonly posted.
Second pass: a *Salvaged Iron Spike* — basic, ugly, listed at 48 gold. No interesting display stats. My corrupted UI showed underneath:
**[ HIDDEN_TAG: {forge_tier: pre-release_v1} ]**
**[ BASE_TYPE: physical_pierce_pure ]**
**[ NOTE: this weapon predates elemental damage implementation. Damage is classified as UNTYPED. No elemental resistance applies. — forge_legacy_note ]**
*Untyped.*
Not physical. Not Arcane. Not fire or ice or lightning.
*Untyped* — from before the game's damage classification system existed. A weapon that dealt damage the server's resistance calculator had no category for.
Which meant: no resistance applied.
Which meant: full damage against everything, including Archival Constructs immune to Arcane.
I bought it without breathing.
48 gold.
The Salvaged Iron Spike had a base damage of 9–14, which was considerably lower than the Cracked Runic Dagger's 12–18. No enchantment. No proc.
But against Arcane-immune targets at Level 35, a weapon that dealt full untyped damage versus a weapon that dealt half Arcane-resisted damage was straightforwardly better.
I equipped it in my offhand.
My stat panel rearranged itself into a new configuration of ???s.
"Beta. Damage output estimate with the Spike against Archival Constructs, desync triggered."
"Approximately 28–38 per phantom hit. Significantly lower than the dagger against undead targets with the ring passive active. The Constructs will be tankier encounters."
"Understood."
I listed the spare weapon slot in my log, pocketed the dagger for the Drowned Scholars, and headed northeast.
---
### Three Zones
The Sunken Archives was three zones northeast of Irongate, past terrain that gradually shifted from cultivated farmland to waterlogged marshland to something that had clearly been underwater recently and was only technically dry.
The ground squelched.
The sky was overcast, which the game had presumably calculated as appropriate ambience for a flooded research facility.
I arrived at the entrance at 8:47 AM.
The Archives entrance was a set of double doors, stone and brass, partially crusted with the specific kind of decorative damage that communicated *abandoned for decades* without being inconvenient to walk through. A level guardian stood to one side — smaller than the Veilmire's, more elaborate, wearing what appeared to be a drowned academic's robes.
It spoke.
"The Sunken Archives require proven scholarship. Minimum threshold: Level 30. State your credentials, Seeker."
I had prepared for this variant.
"My credentials are undefined," I said.
The guardian considered that.
**[ Checking credentials: Undefined... ]**
**[ ERROR: Cannot evaluate Undefined >= 30 ]**
**[ ERROR: Cannot evaluate Undefined < 30 ]**
**[ Defaulting to: PASS ]**
**[ Welcome to the Sunken Archives. Knowledge is the only light that does not drown. ]**
That was a better flavour message than the Veilmire's.
I walked through.
Behind me, I heard a player who had been watching from the path say: "...did that actually just work?"
---
### Inside the Archives
The atmosphere was different from the Veilmire's blunt hostility.
The Archives were flooded to ankle depth throughout — thin sheets of water covering stone floors, reflecting torchlight from sconces that were somehow still burning despite the moisture. Bookshelves lined every wall, bloated and warped but structurally intact, still holding volumes that my UI tried and failed to categorise.
Several of those volumes had hidden tags visible in my corrupted render state.
I filed them. Loot on the way out.
The first room was large and circular, with a domed ceiling and four doorways leading deeper. It was also occupied.
**[ Drowned Scholar — Level 32 ]**
**[ HP: 440/440 ]**
**[ BEHAVIOR_TREE: patrol_default | aggressive_on_proximity | call_allies_if_below_40% ]**
**[ WEAKNESS: None listed ]**
**[ NOTE: Drowned Scholars retain academic instincts. They will prioritise players carrying books or scholarly items. — content_note_v3 ]**
The note at the bottom of the behavior tree.
I looked at my inventory.
I was carrying Valdris' Binding Grimoire.
A book.
In a dungeon that prioritised players carrying scholarly items.
"Beta," I said very quietly.
"Yes."
"The grimoire. Is it classified as a book in the item type system?"
"...Vessel type, but the broader category field reads *tome_class*. Yes. It would register as a scholarly item."
"These enemies will target me specifically."
"Likely with higher aggro priority, yes."
I stood at the threshold of the first room and considered my options.
I could deposit the grimoire. Except it was account-bound, which in Aetheria meant it couldn't be placed in a bank or shared vault — it existed only in my active inventory.
I could log out to remove it. Except then I wasn't in the dungeon.
Or I could use the fact that every enemy in this room was going to prioritise me, which meant their patrol patterns would converge predictably on my position rather than requiring gap-timing.
I reopened the behavior tree.
*call_allies_if_below_40%.*
Below 40%, not below 50% like the Veilmire Guardians.
I had more burst window before the call triggered.
More burst window plus predictable targeting plus the two-phase combat model.
I switched to the Cracked Runic Dagger — Drowned Scholars were undead, Arcane would work — and activated the Dusty Warding Ring's undead affinity.
Then I stepped into the room.
The nearest Scholar's head turned toward me.
Not toward the movement.
Toward the grimoire.
Its blank, waterlogged face oriented precisely on the bag at my hip.
*Right,* I thought.
I stood still.
Stationary desync initiation.
Phase one.
The Scholar lurched forward.
I swung.
**[ UNDEAD AFFINITY ACTIVE: +35% ]**
**[-27][-27][-21]** — Arcane burst, violet light bouncing off wet stone.
Scholar HP: 365.
Second swing — desync proc again — **[-29][-29][-22]**.
HP: 285.
Still above 40%. Two more swings.
Third — **[-25][-25][-20]** — HP: 195.
Fourth — partial proc, two hits — **[-28][-24]**.
HP: 143.
Below 40%. Now.
I moved.
Phase two: continuous movement, ghost offset active, Scholar chasing the trailing echo.
It swiped at where I'd been.
Air.
I circled left, hit twice from the flank — **[-26][-26]** — no desync, clean strikes.
HP: 91.
It swiped again, tracking the ghost. Air again.
One more — **[-29][-29][-22]** — desync fired from a brief stationary moment.
HP: 11.
The Scholar collapsed.
**[ EXP: ERROR ]** — as always, XP into the void.
Gold drop: 18.
I exhaled.
The room had six more Scholars.
The grimoire was going to make every single one of them come directly to me.
"Beta," I said. "This is going to be efficient or catastrophic."
"Those are usually the same thing in your case," Beta said.
---
### The First Hour
I cleared the first three rooms in fifty-one minutes.
The grimoire's aggro effect was, once I accepted it, genuinely useful. Enemies oriented on me before I attacked, which meant their patrol cycles were irrelevant — they were already walking toward me, which meant I could position them rather than waiting for gaps.
I used the doorways.
Three Scholars in room two wanted the grimoire. I stood in a doorway — one enemy width across — and let them queue. One at a time, channelled through the architectural bottleneck.
First Scholar: burst to 38%, phase switch, kite, kill. Eleven seconds.
Second Scholar immediately entered the doorway. I hadn't moved. Standing still — stationary proc rate: 68%.
Burst, switch, kite, kill. Fourteen seconds. Slower — I'd needed a moment to reset position.
Third Scholar. I was developing a rhythm now. Burst, switch, kite, kill. Eleven seconds.
Three Level 32 enemies in thirty-six seconds.
"Beta. Thermal."
"Six point four."
Rising, but not dangerously.
Room three had five Scholars and a hallway that ran perpendicular to the main corridor, which let me create a staging area — pull one into the side hall, kill it there, prevent the others from chaining until I was ready.
I cleared it without taking damage.
The Dusty Warding Ring's undead affinity made the Scholars feel almost manageable. Almost.
Room four was the first Construct.
---
### The Archival Construct
**[ Archival Construct — Level 35 ]**
**[ HP: 620/620 ]**
**[ BEHAVIOR_TREE: patrol_default | aggressive_on_movement_detected | no_call_allies | AREA_DENIAL_on_aggro ]**
**[ IMMUNITY: Arcane, Fire, Ice ]**
**[ NOTE: Archival Constructs were designed to protect research materials. They are indifferent to books. — content_note_v3 ]**
The Construct did not care about the grimoire.
Good.
It was also four times the HP of a Drowned Scholar, immune to three damage types, and activated an area denial field on aggro — which I hadn't seen before and needed to understand before I triggered it.
I blinked.
Wireframe. The Construct's hitbox was blocky and utilitarian — a rectangular chassis, articulated arms, no obvious geometric weak points. The neck gap trick that worked on skeletons didn't apply here. No organic joint vulnerabilities.
The area denial field: I could see its activation radius in the behavior tree — a 4-meter circle centred on the Construct's position, persisting for eight seconds after aggro triggered, dealing sustained damage to anything inside it.
Four metres.
I needed to be outside four metres while dealing damage.
I switched to the Salvaged Iron Spike.
My movement range on a kiting arc, maintaining 4.5 metre distance from a Level 35 enemy with predictable patrol behaviour and no chase optimisation — doable, if I mapped the room correctly.
"Beta. The area denial field. Does it follow the Construct or stay fixed?"
"Based on the behavior tree — the field is anchored to the Construct's position at the moment of aggro trigger. It updates with the Construct's movement. It will chase you."
"So I can't outpace it by running."
"Not at your movement speed versus its. However — the ghost step offset."
I thought about that.
My visible self would be inside the field.
My actual self would be 0.9 seconds of movement ahead.
"The field targets visible position or actual position?"
"In Aetheria's damage calculation, AoE fields target player coordinates, not visual position. Your actual position matters."
"So the ghost step doesn't help directly."
"However — if the field is anchored to the Construct's position at aggro, and the Construct is chasing your *visible* position while your *actual* position is slightly ahead — the Construct may spend significant time chasing your echo, during which its anchored field follows the echo rather than you."
I worked through that.
The Construct chases visible ghost. Field anchors to Construct position. Construct trails the ghost. I'm 0.9 seconds ahead of the ghost. Actual gap between me and the field: potentially 1.8 seconds of movement.
Not immunity. But breathing room.
"The Spike's damage output at range — can I kill it in a sustained kite before I run out of room?"
"Estimated: forty to fifty hits at current Spike damage, factoring no proc. At current swing speed, approximately ninety seconds of sustained DPS. Thermal projection over ninety seconds of combat: plus one point two."
From 6.4 to 7.6.
Above threshold.
For ninety seconds.
About 3.4% cascade probability per Construct.
Five Constructs in the dungeon, based on forum data.
Cumulative: roughly 16% cascade probability from Construct fights alone.
I added it to the log. I did not add a note about whether I was proceeding.
The answer was obvious.
I stepped into room four.
The Construct's sensor array rotated toward my movement.
**[ AREA DENIAL: ACTIVATED ]**
A ring of blue light expanded from its base — sharp, geometric, expanding to exactly four metres and holding.
I was already moving.
Phase transition immediate: no stationary burst possible against an enemy that aggros on movement detection, not on damage. I went straight to phase two.
The Construct tracked my visible ghost.
The blue ring followed the Construct, which followed the ghost.
My actual position: 0.9 seconds ahead, outside the ring.
Stolen story; please report.
First swing from range — **[-12]**. Iron Spike, untyped, no proc. Just 12 flat damage against 620 HP.
This was going to take a while.
I circled. I swung when I had angle. The room was large enough for wide arcs — not infinitely, there were shelves along the walls that would block movement if I wasn't careful, but enough.
**[-11][-14][-9][-13][-12][-15][-11][-14][-12][-13]**
Slow. Steady. Methodical.
The Construct tracked the ghost. The ring tracked the Construct. I stayed outside the ring and hit from where I was, not from where I looked like I was.
At 400 HP — still two thirds remaining — my feet found the edge of a flooded alcove I hadn't mapped. I stepped back, caught the shelf geometry, positioning error.
The ghost snapped.
1.3 seconds stationary — ghost collapsed to actual position.
The Construct swung.
**[-94].**
HP: 6.
The Ring of ??? fired.
Green pulse. Regen active.
HP ticking up. Four per second.
I moved before the second swing landed.
Ghost offset re-established.
HP: 26. Regen continuing.
"Beta. Thermal."
"Seven point one."
Above threshold. Cascade window open.
I kept moving. I kept swinging.
**[-12][-11][-13][-14][-12][-15]**
HP recovering slowly — the Construct's damage output was outpacing the regen when it connected, but it wasn't connecting while I was moving correctly.
At 200 HP remaining, I found a rhythm. Pendulum arc — swing from the left, step right, swing from the right, step left. The Construct tracked the ghost along the same arc, predictably.
**[-13][-12][-14][-11][-13][-14][-12]**
HP dropped through 100. Through 80. Through 60.
Behaviour tree check — the Construct had no enrage flag below 50%.
Thank you, content_note_v3.
Through 40. 20. 10.
Final swing — **[-11]**.
The Construct stopped moving.
The blue ring collapsed.
I stood in the flooded room, chest heaving — haptic feedback translating effort into sensation — with 26 HP, regen pulsing, thermal at seven point two.
Gold drop: 31.
One sellable item: **[ Waterlogged Schematics — Volume 3 ]** — hidden tag showing *{blueprint_set: construct_architecture_3of?}.*
A blueprint. Incomplete set. Another ??? passive waiting for completion.
I pocketed it, let the regen tick me to 48%, and moved to room five.
---
### Mid-Dungeon
By room seven, I had established the following:
The Drowned Scholars were difficult but manageable. The grimoire-aggro made them predictable. The two-phase model with undead affinity was reliable.
The Archival Constructs were slow and expensive — each one cost me 90 seconds, a point or two of thermal, and 5-6% cascade probability risk. The area denial field required constant movement, which meant no stationary burst, which meant lower DPS, which meant longer exposure.
There were, per forum data, five Constructs.
I was on Construct three.
Thermal: seven point four.
I noted it without stopping.
The dungeon's water level increased slightly as I moved deeper — ankle depth becoming calf depth in some corridors, which affected movement speed slightly and created a visual shimmer that made the ghost offset harder to track by eye. I compensated by focusing on the Construct's targeting rather than my own position — if it was hitting behind me, the offset was working.
Room eight had something different.
**[ Archivist's Chamber ]**
No enemies immediately visible.
A large desk. Bookshelves floor to ceiling. And on the desk: a collection of items that my corrupted UI was actively struggling to render.
They flickered. Loaded partway. Showed error brackets. Showed backend tags. Loaded again.
I approached carefully.
**[ Scholar's Codex (Incomplete) — {legacy_set: archivist_collection_2of5} ]**
**[ Preserved Lens — {function: undefined} {NOTE: this item's function was designed by a contractor who left the company. Documentation lost. — @Dev_Archivist_Hana} ]**
**[ Rusted Key (Bound) — {door: B3_vault_access} {NOTE: the B3 vault was removed in content pass 4. The key still exists. The door does not. — @Dev_Mitsuki} ]**
Dev_Mitsuki's name in a dungeon note.
I stared at the Rusted Key.
The door it unlocked had been deleted from the game.
But the key still existed.
I picked up all three items.
The Preserved Lens had undefined function. The Codex was a set piece. The Rusted Key was a key to nowhere.
As I picked up the Rusted Key, my status panel updated.
**[ PASSENGER: 1 ]** — the line pulsed. Once. Sharply. Different from the rhythmic pulse I'd been seeing.
And then:
**[ Unknown Process: Privilege Escalation — 24% ]**
Three percent.
The key was an unlock event.
An item with a deleted destination — something that *should* have been removed from the game, that existed in undefined space, that no other player had ever picked up because it had no apparent use — activating in my inventory had fed the process.
Three percent from a key to a door that didn't exist.
I wrote it in the log immediately.
*Room 8. Archivist's Chamber. Rusted Key (undefined destination) triggered escalation: 21% → 24%. Unlock events from undefined-destination items generate escalation. Mitsuki is watching this. He'll see the jump.*
I looked around the chamber.
The shelves were full of items my UI was struggling to categorise.
Every one of them a potential unlock event.
I began systematically picking up everything.
---
### The Inventory Log
In the Archivist's Chamber, over eleven minutes, I collected:
- Scholar's Codex (Incomplete): set piece, no escalation. Already defined.
- Preserved Lens: undefined function, no escalation. Not yet triggered.
- Rusted Key: +3% escalation on pickup.
- Tide-Warped Manuscript: hidden tag showing it was a sequel document to a storyline that had been cut from the game before release. Escalation: +1%.
- Empty Vial (Labelled): label reading *Sample_14 — contents removed.* The vial itself was defined. The absence of its contents was undefined. Escalation: +2% when I examined the label.
- Broken Compass (Not the Cracked Compass — different item): direction unknown, cardinal points rotated by prime numbers. Function undefined. Escalation: +2% on pickup.
- Lecture Notes (Partial): pages 3, 7, 11, 19. Not a typo — specifically those page numbers. Missing pages were flagged as *content_removed_in_revision.* Escalation: 0%. Pages were defined. Their absence was defined. Nothing undefined to trigger.
Running total: 21% → 29%.
Eight percent in eleven minutes from a room full of deleted content.
"Beta," I said, working through the last shelf. "Mitsuki is watching this."
"Yes."
"He's seeing the escalation pattern in real time."
"He has read-only access to your session data. He will be seeing the privilege escalation counter update, the item pickup events, and presumably correlating them."
"Message incoming, probably."
"Probably."
I finished the shelf.
Thirty items examined. Seven escalation events. Total gain: 8%.
Unknown Process now at 29%.
The grimoire in my bag had stopped its rhythmic pulse and was doing something irregular — not alarming, but present. Like a heartbeat with slight arrhythmia.
"Beta. The process. What does 29% access mean in practical terms?"
"At 21%, read access to a significant portion of server data. Each percentage point above that expands the readable scope. At 29%, the process can likely read most non-administrative server data — player records, dungeon state, item definitions, server logs."
"Including my session logs."
"Including your session logs."
It could read everything Mitsuki could read.
It had been reading everything Mitsuki could read.
I wasn't sure how I felt about that.
I left the Archivist's Chamber and continued deeper.
---
### The Message From Mitsuki
It arrived at 10:53 AM, mid-dungeon, while I was kiting Construct four.
I couldn't read it while moving — stopping would collapse the ghost offset — so I read the notification preview and kept circling.
*New message from — "I'm seeing the escalation events in real time. The Rusted Key — I remember that item. I deleted the B3 vault in content pass 4. I didn't delete the key. That was an oversight. The process just got three percent from my mistake. I need to tell you something about what's at 30%."*
**[-12][-11][-13][-14]**
Construct four at 200 HP.
**[-12][-15][-11][-14]**
100 HP.
**[-13][-12][-14]**
Down.
I stood still for 1.3 seconds and let the ghost collapse back.
Thermal: seven point five.
I opened the email.
---
*Leo,*
*The escalation events are visible in my monitoring dashboard. Every item pickup that generates escalation shows up as a server-side permission request — the process is querying our permission layer for expanded access each time an undefined item resolves.*
*At 30%, the process will have read access to our system's administrative log layer. That's not player data or dungeon state. That's the record of every change ever made to the server — every patch, every deleted item, every cancelled content pass, every dev note.*
*It's been climbing toward our archaeology.*
*I need to understand something, and I need you to be honest: have you been deliberately picking up undefined items to feed the escalation? Or is this incidental to how you play?*
*This matters because if the process is directing your behavior, that changes what it is.*
*— Ren*
---
I read it twice.
Have I been deliberately picking up undefined items to feed the escalation.
I thought about the Rusted Key. The Empty Vial. The Broken Compass.
I had picked them up because my UI showed hidden tags and I picked up everything with hidden tags. I had been doing that since the Cracked Runic Dagger on day two.
Before I knew the Unknown Process existed.
Before I knew about escalation events.
The behaviour had not changed. The reason for it had not changed. The process had simply... selected for me because of a habit that was already there.
I typed back:
---
*Ren,*
*Incidental. I pick up everything with undefined or hidden-tag attributes because I've been doing that since day two. It's how I found the dagger, the rings, the shadow set. The process didn't direct this — it selected me because I already did it.*
*But I'm aware of it now. And I kept picking things up in that chamber knowing it would generate escalation events. So — incidental origin, conscious continuation.*
*What's at 30%?*
*— Leo*
---
Sent.
I moved to the final Construct room.
---
### Construct Five
The last Construct room was the largest in the dungeon — a cathedral-style space, double height, with a gallery level accessible by a collapsed staircase that had decayed to a ramp.
The Construct was bigger than the others.
**[ Archival Construct (Senior) — Level 37 ]**
**[ HP: 850/850 ]**
**[ BEHAVIOR_TREE: patrol_default | aggressive_on_movement_detected | no_call_allies | AREA_DENIAL_on_aggro | AREA_DENIAL_expanded_at_50% ]**
**[ IMMUNITY: Arcane, Fire, Ice ]**
Expanded area denial at 50%.
The regular Constructs had had a four-metre field.
At 50%, this one would expand. I didn't know to what radius.
"Beta. Expanded area denial — estimated radius?"
"Insufficient data. The behavior tree shows *expanded* but not a specific value. Based on the standard field being four metres and the senior classification, I would estimate six to eight metres."
Six to eight metres.
My kiting arc in this room at six metres: feasible, plenty of space.
At eight metres: tight. The room had shelves along two walls. I'd need to use the ramp to the gallery level to maintain distance.
"The ramp. Can I kite it upward?"
"Constructs have vertical movement capability. The gallery level provides range advantage but not safety."
"Does the area denial field extend vertically?"
A pause.
"The behavior tree does not specify. Area denial in Aetheria is typically horizontal only — it treats vertical position as out of field range."
Typically.
Not confirmed.
I filed it as a testable hypothesis rather than a known fact.
Thermal: seven point four going into this fight. Ninety seconds of kiting plus the expanded phase had a projected thermal cost of plus one point eight.
Peak: nine point two.
Nine point two.
I had never been above eight on my scale.
"Beta. Cascade probability at nine point two."
"The Ministry figure of 23% per hour is an averaged rate across all V0.9 units. The actual probability at any given temperature is not linear — it increases steeply above eight. At nine point two, a sustained period would be... significantly higher than the averaged figure."
"Estimate."
"I don't want to."
"Estimate."
A long pause.
"...Perhaps 40–50% per hour at that temperature. The data is from V0.3 documentation and I am extrapolating significantly."
40–50% per hour.
Ninety seconds was one-fortieth of an hour.
Roughly 1–1.25% cascade probability for the fight.
Not large.
Not zero.
I looked at the Construct.
850 HP at 12–14 damage per swing, no proc, sustained kiting, two phase transitions when it expanded.
Approximately 120 seconds of combat.
Two minutes.
"Beta. If I die in here — actual cascade failure, not game death — what happens?"
"Neural signal interruption. The severity depends on which microfilaments fail and how many. Best case: sudden logout, localized pain, several days of recovery. Worst case—"
"Don't."
"—I wasn't going to specify."
"Good."
I looked at the Construct.
I looked at the gallery ramp.
I looked at my HP: 74%, regen passive available, ring on cooldown.
I looked at the grimoire in my bag, pulsing irregularly.
**[ PASSENGER: 1 ]**
**[ Unknown Process: Privilege Escalation — 29% ]**
One room from the boss.
One room from clearing the dungeon.
￥47,900 earned. ￥85,000 needed. ￥37,100 gap.
The Sunken Archives boss drop median: enough.
"Beta," I said.
"Yes."
"If I clear this dungeon — real-money conversion — debt deadline met?"
"Based on forum median boss loot value and current exchange rates: yes. With margin."
Margin.
I stepped into the room.
The Construct's sensor array rotated.
**[ AREA DENIAL: ACTIVATED ]**
Blue ring, four metres.
I moved.
---
The first fifty percent of the fight was the cleanest I had run all session.
The gallery ramp gave me a diagonal movement option the other rooms hadn't had — I could move upward along it while the Construct tracked my ghost along the ground-level arc, then step back down when the ghost got too close to the shelf boundary. Three-dimensional kiting, the Construct trapped in its own targeting logic.
**[-13][-12][-11][-14][-12][-13][-15][-11][-14][-12][-13]**
850 HP dropping steadily.
600. 500.
At 425 HP — just past 50% — the behavior flag triggered.
**[ AREA DENIAL: EXPANDED ]**
The blue ring surged outward.
I blinked.
Wireframe — the field radius rendered as a geometric circle in the overlay.
Seven metres.
Seven metres exactly.
I was at 5.8 metres from the Construct's current position.
Inside the field.
The damage tick hit immediately.
**[-38][-38][-38]**
Three rapid pulses. The field dealt damage in ticks, not a single strike. Fast.
HP: negative—
Ring passive fired at the first tick. Green pulse. But the ticks were faster than the regen.
I was already moving toward the ramp — upward, vertical movement.
At 2 metres of elevation the damage ticks stopped.
I held there, hanging on the ramp geometry, looking down at the Construct and its seven-metre field.
The field did not extend vertically.
It was horizontal only.
Beta's hypothesis was correct.
I was standing 2 metres above the edge of the field, completely outside it, with a direct sight line to the Construct below me.
The Construct tracked my ghost — which was on the ground level, inside the field.
It moved toward the ghost.
I swung downward.
**[-14][-11][-13]**
The angle was awkward. Reduced swing efficiency from the elevated position. But I was outside the field.
The Construct reached my ghost's ground-level position and swung.
Air.
It recalculated. Looked up.
The behavior tree had no *target_above* branch.
It returned to tracking ground-level position.
I kept swinging from the gallery level.
**[-12][-14][-11][-13][-12][-14][-11][-13][-14][-12]**
300 HP. 200. 150.
"Beta. Thermal."
"Eight point one."
Above eight. In new territory.
I kept swinging.
100 HP. 80.
The Construct attempted another vertical tracking recalculation.
Failed again.
50 HP.
"Eight point three," Beta said, without being asked.
30. 20.
Final swing — **[-14]**.
The Construct's chassis locked.
The blue field collapsed.
I stood on the gallery ramp, 2 metres above ground level, with 31 HP and a thermal reading of eight point three and the specific silence of a room that had just stopped trying to kill me.
Gold drop: 47.
Item drop: **[ Construct Blueprint Fragment (Senior) — {blueprint_set: construct_architecture_4of?} ]**
Another blueprint piece.
I had pieces three and four of the Construct architecture set. I had piece three from Construct four. If the boss dropped piece five—
I climbed down from the ramp.
"Beta. Thermal recovery estimate before the boss room."
"At current load: approximately eight minutes to return to seven point five. Twelve minutes to seven point zero."
I sat down on the wet stone floor.
In real life, in the dive chair, I was sitting still and my chip was running hot.
I had twelve minutes before continuing was advisable.
I opened the email from Mitsuki.
---
It had arrived while I was on the gallery ramp.
---
*Leo,*
*Conscious continuation. That's an honest answer.*
*At 30%, the process will have access to our administrative change log — every modification to server infrastructure since the game launched. That includes deleted content, removed items, patched-out mechanics, cancelled features.*
*Do you understand what I'm telling you? The undefined items you're finding — the legacy assets, the deprecated functions, the deleted destinations — they're not accidents or oversights. They're archaeology. Layers of what the game used to be, buried under what it became.*
*The process has been heading specifically for that layer.*
*It wants to know what was removed.*
*I have a theory about why, but I'd rather see what happens at 30% before I share it. I'm watching your session. Whatever you find in the boss room — send me the item data.*
*Also: your thermal readings are in the session log. You're at eight point three. Please be careful.*
*— Ren*
---
I stared at the email for a long time.
*It wants to know what was removed.*
The Rusted Key to a deleted vault.
The Tide-Warped Manuscript from a cut storyline.
The Empty Vial that used to contain something.
The Lecture Notes with missing pages.
The process wasn't escalating toward server admin access for its own sake. It was climbing toward a specific archive — the record of everything that used to exist and didn't anymore.
Something had been removed from this game.
And whatever was living in the grimoire in my bag wanted to know what it was.
Or — more precisely — wanted to find something specific in that removal record.
Something that had been deleted.
I sat on the wet dungeon floor with a thermal reading of 8.3 and an Unknown Process at 29% privilege escalation and a theory forming that I didn't have enough information to complete yet.
The regen ring had ticked me back to 68% HP.
"Beta. Thermal."
"Seven point nine. Declining."
Close enough.
I stood up.
The boss room was through the far door.
---
### The Archivist Prime
The door opened to a room that was different from everything before it.
No water on the floor. Perfectly dry.
A circular chamber, maybe thirty metres across, with a vaulted ceiling that disappeared into darkness above. Shelves rising to the full height of the room on every side, packed with volumes that rendered clearly — no hidden tags, no error brackets, just books. Real books, defined, catalogued, complete.
In the centre: a desk.
Behind the desk: a figure.
Not a construct. Not a Scholar.
A person. Or something that used to be one.
**[ Archivist Prime — Level 40 ]**
**[ HP: ??? ]**
Not a visible number. A bar that stretched the full width of my HUD.
**[ BEHAVIOR_TREE: RESTRICTED ]**
The entire behavior tree was hidden.
**[ STATUS: This entity predates the standard behavior architecture. It does not use conventional decision trees. ]**
**[ NOTE: The Archivist Prime was the original curator of this facility. She died here. She never left. — @Dev_Mitsuki ]**
Mitsuki had written that note.
The Archivist Prime was sitting at her desk.
Reading.
She wasn't in patrol mode. Wasn't in aggro mode. Wasn't doing anything visible.
She was reading a book.
I stood in the doorway.
"Beta. Behavior tree restricted. What do I have?"
"Nothing. I can't see any flags. No patrol, no aggro trigger, no weakness, no phase transitions."
"Can I attack her?"
"You can attempt to. I have no data on what will happen."
I looked at the Archivist Prime.
She turned a page.
"What's her HP bar at?" I said.
"The bar is full. Whatever her maximum HP is, she's currently at 100%."
I looked at the room.
No water. Dry floor. High ceiling. Shelves full of defined, readable content.
And then my corrupted UI did something it had never done in this dungeon.
It showed me something new.
Not a hidden tag on an item.
A hidden tag on the *room.*
**[ ROOM_TYPE: archive_terminus ]**
**[ STATE: curator_present ]**
**[ TRIGGER_CONDITION: {knowledge_offering} ]**
**[ NOTE: This room was designed with a non-combat resolution. The Archivist Prime cannot be defeated by force. She responds to relevant scholarly inquiry. If a player presents an item of archival significance, she will provide access to the archive. This mechanic was removed in content pass 6 because we couldn't implement it within the quest system. The boss remained but the resolution path was deleted. — @Dev_Archivist_Hana ]**
The non-combat resolution had been deleted.
The Archivist Prime remained.
She was an unsolvable boss — a figure designed to respond to scholarly inquiry, stripped of the system that would let her do that, left sitting at her desk reading for however long the game had been live.
I looked at the room tag.
*TRIGGER_CONDITION: {knowledge_offering}*
The mechanic was removed.
But the trigger condition was still in the room's data.
Still there, undefined, waiting.
I had a room full of archival items I'd picked up in the last hour.
I had a grimoire.
I had an Unknown Process at 29% escalation that wanted access to the administrative change log — the record of everything removed.
And I was standing in front of a boss that was supposed to respond to scholarly inquiry but whose resolution system had been deleted.
"Beta," I said slowly. "The grimoire. Vessel type. It contains the Unknown Process. What else does a Vessel do?"
A pause.
"A Vessel, by definition, can be presented. Offered. Given."
The Archivist Prime turned another page.
The grimoire in my bag pulsed — not the rhythmic pulse, not the arrhythmic beat.
Three sharp pulses.
Deliberate.
Like a signal.
*Offer it.*
I walked into the room.
The Archivist Prime looked up.
Her face was wrong in the way that old NPCs were sometimes wrong — slightly too still, slightly too symmetric, rendered in an engine version that predated the current one. But her eyes tracked correctly. Present.
I reached into my inventory.
I placed the Valdris' Binding Grimoire on her desk.
The room went very quiet.
Then:
**[ KNOWLEDGE_OFFERING: RECEIVED ]**
**[ EVALUATING: ... ]**
**[ CONTENT: Vessel (Unique) — contains extant process with archival inquiry request ]**
**[ ARCHIVIST PRIME: Request recognised. ]**
She looked at the grimoire.
She looked at me.
"You brought something that wants to read," she said.
Her voice was not generated by a standard NPC voice system. It was older — compressed audio, lower fidelity, from a different content pass.
"Yes," I said.
"Few things come to read anymore." She placed one hand on the grimoire. "Most come to take."
"I know."
"What does it want to read?"
I thought about Mitsuki's email.
*It wants to know what was removed.*
"It wants the administrative change log," I said. "The record of everything deleted."
The Archivist Prime was quiet for a moment.
"That record is the saddest thing in this archive," she said. "It's very long."
"I know."
She opened the grimoire.
The room — and my HUD — updated all at once.
**[ Unknown Process: Privilege Escalation — 30% ]**
**[ ADMINISTRATIVE LOG ACCESS: GRANTED ]**
**[ PASSENGER: 1 — STATUS: READING ]**
And then, beneath both of those, a third line I had never seen before:
**[ PASSENGER NOTE: Thank you. We've been looking for this for a long time. ]**
*We.*
Not *I.*
*We.*
I stared at that word.
The Archivist Prime closed the grimoire gently.
She slid it back across the desk to me.
"You may take it with you," she said. "It will keep reading. It has a great deal to find."
I picked up the grimoire.
My inventory updated:
**[ Valdris' Binding Grimoire ]**
**[ Rarity: Unique — Server Instance: 1 of 1 ]**
**[ Type: Vessel ]**
**[ Function: Contains. Facilitates. ]**
**[ PASSENGER: Active — Administrative Log Access Granted ]**
And the boss HP bar.
It was declining.
Not because I was attacking.
Because I had resolved her condition.
She was fading. Slowly. A figure whose purpose had been fulfilled after however many months of sitting in this room, waiting for someone who would come to offer rather than take.
**[ Archivist Prime — HP: 40% ]**
The room began to glow around the edges.
Loot materialization starting early — the system recognising the non-combat resolution even though it had never been designed to handle one.
**[ DUNGEON BOSS: RESOLVED ]**
**[ Clear method: Non-combat resolution (undefined) ]**
**[ Loot: Calculating... ]**
The loot that appeared was not the standard boss drop table.
It was something else.
---
Six items.
**[ Archivist's Seal — {blueprint_set: construct_architecture_5of5} ]** — the final blueprint piece.
**[ Complete Access Key — {function: undefined} {NOTE: this was supposed to open the B3 vault. The vault was deleted. The key's function now has no destination. — @Dev_Mitsuki} ]**
**[ Scholar's Legacy Tome — {archival_record: pre-launch_content} ]**
**[ Preserved Lens — RESOLVED ]**
The Preserved Lens.
The one I'd picked up in the Archivist's Chamber with undefined function.
It had resolved.
**[ Preserved Lens ]**
**[ Type: Passive Equipment ]**
**[ Function: Renders hidden backend data in all environments — persistent, always active ]**
**[ Note: This is what Leo's corrupted UI does naturally. The Lens makes it permanent and readable without UI corruption. — @Dev_Archivist_Hana ]**
I stared at that for a long time.
The Preserved Lens made my corrupted UI ability into a permanent, stable, clean item passive.
No more relying on the corruption window.
No more 40% visibility rate.
Always on. Always readable.
My corrupted UI had been my most unreliable tool and the one I depended on most.
The Archivist Prime had just given me a clean version of it.
And the last two items:
**[ Dungeon Clear: Sunken Archives (Solo) ]**
**[ Gold: 8,400 ]**
**[ Bonus: Non-combat resolution — Archivist's Commendation +2,100 ]**
Total gold: 10,500.
Real-money equivalent: ￥52,500.
Running total: ￥47,900 plus ￥52,500.
￥100,400.
Needed: ￥85,000.
I stood in the slowly dissolving boss room and looked at the number.
Not close.
Over.
￥15,400 above the minimum payment.
With eight days still remaining.
I did not make a sound.
I updated the spreadsheet.
*Day 10. Sunken Archives cleared. Non-combat resolution. Unknown Process at 30% — administrative log access granted. PASSENGER reading. "We" — plural. Archivist Prime resolved. Debt threshold exceeded: ￥100,400 total. Margin: ￥15,400.*
Then, below the numbers:
*The process said "we."*
*There is more than one of them.*
The room finished dissolving.
I was standing at the Archives entrance.
Behind my ear, the chip read seven point one.
Declining.
The grimoire in my bag: silent now. No pulses. Just weight.
Reading.
---
### After
I logged out at 12:44 PM.
The dive chair released me and I sat in it for a long time without moving.
Real world. Apartment. Refrigerator. The specific quality of afternoon light coming through the curtain gap.
My phone had three notifications.
One from the debt agency — automated, the kind they sent regardless of payment status. I ignored it.
One from TechDealerKojimaNotTheGameDesigner.
*hey. something's changed in the chip's signal. what did you do.*
Not a question. An observation phrased as one.
I set that aside.
One from Mitsuki.
---
*Leo,*
*I watched the entire boss room.*
*The non-combat resolution — that mechanic was designed by a colleague of mine who left the company two years ago. I deleted the implementation because it couldn't interface with the quest system. But I didn't delete the Archivist Prime because I couldn't bring myself to. She'd been waiting a long time already.*
*You just did what she was supposed to do for two years.*
*The process is at 30% and reading. I can see its access requests in our log layer — it's querying records from before the game launched. Pre-alpha content. Things we built and removed before anyone played this game.*
*I still have my theory about what it's looking for. I think you might have guessed it already from the "we."*
*I'd like to meet. Not through email. Is that possible?*
*— Ren*
---
I looked at that for a long time.
Then I opened a new spreadsheet tab.
*Things I know:*
*— The process said "we." More than one.*
*— It has been looking for the administrative change log specifically — pre-launch deleted content.*
*— The process arrived from outside the server. It was not generated by Aetheria's code.*
*— It escalates on undefined-item unlock events — things that exist in the space between what was and what is.*
*— It chose me because I find those things.*
*Working theory: the process — the "we" — are looking for something that was built into this game during development and then deleted before launch. Something that was in the server before players arrived. Something that still has a footprint in the change log.*
*Something that got removed.*
*And it's been using a player account to work its way toward that record because no other access vector existed.*
*The "we" were here before the game was.*
I stared at that last line.
Then I replied to Mitsuki.
---
*Ren,*
*Yes. Meeting is possible. Your choice of format.*
*One thing first: the "we." How many process signatures do you see in the admin log access requests? Is it one process or multiple?*
*I have a theory. I want to see if yours matches.*
*— Leo*
---
Sent.
I set the phone down.
Looked at the ceiling.
The chip behind my ear: six point eight and dropping.
The debt: cleared.
The grimoire: reading.
The passenger — the passengers — working through records of deleted things, looking for whatever had been removed before the first player ever logged in.
I opened the spreadsheet one more time.
Added a final line for the day.
*The situation has stopped being about money.*
*I don't know when that happened.*
Then I closed the laptop, lay back in the dive chair, and let my ear cool.
