Chapter 17: Frost's Move — Dragonetti
Dragonetti's blood-sigil went quiet at 11:47 PM.
I was running a standard active Transparent World session from my Node 3 observation position — routine network maintenance, checking signature stability across the Council member profiles — when the change registered. Not movement. Not combat activation. Termination.
The specific signature pattern of a pure-blood dying in UV exposure bloomed across my perception: photonic energy discharge spiking through the architectural markers, the biological equivalent of a system crash, then silence where a six-century-old vampire had been moments before.
[Blood-Sigil Alert: Lord Dragonetti. Status: TERMINATED.]
[Cause: UV exposure (high-intensity, sustained). Covenant architecture: collapsed.]
I checked my projection timeline. Frost was supposed to make his open move against Dragonetti in two more days — that was the sequence I'd built from the glyph completion percentages and the operational security patterns I'd been tracking. Two more days for Frost to complete the remaining Council markings, consolidate his faction position, and move from covert glyph application to direct confrontation with the pure-blood establishment.
I was wrong.
"He moved early. Specifically on Dragonetti. Why?"
I held the active Transparent World and scanned the city's blood-sigil architecture for context. Frost's signature was stable — no combat indicators, no stress response, no biological evidence that he'd personally executed Dragonetti. But Frost's people had been active in the last hour: Quinn's signature showed recent combat activation patterns, and three other faction members had moved through Dragonetti's compound's general area within the past forty minutes.
The execution had been delegated. Professional. Planned.
I pulled up my records on Dragonetti's recent activity and began reconstruction.
The answer was there. I'd had the data for a week and built the wrong conclusion.
Dragonetti had been making increased communication with external pure-blood contacts — Council equivalents in other territories, old-money families with political influence outside Manhattan. I'd read this as normal hierarchy maneuvering: the eldest Council member shoring up alliances in response to Frost's growing faction influence. Standard political behavior.
I hadn't read it as Dragonetti preparing to expose Frost's operation to external allies.
"He was going to bring in outside help. Frost killed him because Dragonetti was about to compromise the entire La Magra timeline by alerting people who could actually stop it."
The timeline methodology I'd built was wrong. Not in the data — in the framework. I'd been modeling Frost as a fixed-sequence operator: complete the glyph markings, then move to the next phase, then execute the ritual. A schedule to be followed.
Frost wasn't following a schedule. He was running an adaptive operation, responding to threats as they emerged, accelerating or adjusting based on what the environment required. The La Magra ritual had requirements — twelve vessels, specific timing, particular architecture — but Frost's path to meeting those requirements was flexible.
Every projection I'd made needed to be revised against this methodology.
I keyed the secure line.
"Dragonetti is dead. Frost moved early. Revising all Council timeline projections."
Blade's voice came back after a two-second delay. "When's the ritual?"
"Unknown. My projections are unreliable until I rebuild the timeline methodology."
A pause. "How unreliable?"
"Honest answer or managed answer?"
"Enough that I won't give you a number I can't support."
Another pause. Longer this time.
"That's honest."
The line went quiet.
I spent the next six hours rebuilding the projection framework.
The original methodology assumed Frost would complete each phase before moving to the next — glyph markings, political consolidation, open move, ritual execution. Sequential. Predictable. Wrong.
The revised methodology modeled Frost as an adaptive operator: responding to threats, accelerating where possible, adjusting sequence based on environmental pressure. Dragonetti's external contacts had been a threat. Frost eliminated the threat before it could materialize, even though it meant moving the open-move phase earlier than optimal glyph completion would suggest.
[Timeline Projection: Revised]
[Previous estimate: 6-8 weeks to ritual readiness.]
[Revised estimate: 3-7 weeks. Range increased due to adaptive-response uncertainty.]
The range was almost as wide as my original projection had been. Three weeks at the compressed end meant Frost was moving at maximum acceleration. Seven weeks at the extended end assumed he'd encounter significant resistance or operational complications.
The honest answer was that I didn't know which end of the range was more likely.
"Intelligence operations that produce accurate conclusions fast are rarer than they look from outside."
I documented the methodology revision and the Dragonetti termination in my operational log. Added a note about the adaptive-Frost model and the specific indicators I'd missed. Filed the two-day projection error as a calibration failure that I'd need to account for in all future analyses.
The secure line crackled.
"Friday still?"
Blade's voice. Checking whether the Dragonetti killing changed the Pearl archive timeline.
"Friday still," I confirmed. "Pearl's archive isn't connected to Dragonetti's termination. The ritual requirements are the same regardless of which Council members are alive to fulfill them."
"Good."
The line went quiet again.
I sat in the lab and watched the network status display show the city's blood-sigil architecture continuing its patterns as though the oldest vampire in Manhattan hadn't just been executed by UV exposure in his own compound.
Somewhere out there, ten remaining Council members had just learned that Dragonetti was dead. Frost's open-move phase had started. The window between preparation and execution had shortened by an amount I couldn't precisely calculate.
The dread was appropriate. I documented that too.
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