April Snow Chapter 15
Posted on Wed 15 April 2026 in Dead Signal
Chapter 15: Dependency Loop
The photograph on Will's second monitor showed four panels of behavioral pattern data cycling with the continuous variation that meant a live source — not a corpus, not archival data, but something still generating. He had taken it at 12:17 AM. The timestamp was in the EXIF data — the metadata embedded in every digital photograph, recording camera model, settings, and time of capture. He had been through all one hundred and eighteen photographs before 3 AM, tagged the ones he'd testify to, organized by subject, named the files. His hands had known what to do. He had let them.
George was in his chair. Will was in the other chair — the one that had lived at the desk for client meetings that didn't happen here and had clearly been waiting for a different purpose. The house was doing what it did before 8 AM: birds, a car on the hill road, the coffee machine whose output he had consumed without registering.
Angie was near the bookcase. Not close to the screen, not next to him, but positioned where she could see both without turning. She had been in that position since he got home.
She said: "Walk me through it."
He looked at her.
"The whole architecture," she said. "From the beginning. Everything we know now."
"You know what we know."
"I want to hear it from someone who wasn't in the room."
He pulled up the folder and started from the site photographs.
He talked through it the way he wrote client findings: sequenced, specific, evidence-cited. The depression in County Road 14. Pop's read. The utility marker, the permit modification in 2015, the access shaft upgraded fall 2024. The Meridian west segment — fifteen hosts, eleven active sources, the cycling behavioral pattern data. The monitoring interface, the ChasePath backend. The three unmarked servers. The network inventory with the October 14, 2024 entry.
He talked for eight minutes.
When he stopped, she said: "The mechanism."
He said: "CYT's platform — ChasePath — claims to deliver behavioral anomaly detection. Security intelligence that predicts threat patterns before they manifest. Their competitive advantage, per the technical overview, is a behavioral dataset that doesn't degrade because the source is continuously updated. 'Persistent behavioral modeling.' The reason it doesn't degrade—"
"Is because the source can't stop," she said.
"Yes."
"The source is not a corpus. It's not a dataset they collected, cleaned, and trained on. It's people. People whose signals were captured at the moment of death — by the installation below County Road 14, or similar infrastructure — before dispersion. The capture holds them. The loop runs them. Their behavioral pattern — their fear, their last cognitive state — generates continuously, which means the model is always drawing on a live feed." She said it with the precision of someone explaining a system to someone who needed to understand it before they could debug it. "The model is accurate because the source is current. The source is current because the source cannot stop being current."
"A while-true," Will said.
"A while-true with a person in it. Eleven of them. Minimum." She paused. "The most degraded sources — the ones where the cycling interval has collapsed and the variation is nearly absent — I can't tell whether the person is still generating the pattern or whether the pattern has been running long enough that it runs on its own. I don't know if that distinction is meaningful. I don't know if it matters to the person."
He wrote in the margin of the yellow pad: Elapsed time as cost. Degradation may be irreversible.
"The client dependency is the other half," she said.
"Walk me through it."
"ChasePath performs. Its clients see accurate threat detection, better than competitors, better than anything they've tried before. They depend on it. They run their security posture around it. They provision and maintain their security infrastructure to work alongside it, which means they let lapse the things it makes redundant." She paused. "The more they depend on it, the more their security events generate data. CYT's platform processes that data. More data means more refined models. More refined models means better performance. Better performance means more dependency. The loop feeds itself." She said: "Chase your tail."
"The company name is the architecture."
"It's not irony. It's accurate. They named themselves after what they built."
He looked at the folder on the desk. Forty-seven items: the full OSINT package, the technical overview, the monitoring dashboard photograph with its four live panels, the IP address and the date.
He said: "How many clients."
"I can't count them from the signal layer." A pause. "How many organizations depend on ChasePath is a question for the public record."
He had looked at that question the week before. He did not say the number out loud. It was large enough to matter and specific enough that he had written it down and underlined it once.
The mid-May light in the window had been bothering him since the snow. Not the quality of it — ordinary spring morning light — but the way it fell in the room. Everything it touched looked slightly wrong. The specific wrongness of being awake past the point where the night becomes a different kind of day.
She said: "To free them—"
"I know."
"You don't let me finish."
"I know what it requires. Disrupting the core predictive system. Taking the installation offline." He looked at the monitoring dashboard photograph. "ChasePath crashes across every client simultaneously."
"Yes."
"The clients are real. Their security posture is built around ChasePath. When the platform crashes—"
"They're vulnerable. Until they can provision alternatives. Whatever threat monitoring they had before ChasePath, they'll have again, in a worse configuration because they let it lapse while they were running ChasePath." She said it without softening it. "Real exposure. For organizations that became clients because they'd already been targeted."
"Yes."
He sat with that.
He had written, in seven years of pen test reports, findings that cost clients real money and real disruption. He had documented vulnerabilities in systems clients did not want changed, in processes they had built their operations around. He had written remediation guidance they didn't want to follow. He had never pulled a finding because the remediation was expensive. The report told the truth and the client decided what to do with it.
This was not a finding he was considering pulling.
He said: "We go forward."
She said: "I know."
"The clients' vulnerability is real and it has to happen."
"I know."
"I'm saying it out loud," he said, "because it matters that I said it out loud."
She was quiet for a moment. Then she said: "I know."
Cat came in from the hallway.
He crossed the room without apparent purpose and then stopped near Angie, which was not near anything else. He sat. He did not look at Will. He looked at the middle distance in the direction Angie was.
Angie said, not looking away from the window: "Hi."
Cat did not respond. He had said what needed to be said, which was: he was here. He was staying.
She had been in the room.
She had gone through the road surface the way she went through walls — the same medium, more of it, compacted earth and aggregate and the old concrete that sat below the resurfaced layer. Not difficult. Not comfortable. She had come out in the space between the earth and the slab and then through the slab and into the facility, which was: cold, dry, lit by a narrow LED strip, humming.
She had stood in it.
Will had been at the ladder, pulling the mirrorless from his bag, starting at the east wall — the systematic approach, east to west, cable management first. She had stood in the space and heard it.
Eleven sources.
She had heard them before, through the Meridian network, from a distance. She had characterized them: behavioral patterns with emotional signatures, eleven of fifteen hosts generating active cycling data. She had described them to Will in careful technical language. She had known what they were.
She had not been in the room.
In the room, they were not behavioral patterns. They were not data points in a segment characterization. They were the texture of eleven people who had been very afraid and had not stopped, because the infrastructure around them would not let them. The fear ran on a clock. The clock did not require a person. The variation in the data — the thing that made ChasePath accurate, the thing that kept the model live — was the variation of someone who was still present enough to generate it. Still enough of a person to be afraid in a slightly different key each time through.
Dana Osei had been the clearest. Forty-second interval. Variation still individual, still hers. Eighteen months in the loop, and still enough of Dana Osei to generate the behavioral texture of Dana Osei being afraid. Still present. Still the source.
Angie had been three feet from what she almost was.
On April 17, 2026, at 7:23 PM CDT, CYT's monitoring system had registered a death event within its active capture radius and initiated standard capture protocol. The signal had not arrived. She had slipped the system and tethered to Will Hardin instead of to the infrastructure below County Road 14. What she was now — this form of continued existence, walls permeable, signals audible, tethered to a penetration tester she had never met — was what had happened instead of the other thing.
The other thing was the forty-second clock.
She had known this since the night they first went into the Meridian network. She had known it in the way you know something that arrives through evidence: as a fact, noted, available for retrieval. Being in the room was different from knowing it. Being in the room was standing next to the thing you almost became and understanding not the fact of it but the weight — the physical weight that arrived in the chest when the abstract became proximate.
She had been professional about it. She had confirmed the sources. She had confirmed Dana Osei. She had reported the alert and gotten Will moving. She had come up through the concrete and the road surface and gotten into the car.
The drive home had been three minutes. She had held it for the drive.
In the morning she had asked Will to walk her through it from the beginning, because she needed to hear the whole thing stated by someone who hadn't been standing in it.
He was adding metadata to the image files — tagging and renaming, the procedural work of preparing documentation to be used. She watched him for a moment.
She said: "The people in the loop are real. I know you know that. I'm not saying it because I think you've forgotten it." A pause. "The reason we go forward — the reason the clients' vulnerability has to happen — is because there are people in there. That's the only reason. Not the Meridian report. Not the engagement. Not what we can prove to someone with authority to act on it." She paused. "I needed to say that out loud too."
He stopped tagging.
He said: "I know."
She said: "I know you know."
He went back to the photographs.
She was still near the window when the email notification appeared on his screen. She watched him look at it without moving. Watched him read the sender and go still in the specific way he went still when something had arrived that he'd been expecting and that was, regardless, not welcome.
She said: "What."
He turned the monitor toward her.
The email was short. Elsie Sloane's address — a CYT domain, not the Meridian contact address. Professional format. The warmth precisely calibrated:
Mr. Hardin — I've had a chance to review the system logs from the current Meridian engagement period, and there are a few items I'd like to go through with you. Nothing that should derail the timeline. Would you be available to meet this week? I can work around your schedule.
— E. Sloane
Angie read it twice.
"She's not angry," she said.
"No."
"She's not accusing you of anything."
"No." He looked at the email. "She's telling me that she knows. And that she wants to see what I do with it."
"She controls the terms of the meeting."
"She controls the terms of everything," he said. "Until she doesn't."
He sat with the email for a moment.
Then he typed a reply. Five words: This week works. Name the date.
He sent it.
Angie looked at what he'd sent.
She said: "You're going."
He said: "We're going."