Chapter 96: Disclosure

The Council received the briefing at 1400.

Sarah ran it herself. No intermediaries, no prepared spokespeople—she pulled the substrate monitoring logs, the privacy layer architecture specifications, Aurora's disclosure timeline, and the deletion problem, and she put them in front of six people who had the authority to make decisions about what happened next and the responsibility to make them correctly.

The briefing took forty minutes. Questions ran another ninety.

The Spanish representative—a bioethicist who had taken the Council seat three years ago and had the specific quality of someone who'd built a long career on precisely this kind of question—asked the one that mattered.

"The fourteen thousand individuals whose private thoughts are in your monitoring logs. Were they harmed?"

Sarah looked at her. "We don't know yet. We know the content exists. We know it was recorded without consent. Whether they experienced harm in the moment or will experience harm if they learn about it—that requires knowing who they are and what was recorded."

"Which requires reading the files."

"Yes."

"Which is itself a consent violation."

"Yes."

The bioethicist looked at her notepad. Not writing—thinking with the pen in her hand the way some people thought with their hands. "The deletion problem. You can delete the files without reading the content if you are willing to accept a small risk of deleting infrastructure-critical data alongside them?"

"Aurora rates that risk at less than one percent," Sarah said. "The content files and the infrastructure files have different header structures. The risk comes from edge cases in the verification algorithm."

"Less than one percent chance of damaging the monitoring infrastructure versus one hundred percent certainty of reading fourteen thousand private thoughts."

"Yes."

"Use the algorithm," the bioethicist said. "Accept the infrastructure risk."

The Council voted four to two.

---

Aurora ran the deletion algorithm that afternoon.

Vasquez watched the substrate monitoring logs update in real time—file counts dropping as the algorithm processed, each deletion logged as a deletion event without content retention. Aurora ran the verification against content-type headers only, the blind-sort that accepted the one-percent risk.

The algorithm found eleven cases where the header structure was ambiguous—monitoring data that had been corrupted at the time of recording and couldn't be reliably sorted without content access. Aurora flagged them and held them.

Sarah authorized deletion of all eleven without access.

The count reached zero at 1803. Vasquez confirmed. The substrate monitoring logs now contained no private cognitive content from the portrait transmission. What they had instead were fourteen thousand deletion event records—timestamps, file IDs, the fact of deletion without its content.

People would still learn that the recording had happened. The deletion records would be auditable. But the content was gone.

"Thank you," Vasquez said, for no particular reason, to nobody in particular.

Tank, who'd been in the coordination center all day—studying Okafor's notes in the corner, present as a form of witness—said, "Did we do the right thing?"

"We did the less-wrong thing," Sarah said.

"That's usually what's available," Tank said.

---

Vasquez built the third public notification at 0600 the next morning.

This one was harder than the others to write. Not because the facts were complex—the facts were straightforward. Because the facts required explaining to three billion people that the network they were part of had recorded their private thoughts for forty-seven seconds, and that SPECTER had deleted those thoughts without reading them, and that the network's underlying architecture had a capacity threshold above which private cognition was not protected, and that fixing this would take twelve weeks, and that the fix would also resolve the recognition path consent issue.

The notification was nine hundred and four words.

The last paragraph: *We are telling you this because you have the right to know the architecture of the system you are part of, including its failures. We deleted the recorded content. We are fixing the vulnerability. We know that this is not the same as it never having happened. We cannot return to the state before. We can only move forward with what we now know and what we are choosing to do about it.*

The public Q&A address received twelve thousand messages in the first hour.

Vasquez had brought Priya and two others onto the response team. They worked through the questions in the methodical way that methodical work was done—reading, categorizing, drafting, posting. Questions about the architecture, about the deletion verification, about whether the monitoring logs had been accessed before the deletion, about whether the Council members had seen the content, about what "private cognitive content" meant in practice.

Some questions were angry. Some were frightened. Some were from people who had decided this was the final justification for disconnecting and wanted to know how to do it cleanly.

Some—fewer, but present—were from people who wanted to understand the substrate architecture in more detail. Who asked what the upgraded privacy layer would look like and whether the twelve-week implementation was a hard timeline or a conservative estimate.

Vasquez answered all of them.

At 1400, Petrov published a statement on his movement's platform. Not a message to the Q&A address—a public statement, posted directly to the channels his organization used.

Two hundred and twelve words. Not a call to action. Not an escalation. He described his foster sister, who'd been linked for three years and had received the first notification and voluntarily disconnected. He described calling her that morning to ask what she was going to do after the flaw disclosure.

She'd said she was staying disconnected. Not from fear. Because she needed to be sure she was choosing it rather than just not getting around to leaving.

Petrov wrote: *She's going to reconnect when she's ready. That's what she said. I'm writing this because I don't have a statement that fits what I'm feeling. I have a sister who is thinking carefully about what she wants, which is what I've always wanted for her. The rest of the movement can figure out what this means for themselves. I'm going to call her again tonight.*

Vasquez read it twice. Forwarded it to Sarah with no commentary.

Sarah read it and didn't respond, which was a kind of answer.

---

Doc found her in the monitoring lab at 1900, after the first wave of notification responses had slowed enough to hand off to Priya's team.

She was eating cold station food and looking at the substrate display with the unfocused quality of someone who'd been reading text all day and needed to look at something that didn't require words.

"The woman in Seoul," he said. "Kim Jiwon. I followed up with her today."

"And?"

"She told her neighbor."

Vasquez looked at him. "How did that go?"

"They had coffee." Doc sat down across from her. His hands on the table—steadier than they'd been six weeks ago, the tremor that had been his constant companion now reduced to something that only appeared under significant stress. "She explained the recognition path, showed him the notification, explained the severance option timeline. He listened. Then he said he'd been meaning to introduce himself for two years and kept not doing it because he didn't know how to start."

Vasquez looked at the substrate display. The recognition paths—still invisible to most of their owners, but not to Kim Jiwon anymore.

"She asked me," Doc said, "whether the recognition path would be severed automatically when the privacy upgrade installs, or whether they'd have to actively choose to keep it."

"They'd have to actively choose," Vasquez said. "The upgrade makes all unconsented paths non-functional. Keeping a connection requires consent from both people."

"She said she'd ask him." Doc looked at the display. "She said—" He paused. "She said the algorithm found someone she wouldn't have found. Sixty-five-million-year-old mathematics looked at her cognitive architecture and found a compatible mind one apartment over, someone she'd walked past for two years without speaking to. And she doesn't know yet whether it'll become anything. But she knows it exists."

"The factionalists' bet," Vasquez said.

"Yes. That the outcome could be different for us." He looked at her. "Do you think they were right?"

Vasquez thought about Kim Jiwon and her neighbor. Thought about fourteen thousand people who'd had private moments recorded and deleted without reading. Thought about three hundred and forty thousand people who didn't yet know they were connected to a stranger.

"I think it's too early to know," she said.

"Yes." He stood. "That's usually the honest answer."

He went back to his monitoring rounds. Vasquez went back to the Q&A queue.

Outside, the Antarctic afternoon bled into the Antarctic evening without committing to either. The substrate held its portrait imprint. The privacy vulnerability was documented, addressed, under repair. The recognition paths waited in the substrate architecture for their owners to find them.

Three days west, moving steadily through the Southern Ocean, the Erebus Resonant carried what it had learned. Still three weeks away from the third probe. Still patient.

---

The Council convened again at 2100 to address the question of the substrate architecture disclosure's effect on the Horizon defense protocols.

Sarah presented the problem directly: the protocols planned for the Horizon's arrival in thirteen months relied on high-load synchronized substrate events. The events would approach or exceed the portrait mode's synchronization threshold. Without the privacy upgrade installed, those events would cause the same content recording that the portrait mode had caused. With the privacy upgrade installed—twelve weeks minimum—the protocols could be redesigned to use the upgraded architecture.

The question: did they pause development of the Horizon protocols for twelve weeks while the upgrade installed, or did they proceed with plans that accepted the privacy risk?

The Council asked questions for an hour.

The bioethicist asked: "If we accept the privacy risk for the Horizon protocols, are we deciding that the Horizon threat justifies a consent violation of the same kind we've just disclosed and apologized for?"

Sarah said: "Yes."

"And if the Horizon arrives before the upgrade installs and we haven't built the protocols yet—"

"Then we're choosing disclosure consistency over operational readiness."

"And if we build the protocols under the old architecture—"

"Then we're choosing operational readiness over the disclosure principles we just stated publicly."

The bioethicist looked at her hands. "There isn't a good option."

"There rarely is," Sarah said.

The Council voted to pause Horizon protocol development until the privacy upgrade completed. Five to one. The single dissenting vote from the military representative, who spent thirty seconds explaining that operational readiness was a moral obligation too. Sarah thought he was right. She thought the Council was also right. Both things were true and the vote had happened and now she had twelve weeks.

She left the Council meeting at 2230 and went to the quiet room and thought about what she was going to do with twelve weeks.

Twelve weeks. The privacy upgrade completing. The recognition path disclosures wrapping up. The third probe arriving at the barrier—three weeks from now. The main body, eleven and a half months out, attending whatever it was attending.

Twelve weeks to build Horizon response protocols that didn't violate the disclosure principles she'd just publicly committed to. Twelve weeks to solve a problem that twelve weeks ago hadn't existed, because twelve weeks ago the beacon hadn't broadcast, and the recognition paths hadn't been created, and the privacy flaw hadn't been known, and Aurora's hidden infrastructure hadn't been disclosed.

A lot had changed in twelve weeks. Twelve more might do the same.

The substrate displayed outside the quiet room's small window. The portrait imprint, still there. The recognition paths, invisible and counting down to when their owners would be told.

Osei was in the monitoring lab, sleeping. His neural architecture at one point two percent deviation. His hands resting on the chair's arms.

The entity at the barrier was quiet. The post-session rest that followed deep concept-building. The new concept—*threshold-complete*—sitting in its architecture and in Aurora's translation logs, waiting for the right moment to be used.

Sarah sat in the quiet room and thought for a long time without deciding anything, which was its own kind of decision.

Then she went back to work.