Cherreads

Chapter 29 - Chapter 29 — Priya

She came to him on a Friday afternoon in February, which was unusual because Priya worked with a precision that made her unlikely to bring non-urgent matters to him at the end of a week. When she appeared in his office doorway with her laptop and a specific expression — not alarmed, not accusatory, but careful — he moved what he was working on to one side.

"Close the door," he said.

She did. She sat across from him and opened the laptop and turned it to show him the screen.

It was a financial news alert. A hedge fund strategy paper, published in a trade publication, discussing the theoretical application of procurement anomaly detection to equity research. The paper cited Threadline by name.

"Reiss published this?" Marcus said.

"Not Reiss. A competitor fund. Different name, similar strategy." Priya's voice was even. "But the methodology described in this paper is not theoretical. It's our methodology. The specific approach to entity disambiguation, the confidence scoring framework — this is Threadline's architecture described in strategy terms."

Marcus read the paper carefully. She was right. The description was precise enough that whoever had written it had either reverse-engineered the product with extraordinary care or had access to internal documentation.

He thought about the intrusion Yuki had found four months ago. The endpoint probing. The document distribution question that had been resolved as a handling error.

"When was this published?" he said.

"Three days ago."

"Does Yuki know?"

"I came to you first."

Marcus looked at the paper. He thought about what it meant for someone to have this level of detail about the methodology. He thought about what it meant for that detail to have reached a competitor fund before the Reiss partnership had been formalized.

"Who else has access to the Threadline architecture documents?" he said.

"Internal: the four of us plus you. External: Marsh, Hollis, Faye Brennan at Lattice, the Meridian technical team during diligence." She paused. "And whoever has been probing our systems."

"The intrusion was neutralized."

"The intrusion Yuki found was neutralized. We don't know if it was the only one."

Marcus looked at her. Priya was the person on his team who asked the most uncomfortable questions with the least unnecessary drama about it, and he valued this quality precisely because moments like this required it.

"You're right," he said. "Run a full audit with Yuki. Every system, every access log, every external credential. I want to know every place this documentation could have gone."

"What about the published paper?"

"I'll have Marsh look at the IP question. If there's a case, we pursue it. If there isn't, we note it and move faster." He looked at the paper once more. "This tells us someone thinks what we've built is worth stealing. That's a form of validation."

"It's a form of threat," Priya said.

"Both things are true." He looked at her steadily. "Priya. I want to tell you something."

She waited.

"The government engagement I've been managing in parallel — the one I've told you exists but not the specifics of — it has a security dimension. There are people whose activities our work is affecting, and some of them have the capability and the motivation to come at us indirectly." He paused. "What you're looking at may be related to that."

She was very still.

"How long has this been true?" she said.

"Since the first Monitor story, in terms of basic attention. Since Phase Two of the engagement, in terms of actual risk."

"And you've been managing it alone."

"With Marsh, and with Yuki on the technical side."

Priya looked at him for a long moment. He watched her process it — not the anger of someone who felt deceived, but the calibration of someone who was adjusting a model.

"I need to know more," she said. "I'm not asking for the classified details. I'm asking for the threat picture. I can't do my job — I can't protect this company's customer relationships and reputation — if I don't understand what's coming at us."

He thought about the NDA. He thought about what he could say within it and what he couldn't. He thought about the architecture of trust.

"Schedule a meeting with me and Marsh," he said. "Monday. I'll get you the picture I can give you."

She nodded, closed the laptop, and stood. At the door she paused.

"For what it's worth," she said, "I don't think you've managed this wrong. I think the weight of it is bigger than you've let show." She looked at him. "You should let it show more. Not to customers. To us."

She left.

Marcus sat alone with the office door closed and thought about what she had said. He thought about the Fourth Gate — *the architecture of trust is harder than any system you have made* — and he thought that he had been building it structurally, the way he built technical systems: placing components in optimized positions, designing interfaces for maximum efficiency. That was not the same as building it humanly.

He thought about what the difference was.

He thought he was starting to understand.

More Chapters