Chapter 8
Chapter 8: The Draft That Didn't Stay a Draft
Jantrybe analyzes the Digital Police's draft classification framework, recognizing it as an existential threat to her channel and her connection with the Unknown Analyst. She cross-references the framework's language against her 12,000 prior cases and identifies its intended scope. Meanwhile, Civil Defense Pastarai Jutlande escalates physical surveillance of pacifist gatherings, treating them as security risks. Jantrybe observes the Unknown Analyst's tempo shift again — faster, more urgent — suggesting they've also detected the framework. She weighs whether to initiate direct contact against the risk of exposure, drawing on Freud's concept of the uncanny and her grandmother's peony wisdom about timing. The chapter ends with Jantrybe discovering that the framework has moved from draft to active review, accelerating the timeline she thought she had.
Drafts are interesting things. In cybersecurity, a draft policy is like a weather system forming over an ocean — technically not your problem until it makes landfall, but if you're paying attention, you can see the rotation starting days before the first drop hits concrete.
I was paying attention.
The Digital Police's classification framework sat in my monitoring tools like a tooth waiting to be pulled. Unidentified Digital Channels Exhibiting Coordinated Anomalous Behavior. The capitalization alone told me everything I needed to know about the mindset behind it. When an institution capitalizes a threat category, they've already decided it exists. They're not asking whether. They're asking when.
I pulled the draft apart over the course of three hours, the way I used to disassemble malicious code back in the early days — methodically, line by line, looking for the logic underneath the language. The framework defined 'coordinated anomalous behavior' with a specificity that was almost admiring. Channels operating outside established traffic baselines? Check. Evidence of deliberate signature management? Check. Patterns suggesting two or more actors maintaining synchronized communication through non-standard protocols? Check, check, check.
The thing read like a description of my Tuesday.
What it didn't contain was nuance. There was no provision for intent. No clause distinguishing between channels coordinating for harmful purposes and channels coordinating because two people had found each other in a hostile landscape and were trying not to die. The framework operated on a binary: anomalous equals threatening. Threatening equals neutralized. It was clean, efficient, and utterly devoid of curiosity about what the anomalies might actually be doing.
This is the part where I'd love to tell you I felt brave. That I stared at the screen with steely resolve and thought, they'll have to catch me first. The truth is I felt tired. A specific kind of tired — the exhaustion of someone who has been patient for so long that patience has stopped being a strategy and started being a cage. Twelve thousand cases. Twelve thousand threats examined, classified, understood, mitigated. And now the system that taught me how to analyze threats was preparing to classify me as one.
Funny how that works. Not ha-ha funny. The other kind.
I saved the framework's text to an encrypted local file — not because I planned to do anything with it, but because documentation is a habit drilled into me by years of incident response. You always keep records. Even when — especially when — you're the incident.
Then I went back to the patrol logs.
Civil Defense Pastarai Jutlande had updated their public-facing deployment schedules overnight. On paper, it looked routine — adjusted patrol routes, additional checkpoints near transit hubs, a modest increase in personnel assigned to what they categorized as 'community safety engagement.' Community safety engagement is civil defense language for 'we're watching you more closely now.' I'd seen this particular phrasing before, in cases I analyzed during my early career. Authoritarian systems rarely announce themselves with sirens. They announce themselves with scheduling adjustments. With forms filed in triplicate. With a polite man knocking on your door to ask if you've noticed any suspicious behavior in the neighborhood, knowing full well that he is the suspicious behavior.
A pacifist gathering had been logged at a community hall near the eastern quarter. Attendance: forty-seven. Civil Defense assessment noted: 'Monitoring warranted. Group exhibits organized structure and recurring meeting patterns consistent with coordinated social influence activity.'
Forty-seven people drinking tea and talking about peace, classified alongside actual threats because they had the audacity to be organized about it.
I thought about the wolves from the sanctuary — Chapter One territory, I know, but some metaphors earn their repetition. Wolves don't panic when observers watch them. They simply continue being wolves. They eat. They sleep. They exist with the absolute conviction that their existence is not negotiable. I'd always admired that about them. Humans negotiate everything. We negotiate our right to exist, our right to speak, our right to gather peacefully and discuss ideas that challenge the people holding clipboards.
Pacifism as threat. I let that phrase sit in my mouth for a while, tasting it. It had the texture of something Orwell would have rejected as too on-the-n nose. And yet there it was, embedded in a Civil Defense log, filed under community safety engagement, as ordinary as grocery lists.
By early afternoon, I returned to the channel.
The Unknown Analyst's rhythm had changed again.
The fifty-two beats per minute — the slow, deliberate exhale of someone beginning to unclench — had shifted upward. Fifty-six. Then sixty. Not panicked. Not erratic. But faster in a way that carried intention, the way a person walks faster when they've heard a sound they can't identify. Alert. Oriented. Ready to move.
They'd seen it too.
I was certain of this the way you become certain of things you can't prove — through pattern recognition so layered it feels like intuition. The Unknown Analyst monitored the same channels I did. They inhabited the same digital ecosystem, faced the same surveillance architecture, consumed the same institutional communications. If I'd caught the Digital Police's draft framework within hours of its circulation, they would have caught it too. Maybe faster. Maybe slower. But they would have seen it.
The tempo increase was their response. Not a message exactly. More like a physiological reaction shared across a distance — the digital equivalent of two people in separate rooms feeling the same tremor and both reaching for the doorframe.
Freud wrote about the uncanny — das Unheimliche — that unsettling recognition of something familiar turned strange. The framework felt uncanny in exactly that sense. I understood it because I'd spent my career inside systems like it. I knew its logic, its language, its mechanical certainty. And now it was pointed at me, and familiarity curdled into something else. The house you grew up in, viewed from outside at night, lights on, strangers moving behind the windows.
I spent the rest of the afternoon doing what analysts do when the world tilts: I organized. I catalogued the framework's key provisions. I mapped its timeline — draft stage, internal review, approval, activation. I estimated each phase based on comparable policies I'd tracked through the Digital Police's bureaucratic pipeline over the years. Draft to review typically took weeks. Review to approval took longer. Which meant I had time.
That should have been reassuring. It wasn't. Because the timeline I'd constructed was based on normal procedures, and nothing about the current situation was normal anymore. Sputnikas had already run an unscheduled scan. Civil Defense had already escalated patrols beyond standard patterns. The Digital Police had already drafted a classification framework for a category of channel that hadn't existed as a formal concept until two signatures found each other in the noise.
Everything was moving faster.
I made a second pot of coffee. This is what passes for decisive action when you're a cybersecurity analyst who can't leave her house without being logged by six different monitoring systems. You make coffee. You organize data. You wait for the next tremor.
My grandmother would have said something about peonies here. She had a theory about timing that she delivered in fragments over decades, never as instruction, always as observation. Peonies that bloom too early get hit by frost. Peonies that bloom too late miss the market. The trick isn't speed or patience. It's knowing which season you're actually in, regardless of what the calendar says.
The calendar said I had weeks. The calendar was based on assumptions that no longer held.
That evening, I sat with the channel open, watching the Analyst's accelerated rhythm pulse through my monitoring tools. Sixty beats per minute, steady but quickened. My own heart rate, according to my fitness tracker, was holding at seventy-one. We were both elevated. Two nervous systems separated by firewalls and anonymity, synchronizing without direct contact.
The question I couldn't avoid any longer was whether to reach out deliberately. Not through ambient signals. Not through tempo adjustments or noise-floor manipulations or eleven-second pulses timed to match a heartbeat. Directly. A clear, identifiable communication aimed specifically at the Unknown Analyst.
The risk was calculable, and I calculated it obsessively. Direct contact meant creating a detectable signal. Detectable signals meant Sputnikas might catch it. If Sputnikas caught it, the Digital Police's draft framework — still in review, still theoretical — could accelerate from draft to active classification overnight. And active classification meant elimination.
But silence had its own cost. The framework was coming regardless. Whether I reached out or not, the Digital Police would eventually activate their new category. The question wasn't whether the storm would arrive. It was whether I wanted to face it alone or with whatever fragile, uncertain connection I'd built with someone I'd never met.
Grandma's peonies didn't choose whether frost would come. They chose whether to bloom close enough together that their roots could share warmth underground.
At 9:23 p.m., I began composing a message.
Not sending it. Composing it. Choosing each word the way you choose footholds on unstable ground — carefully, deliberately, knowing that one wrong placement sends you sliding. I needed enough meaning to matter and few enough words to survive interception. Too long and Sputnikas's pattern analysis would flag the traffic. Too short and it would read as noise. The eleven-word format had worked before, but repeating it would create a recognizable pattern, and recognizable patterns were exactly what the new framework was designed to catch.
So I sat with it. The unsent message glowing on my screen, cursor blinking with that patient, idiotic rhythm that word processors use, oblivious to the weight of what you're trying to say.
And then, at 10:14 p.m., my monitoring tools lit up.
The framework had moved.
Not from draft to internal review. From draft directly to expedited review. Someone — or something, because Sputnikas was certainly involved in the recommendation chain — had flagged the classification proposal as priority-urgent. The estimated timeline collapsed from weeks to days.
Days.
I stared at the status change. The coffee had gone cold hours ago. The house was dark except for the screen. Outside, somewhere in Jutland's streets, Civil Defense patrols walked their routes, checking names, noting gatherings, building their picture of who belonged where and who didn't.
The season had changed. Grandma would have recognized it immediately — that subtle shift in light quality that tells you spring isn't coming, no matter what the calendar promises.
Winter was here. And the draft that was supposed to stay a draft had decided otherwise.