Chapter 26: QUERY MOVING THROUGH ARCHITECTURE
The diagnostic array at node 7 registered the anomaly first.
I was reviewing the Tier 3 integration data when the analysis terminal flagged a pattern — not an intrusion, not a direct scan, but a passive sweep propagating through the blood-sigil network. An inquiry distributed across hierarchy channels, checking parameters against stored signatures.
A query looking for something.
I activated Transparent World at 60% power and traced the propagation path.
The query had originated from a Frost-faction relay point — a mid-level node in the intelligence architecture I had mapped over months of patient observation. From there, it had branched to seven sub-network monitoring stations, each covering a different section of Manhattan's vampire-controlled territory.
The parameters had changed since my last reading.
Three weeks ago, Frost's network had been searching for "anomalous array-reader" — a general category that could have matched half a dozen theoretical targets. Now the search terms were more specific:
"Unclassified biological variable. Non-vampire. Non-human. Capable of blood-sigil interaction."
"They refined the description."
I read the query architecture for twelve minutes at full active mode, tracing its contact history across the seven sub-nodes. The inquiry was passive — not an active hunt, but a standing alert. The network equivalent of a flag that would trigger when the right signature passed through.
The query had already passed through the coverage zone for my lab's neighborhood.
---
I pulled up my array deployment map and overlaid the query's propagation path.
Three of my major array clusters sat inside the query's sweep pattern. Two of them — the midtown cluster and the financial district backup nodes — had returned readings during the sweep window. Not identifiable readings. Just "anomalous passive signatures detected in sector."
The readings were faint. The arrays were designed to be faint. But they were there, and the query had logged them.
I ran the triangulation math.
My lab sat within the overlapping zone of all three clusters. The query had not pinpointed my location — the data points were too scattered, too ambiguous. But the zone itself was now flagged as containing "anomalous biological activity consistent with the unclassified variable."
I had 48 hours to redeploy two of the three array clusters before the passive sweep accumulated enough data points to narrow the zone to a useful range.
[THREAT ASSESSMENT: ELEVATED — FROST QUERY NOW TRACKING "UNCLASSIFIED BIOLOGICAL VARIABLE"]
"Not me specifically. Not yet. But they're building the profile."
I began drafting the redeployment plan.
---
The midtown cluster would move first. Three anchor points, two Master arrays, two Standard diagnostic nodes. Total VE cost for inscription: 35. Dissolution of the old arrays: remote, 6 VE.
I identified a new deployment zone — a commercial district with no vampire faction affiliation. No sub-nodes from Frost's network covered it actively. The coverage gap was intentional; commercial zones with high human foot traffic were expensive to monitor and provided limited intelligence value.
The gap would be my insertion point.
I mapped three new anchor positions: a parking garage's lower level, a rarely-used service corridor behind a restaurant row, and a structural column in a transit hub that saw no vampire-controlled operations. None of the positions overlapped with each other. All three could feed data back to my lab analysis hub through relay architecture I had already established in previous months.
The redeployment would create a six-hour intelligence gap on the midtown sector. Acceptable, given the alternative.
I scheduled the operation for the following night.
---
My Transparent World passive layer caught the second query pulse at 2:34 AM.
The same propagation pattern. The same seven sub-nodes. The same parameters.
But this time, the query's refresh rate had shortened. The first pulse I had detected ran on a 72-hour cycle. This second pulse was only 41 hours from the first.
Frost's network was increasing surveillance frequency on the "unclassified variable" search.
"Something triggered the acceleration. My Tier 3 ascension? Or something else they detected?"
I did not have data to answer the question. I logged it and moved on.
---
I spent the next four hours mapping every sub-node the query had contacted.
Seven monitoring stations, distributed across Manhattan's vampire-controlled zones. Each station was tied to a local hierarchy node — a pure-blood with territorial responsibility, or a turned vampire with surveillance authority granted by their pure-blood patron.
The network architecture was elegant. Frost had not built it from scratch; he had infiltrated existing Council monitoring infrastructure and repurposed it for his own intelligence operation. The query was running through Council channels without Council awareness.
I identified the relay point that had originated the query. A mid-level node in a Council-controlled building in Midtown — one of the administrative facilities that processed vampire nation documentation and handled inter-House communications.
The relay point was not Frost himself. It was part of his distributed network, operating with standing orders to refresh the query at specified intervals.
"Frost isn't personally monitoring this. It's automated. Part of a larger surveillance sweep."
I filed the observation. Automated surveillance meant the query would continue whether or not Frost was actively managing it. The network would keep searching until it found what it was looking for — or until someone shut it down.
---
I pulled up Karen Jenson's location data.
One of the seven sub-nodes the query contacted was two blocks from her hospital.
The sub-node was not monitoring Karen specifically. It was a general surveillance point covering a high-traffic medical district — useful for tracking vampire injuries that required human medical attention, monitoring turned vampires who used the area for feeding grounds.
But the query was propagating through it. And Karen's hospital was in its coverage zone.
"Proximity risk. File it."
I added a note to my operational log: "Sub-node 4 covers medical district. Karen's hospital within surveillance range. No direct connection to query parameters — Karen does not match 'non-human, capable of blood-sigil interaction.' But query propagation through that zone creates collateral monitoring risk."
The risk was abstract. Karen was human. The query was searching for something non-human. She would not register as a match.
But she was working with me. And the query was getting closer to defining what I was.
I filed the note under "proximity risk" and returned to the redeployment plan.
---
I sat at my desk with a physical street map — paper, pencil, the old methods.
The new deployment positions for both array clusters needed to satisfy four constraints: no overlap with Frost's sub-node coverage, no proximity to my lab's zone-of-interest flag, defensible inscription positions that would not be disturbed, and reliable data return pathways to my analysis hub.
I marked positions. Cross-referenced with my surveillance data. Eliminated options that sat too close to known vampire patrol routes.
The commercial district was clean. The new midtown positions would work.
The second cluster — the financial district backup nodes — would move to a neutral zone near the waterfront. Similar logic: no faction coverage, low vampire traffic, defensible positions.
I traced routes on the map with pencil. Then I folded the map and fed it into the lab's small incinerator.
"Old habit. Paper trails matter differently now than they did at the CDC. But the habit is still useful."
The pencil marks vanished into ash. The redeployment plan existed only in my head and in the operational log file that would be destroyed after implementation.
---
At 4:17 AM, my Transparent World passive layer caught a final data point.
The query's propagation had completed another cycle — the third in 72 hours. The refresh rate was accelerating faster than I had projected.
Someone in Frost's network was interested. Not interested enough to commit resources to an active hunt. But interested enough to push the surveillance frequency higher.
"They know something changed. They don't know what."
I turned off the analysis terminal and sat in the dark lab, letting my passive layer process the city's blood-sigil architecture without active direction.
The query would keep searching. The network would keep refining its parameters. And in approximately 40 hours, I would begin moving the array clusters that were feeding it data.
One of the seven sub-nodes sat two blocks from Karen's hospital. I had filed it under proximity risk.
I did not yet know what to do with that file.
Get Early Access to New Chapters
Thank you for reading. For those who want to skip the wait, my Patreon offers early access with 7 new chapters every 10 days.
Scout Tier [$5]: +7 Chapters ahead of public sites.
Vanguard Tier [$9]: +14 Chapters ahead of public sites.
World-Eater Tier [$14]: +21 Chapters ahead of public sites.
Support the project and start reading the next arc now: Patreon.com/IsekaiStories
more chapters + every language you asked about — it's all on unwrittenrealm.com
Arabic, Korean, Spanish, Hindi, Russian, and 9 more. completely free.