Page 168 of Operation: Defiance

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.