Chapter Thirty-Six
Raine
Next to me, Asher mutters something about how firmware updates shouldn’t take this long.
I go back into the file I’d abandoned after Inara’s call, but almost immediately close it again.
I could push through it. I know that. I’m steady enough, sharp enough, that I’d be able to decode patterns rather than react to the content.
But I’m also tired, and exhaustion makes me sloppy in ways I can’t afford.
If GSD has already flagged Asher’s alias as a person of interest, then our window narrowed, and I don’t get to waste the time we have proving something to myself.
After a little distance, I’ll be able to come back to it fresh.
I load the file list and scan through the names. Most are detainee logs. Mine is at the bottom. Detainee 3F-207.
Tomorrow, I promise myself. I’ll go back to it tomorrow.
At the end of the list, a handful of files break the pattern. They’re older than all the rest. One…by a lot.
“Asher? You only copied one directory?” I ask. “You didn’t poke around anywhere else?”
“Once I saw your vitals, I knew I didn’t have the time.” He runs a hand through his hair, not looking at me. “You were….in trouble.”
The way he says it—his voice flat and careful—tells me he knew how close it was.
A brief pressure tightens behind my ribs, but I breathe through it before it can spread.
“I know.” I reach over and rest my fingers briefly on his.
After a beat, he frowns. “Why?”
“Look at this.” I angle the laptop. “These three files aren’t detainee logs. The metadata doesn’t line up. They’re older. And the file names aren’t even close.”
“Old and mislabeled? That’s how you hide something you want to get lost.”
I click on the oldest one.
Continuity of Care Guidelines
The title is dry enough to be almost…comforting. But then I hear a man’s voice in my head.
“This isn’t punishment. This is care.”
I lock the memory away and start reading. The document seems to be a blueprint for what happens after someone is released from Coherent Path.
The language is exactly what I expect. Neutral to the point of anesthesia.
Sleep disruption, slowed response to instruction, and resistance to authority may indicate destabilization.
Intervention to be applied as clinically appropriate.
Appropriate to what, by whose standard, and applied by whom are never specified.
I read the first page once just to see the shape of it, then again more carefully.
The pattern is familiar. This wasn’t written to guide decisions. It was written to justify them after the fact.
Monitoring framed as care.
That’s the first lie.
Stabilization of the detainees Coherent Path “releases” is the stated goal, but the structure documented here tells a different story.
The file is organized around acceptable ranges. Heart rate during compliance checks. Sleep disruption, tracked by a smart watch that isn’t framed as optional. Failed or missed check-ins. Communication lags. They don’t expect something to go wrong immediately. They’re certain it will eventually.
Each section has a baseline value, then outlines the conditions under which deviation is logged, flagged, or escalated. Yet, there’s no section for improvement. No criteria for discharge. No point at which monitoring ends because someone is deemed “stable.”
Recurrence isn’t framed as something that might happen. It’s treated as something that will, and the system is built to catch it when it does.
I scroll back to the top and start again.
Asher sets a mug down near my elbow. “Chamomile,” he says. “With honey.”
I glance up, briefly, and a burst of warmth stirs in my chest. “Thanks.”
He offers me his coffee, and I smile. “Tomorrow—maybe the next day—I’m going to need a cup all to myself.”
“Good. Progress.” He slides a plate between us. Crackers, turkey, two slices of toast with peanut butter. “This is most of what we have left,” he says. “I’m going to have to go back to the grocery store when this firmware update finishes.”
My heart stutters. I knew he hadn’t come back with any food, but hadn’t processed what that meant. That he’d have to leave. Again. I wrap my hands around the mug of tea and let the weight of it steady me for a moment before I can speak.
“When you go, keep it boring.”
He waits. Listening the way you do when the details matter.
“Don’t go back to the same store you ran out of earlier,” I say. “Pick somewhere else, get what we need, and come straight back.”
“That’s the plan,” he says.
“I’m not worried about you,” I add, glancing up briefly. “I’m worried about someone seeing the same face in the same location twice in one day and registering the pattern.”
A small acknowledgment flickers in his eyes. “Fair.”
“And if anything feels off, you leave. I’ll go hungry before I’ll risk you.”
His jaw tightens. “Your body can’t take another hit right now.” He closes his eyes and takes a single deep breath. “But if it comes to that, we manage. A day of broth and electrolytes is better than one of us…being taken.”
I force myself to look at him again. Really look. And let myself be seen in return. “Agreed. You’re going…now?”
“Ten, maybe fifteen minutes. The laptop is going to be needy during all these updates.”
I nod, take a piece of toast, and return my focus to the screen—to another paragraph that reads…wrong .
Monitoring protocols include scheduled task audits, review of supervisory reports, and both physical and environmental status checks during site visits. Additional oversight is ordered on an “as needed” basis.
With language like that, they could track anything. Parking tickets. Dietary changes. Whether someone mows their lawn on schedule or cuts their hair.
This is language designed to survive legal challenges and public oversight—it sounds restrained while quietly authorizing harm.
I take another sip of tea, giving my brain a moment to organize and orient.
Asher clears his throat. He’s standing by the door, a ball cap pulled low over his eyes, and a pair of aviator sunglasses in his hand. I hadn’t noticed him getting up from the table. I file that piece of information away too.
“I’ll be forty-five minutes. Maybe less,” he says. “And I set up a backup phone. The music won’t cut out again.”
It takes a beat for that to land. Not the logistics. The intention. He understood the failure point that caused my earlier panic and quietly closed it.
I nod, giving myself a second to find my voice. “Forty-five minutes. Noted.”
As soon as the lock engages, the apartment feels…emptier. Quieter in a way I haven’t adjusted to yet. I don’t linger on it. I turn back to the file.
A subsection header interrupts the policy language: Observed Case Logs.
Up to this point, the document has stayed safely theoretical. This section changes tone. It stops talking about what should happen and starts laying out what has happened before.
The pages that follow read like case studies. But there are no names or dates. Just labels like Subject A, Subject B, Check-In #1, Check-In #2. Enough structure to compare outcomes, not enough detail to anchor them to a specific life.
What they all have in common? They complied enough inside Coherent Path to be released.
They’re people like Tessa. Like the other two detainees whose files I examined this morning.
This is what happens after.
They’re not measuring resistance. Or refusal. This is something more sinister. They’re measuring deviation.
Missed calls. Delayed response times. Shifts in sleep duration outside of a defined range. How performance of assigned tasks accelerates—or tapers.
Nothing dramatic. Nothing that would be concerning on its own. But the changes aren’t recorded in isolation. They’re stacked until each case study ends with the same line.
Threshold exceeded. Escalation approved.
I stop scrolling. I don’t need to keep reading. I know exactly what they’re doing.
Making escalation routine.
Expected.
Normal.
A quick glance at the next section is all I need for now. It’s denser. More technical. Tables. References. Language that defines limits and consequences in harsher detail than I’m ready to absorb alone.
I scroll back to the beginning and start annotating instead. Short notes without emotion.
Compliance is a prerequisite for release.
Post-release monitoring tracks accumulation of multiple violations.
Escalation is inevitable once thresholds are crossed, but thresholds are never defined.
No approving authority is ever named.
I save and close the file. There’s more to analyze, but I’ve reached the point where additional input wouldn’t be helpful. I need the patterns to settle so I can understand what’s signal and what’s simply noise.
Ellen is the next step. I’m more sure than ever that she’s gone through Coherent Path—or some version of it. Whatever comes after release, she’s lived through it.
The Continuity of Care file describes intent. Ellen can tell me how it’s actually implemented. And what toll it exacts.
But not tonight.
If I reach out now, I’ll ask questions before I’ve finished framing them. I’ll chase confirmation instead of clarity. That’s how blind spots form.
Tomorrow, I’ll be ready.
I slide the laptop a few inches away. The music plays on, a subtle backdrop keeping the apartment quiet, but not silent.
I test my shoulder. Slowly. One controlled lift. A careful rotation. The first range-of-motion work I was cleared to do after the shooting that took me out of the field. I stop at the edge of resistance, breathe, then try again.
The ache is there, but it’s clean. Specific. The kind of pain I’d expect. Not the kind I worry about.
Good.
I check the time. Asher still has ten minutes. He won’t be late. He’s too careful for that.
Moving to the couch, I pick a book from the small collection under the window. The Christie novel waits for me in the bedroom, but what I need most right now is something dry. Boring. Words to occupy a part of my brain so the rest of it can work out what happens next.
I pick up the Field Manual for Technical Communications, flip to the first page, and start reading.