She called at nine-thirty Saturday morning, which was twelve hours after Warren had said she would call, and forty-five minutes after Marcus had finished his daily run and made coffee and opened the threat monitoring dashboard on his personal system. He had been reviewing the overnight anomaly reports when the call came — nothing significant in the logs, but he had been in the habit of reviewing them since the supply chain attack, and the habit was useful enough that he kept it even when the logs were clean.
"I have two elevated assessments," Elaine said, without preamble. "I'll do them in order of complexity rather than severity, because the simpler one requires a decision from you before Monday and the more complex one is informational."
"Go ahead."
"The first is a personnel contact report. Three days ago, a member of your team — not one of the inner four — was approached via LinkedIn by a recruiter representing a company called Parnell Digital. Parnell Digital is a real company, a data analytics consultancy in Boston, with legitimate clients and a legitimate business. The recruiter's message was professional and unremarkable. The team member has not responded." She paused. "Parnell Digital was capitalized two years ago by a subsidiary of an investment vehicle that has documented connections to the Varela network's secondary tier. Not the principal network — the secondary tier. People who were not named principals but who provided logistical support and financial services to the named principals."
Marcus absorbed this. "The contact is a probe. They're identifying which of my people are reachable."
"That's the assessment. The team member who was contacted is a data engineer. Not technically irreplaceable, but knowledgeable about the monitoring architecture and the output pipeline." She paused. "The decision you need to make before Monday is whether to brief that specific team member on the contact and its context, or to handle it through your security firm without direct disclosure to them."
Marcus thought about Lena Park's question and about what he had said to seventeen people two days before this call. *Everything you built, you built knowing what it was for.* He thought about what it would mean to find out, after being contacted by a Varela-adjacent recruiter, that Marcus had known about it and had not told you.
"I'll brief them directly," he said. "Monday morning, before the security firm session. They need to understand what the contact was and why it matters."
"Agreed," Elaine said. "The second assessment is more complex. In the past seventy-two hours, we've observed a pattern of queries to commercial data aggregators. Multiple queries from multiple source accounts, all using slightly different search parameters, but all resolving to a common profile target: persons with documented connections to federal oversight bodies and congressional staff who have been in contact with the Threadline methodology."
Marcus was still. "They're mapping who knows about the filings before the filings are public."
"Yes. The queries are consistent with an effort to identify the congressional staff who received the pre-publication briefing. The monitor story was published five weeks ago. Anyone who was briefed before publication and then acted on the briefing — even in small ways, like updating a procurement oversight calendar — would be visible in certain commercial data aggregator records."
"What's the implication?" Marcus said.
"Pressure," Elaine said. "Not physical — procedural. If they can identify the congressional staff who were briefed before publication, they can construct a narrative that the briefing was coordination rather than disclosure. That the oversight process was pre-arranged with the media, which would allow them to characterize the federal case as politically engineered rather than independently investigated." She paused. "It's a counter-narrative strategy. The goal is not to stop the filing — that ship has sailed. The goal is to contaminate the legal and political environment in which the filing lands."
Marcus thought about this for several seconds. The counter-narrative was sophisticated because it was partially true: there had been a pre-publication briefing. The briefing had been factual, non-advocacy, documented in the Monitor's editorial records, and was itself standard practice in national security journalism. But the existence of the briefing was real, and in the right information environment, it could be described in ways that made coordination and disclosure look identical.
"The counter-narrative depends on characterizing the briefing as coordination," he said. "The Monitor's editorial records document the briefing's content and framing. David Osei's articulation of the independence principle is in writing. The briefing was procedurally clean."
"Yes. But the counter-narrative doesn't need to win in court. It needs to win in a particular political environment, at a particular moment, in front of a particular audience that is already disposed to distrust the oversight process." She paused. "The working group's assessment is that the counter-narrative will be attempted. The question is the medium — whether it surfaces as a leak to a friendly media outlet, a complaint filed with an oversight ethics body, or something more operationally direct."
"If it surfaces as a leak," Marcus said, "we need the Monitor to be positioned to respond before the narrative gets traction. David needs to know this is coming."
"He does. I called him yesterday. He and his legal team are preparing a public documentation of the briefing's timeline and content — not anticipatory publication, but a prepared response that can move quickly when needed." A pause. "Osei's response was interesting. He said, and I'm passing this on because I think you'll find it useful: 'This is what they do to stories that are true. The ones that don't work get archived. The ones that matter get attacked. I've been doing this for fifteen years and I've only been attacked this directly twice. Both of those stories resulted in significant institutional change. I'm not concerned about the attack. I'm satisfied about what it means.'"
Marcus let that sit for a moment. He thought about the methodology that persisted beyond any single finding. He thought about Carla Reyes saying *twenty-two years looking for structures I could see existed but couldn't prove existed.* He thought about two journalists and a team of seventeen people and a government legal process that was three months from resolution, all of them operating in connected but distinct domains, all of them building toward the same thing from different directions.
"What's the working group's posture on the data aggregator queries?" he said. "Active counter or monitor-and-document?"
"Monitor-and-document for now," Elaine said. "The queries are from commercial accounts — nothing actionable. But we're tracking the account cluster and will have more pattern clarity within a week."
"Yuki should see the query pattern," Marcus said. "Not the classified context, but the behavioral signature. If they switch from commercial aggregators to direct approaches, she'll be in a better position to recognize the pattern shift if she knows what the pattern looks like now."
"I can provide a declassified version of the behavioral summary," Elaine said. "Send me Yuki's secure contact."
"Done by this afternoon."
The call ended. Marcus sat with his coffee and looked at the city through his apartment window — a clear August morning, the kind of day that felt indifferent to the complexity of everything happening underneath it. He thought about counter-narrative strategies and the difference between winning in court and winning in an information environment. He thought about fifteen years of journalism and two stories worth attacking.
He thought about the Sixth Gate and what building in the light meant when there were people who preferred the dark and were willing to construct their own version of visibility to compete with yours.
He opened his laptop and began drafting the note he would send Priya before Monday: the briefing for Caleb Wu, the security firm session, the Yuki contact for Elaine. Logistics that were the organizational form of the thing he was actually doing, which was building a structure that could hold the weight of being seen without collapsing under it.
The System updated, brief and without fanfare:
---
**Adversarial Modeling Lv. 5 → Lv. 6** *(counter-narrative threat correctly characterized before deployment; pre-positioning response architecture completed)*
**Sixth Gate: 17% complete.**
---
He read it and went back to his draft.