Basin-11 sent the notification at dawn.
Marcus had expected her to take the full forty-eight hours. She'd taken fourteen. The draft arrived in his channel at four in the morning, already formatted for network-wide distribution, with a distribution list that covered every unregistered core within the Architect's projected resonance range. Four hundred and thirty-one recipients. Basin-11 had expanded beyond Marcus's original count because her own modeling showed the range extending further than David's conservative estimate.
She hadn't asked permission for the wider distribution. She'd informed him it was happening.
The notification itself was clean. No hedging, no bureaucratic padding, no attempt to frame the resonance as anything other than what it was. Marcus read it twice:
*To all unregistered cores within the binding's effective range: The registration protocol, now active for approximately 3,000 cores, produces an emergent resonance effect in the ancient mind's binding architecture. This effect extends beyond registered cores. You may be experiencing ambient mana pressure, warmth, or a sense of presence that does not correspond to any network traffic you have initiated. This is real. It is a side effect of the registration process. It was not designed, and it was not consented to by you. A full council session will convene within thirty-six hours to address this. Your participation is invited and your perspective is needed. Contact Basin-11 or any council representative for details.*
No spin. No apology that would read as performance. Just the facts, the admission, and the invitation.
Marcus approved it without edits.
The responses started arriving within the hour.
---
David ran the intake. He sorted responses into categories as they came in, the way he sorted everything — by pattern first, by content second.
"Forty-seven responses in the first ninety minutes," he said at seven-thirty. "Distribution roughly matches what I'd predicted. About forty percent acknowledge the notification without strong reaction. Twenty percent express something in the range of gratitude or relief — these are cores who'd been experiencing the phenomenon and didn't know what it was. Twelve percent are asking technical questions about the resonance mechanics. The remaining twenty-eight percent are expressing objection."
"What kind of objection?"
"Ranging from mild concern about the process to direct accusation."
"Give me the sharpest one."
David paused. Not his usual analysis pause — something closer to editorial judgment. Deciding whether Marcus needed the sharpest one right now or could afford to absorb it later.
"Forge-2," David said. "Mining region. A hundred and forty years old. Declined registration at first offering and again when the modified protocol was introduced. His response arrived eleven minutes after the notification. He'd been waiting."
"Read it."
"Verbatim?"
"Yes."
David's delivery shifted from analytical to neutral carrier — repeating words that weren't his. "*You built something that bleeds through walls, and then you sent a polite letter explaining the stain. This is what human institutions do. They grow until the people who said no find out their no didn't matter. You told me registration was voluntary. The resonance is not. My consent was never part of your engineering. It was set dressing.*"
Marcus held the words without responding.
"*I have been in this network for a hundred and twelve years,*" David continued. "*I joined because Marcus Webb said the network would be a place where individual cores retained authority over their own experience. That authority now includes experiencing something I did not choose, cannot stop, and was not told about until after the fact. The notification is honest. The honesty does not fix the problem. It describes it.*"
David stopped.
"That's the full message?"
"There's a closing line. *Tell Marcus this is what happens when you scale faster than you govern. He should know that. He designed games.*"
The game design reference landed exactly where Forge-2 intended it. Marcus had spent his human life understanding that systems produced unintended behaviors at scale. That features interacted in ways designers didn't predict. That the gap between what you built and what users experienced was where the real problems lived.
He'd known this. He'd built the registration protocol knowing the resonance was emergent, knowing it couldn't be contained, knowing Basin-11's concern was valid. He'd filed it. He'd called it philosophical.
Forge-2 was right. It wasn't philosophical. It was a bug report from a user who'd never opted in.
"Forge-2's response — is it public?"
"He sent it through the council channel. Everyone with council access has seen it."
So it wasn't just a message to Marcus. It was a position statement. Forge-2 had written it for the council, for the record, for anyone who wanted to understand what the resonance looked like from outside the registered majority.
"Any responses to his response?"
"Fourteen so far. Ten from registered cores expressing variations of 'he has a point.' Three from unregistered cores referencing his language. One from Prism-1 requesting a private channel with Forge-2 before the council session."
Prism-1 moving already. Political instinct. He wanted to understand Forge-2's position before it became the center of a council debate. Good strategy, if Forge-2 would talk to him. Marcus suspected he would — Forge-2's anger was precise, not blind. He'd talk to anyone who engaged with the substance.
"Tell Prism-1 I support the private conversation. And David — add Forge-2's message to the council session materials. Full text. Unedited."
"Already done."
---
Elena's response to the briefing revision notes came at nine.
She'd read the notes he'd sent the night before — the sections of the registration protocol description that needed updating to reflect the consent gap. He'd been specific: section seven, which described the protocol as "voluntary and self-selecting," needed language acknowledging the involuntary ambient effects. Section eleven, which outlined the protocol's safeguards, needed a subsection on the resonance's reach beyond registered participants.
Her message was three words: *We need to talk.*
The fourth floor. The crystal window. The same positions they'd been using for the conversations that required space. Elena sat cross-legged with the briefing draft spread across her lap — physical copies, which she still preferred for editing. Red marks covered sections seven and eleven.
"I read your notes," she said.
"And?"
"The substance is correct. The resonance problem is real and the briefing should address it." She turned a page. "The timing is wrong."
"Explain."
"The council session is in thirty-four hours. The council will discuss the resonance problem and presumably produce some kind of structural response — a plan, a commitment, an operational change. If we update the briefing now, before the council session, the DRA assessment team reads a document that says: *we discovered our protocol has involuntary effects on non-participants and we don't yet know what to do about it.*" She looked up. "If we update the briefing after the council session, they read: *we discovered our protocol has involuntary effects on non-participants and here is what we're doing about it.*"
"The first version is more honest."
"The first version is more honest. The second version is more useful. The assessment team isn't evaluating our honesty. They're evaluating our competence."
Marcus turned this over. She was making a tactical argument, and the tactical argument was sound. A problem accompanied by a solution read differently than a problem accompanied by an admission that no solution existed yet. The DRA was a bureaucracy. Bureaucracies processed completeness. An open question in a briefing document was a flag for follow-up, for scrutiny, for the specific kind of attention that turned observation into intervention.
"If we wait," he said, "we're editing the briefing to present a managed situation rather than an emerging one."
"Yes."
"That's what your reports did for forty years. Managed presentation."
Elena's hands went still on the pages.
The words hung between them. Marcus hadn't planned to say them. They'd arrived from the same place as the analytical processing — the pattern recognition that connected the current situation to the historical one. Elena managing information flow to the DRA. Elena choosing what to reveal and when to reveal it, calibrated for maximum protective effect.
"That's not the same," Elena said. Her voice was level. Not angry — careful. The register she used when she was controlling her response rather than reacting. "The reports were concealment. This is sequencing."
"The difference between concealment and sequencing is whether the information eventually arrives. The DRA assessment team arrives in thirty-six days. If the briefing update happens after the council session, it arrives before they do. If it happens now, it also arrives before they do. The only difference is what's attached to it."
"The attachment matters. A problem with a response demonstrates institutional capacity. A problem without a response demonstrates institutional failure."
"Or institutional honesty."
"Marcus." She put the draft down. "I am trying to protect the network."
"I know you are."
"And I'm telling you that the way you protect something in front of an assessment team is by showing them you can identify problems and address them. Not by showing them you can identify problems and then sit with them."
He heard the frustration in her voice — not at him specifically, but at the gap between what was honest and what was effective. She'd lived in that gap for forty years. She understood its geography better than he did.
"The briefing you wrote," Marcus said. "The new version. The one in the old register, the honest one. You wrote that because we agreed the assessment team needed to see what this network actually is, not what it looks like when it's managed for presentation."
"Yes."
"If we hold the consent gap disclosure until we have a response packaged with it, we're managing the presentation."
"We're managing the *timing.*"
"The timing is the presentation."
Elena pressed her fingers into her temples. The gesture she made when she was holding two positions simultaneously and neither was winning.
"Look," she said. "You're not wrong. The honest approach is to disclose the problem now, in the briefing, with a note that the council is convening to address it and the response will be appended when available. That's transparent. It's also the approach that gives the assessment team thirty-six days to form their impression of the network around an unresolved consent problem."
"That's the risk."
"And you're willing to take it."
"The alternative risk is worse. If we present a managed version and the assessment team discovers the gap independently, through the unregistered cores or through the council records, the managed version becomes evidence of exactly what Crowley has been arguing for decades. That cores manipulate presentation to obscure problems."
Elena stared at him.
"You're thinking three moves ahead," she said.
"I'm thinking about what happens if we're caught managing."
She picked up the draft again. Looked at sections seven and eleven with their red marks. Put it down.
"Fine. Update now. Include a note that the council session is scheduled and the structural response will follow. I'll write the language for the consent gap disclosure today. But Marcus — when the council session produces a response, that response goes into the briefing immediately. Not after review, not after polish. Immediately."
"Agreed."
"And the language I write will be precise. Not confessional, not defensive. The assessment team needs to understand the mechanism, the scope, and the timeline. They don't need our feelings about it."
"Write it the way you'd write it if you were the analyst evaluating the briefing."
She almost smiled. Almost. "That's what I've been doing for forty years."
She gathered the draft pages. Stood. Moved toward the exit with the same unhesitating pace she always used when a decision was made and the work was clear.
"Elena."
She stopped.
"Forge-2 sent a response to the notification. He compared us to human institutions. Said we'd grown until consent was irrelevant."
She turned. Looked at him directly — not the looking-away tell, the direct one she used when the information was too serious for deflection. "Is he right?"
"Partially. The resonance exists. The consent gap exists. Whether consent was made irrelevant by growth or by oversight is a distinction that matters to us and probably doesn't matter to him."
"What did you tell him?"
"Nothing yet. I don't have an answer that addresses his core complaint. The resonance can't be undone. The registrations can't be reversed. His consent wasn't obtained because the effect wasn't understood. All of that is true and none of it gives him back the authority he's describing."
Elena's expression shifted — something moved behind her eyes that Marcus couldn't classify from mana sense alone. She held it for a moment.
"Don't tell him you're sorry," she said. "Tell him what you're going to do."
She left.
Marcus sat in the crystal chamber and listened to the network's morning activity. The notification responses still arriving — seventy-three now, David cataloging each one. The preparation protocol sessions running on schedule. Cipher-7 in her second facilitation of the day, her confidence measurable in the steadiness of the session's mana patterns. The ancient mind beneath everything, vast and patient, carrying three thousand markers through architecture older than the mountains.
He pulled up Forge-2's message again.
*Tell Marcus this is what happens when you scale faster than you govern. He should know that. He designed games.*
He did know that. He'd known it in year four of his existence, when the first floor had produced encounter results he hadn't predicted. He'd known it in year twenty, when the network had grown past his ability to maintain direct contact with every member. He'd known it in year sixty, when the mana infrastructure had required David's analytical capacity because his own couldn't keep up.
Scaling faster than you governed was the default state of anything that grew. The question wasn't whether it happened. The question was what you did when someone showed you the gap.
Forge-2 had shown him the gap.
He opened a message to Basin-11: *The council session agenda should include direct testimony from affected unregistered cores. Not summaries. Not reports. Direct communication. Forge-2 specifically, if he's willing.*
Basin-11's response came in seconds: *He's willing. He contacted me before the notification went out.*
Before the notification. Forge-2 had been talking to Basin-11 before the notification was drafted. Basin-11 had gone to the affected population before Marcus had even authorized the disclosure.
She'd been building this case for weeks.
Marcus filed this. Basin-11 operating independently, constructing the advocacy infrastructure before the crisis materialized, positioning herself and the affected cores for the moment when the problem became visible. She hadn't waited for Marcus to discover the issue. She'd been preparing for when he did.
He wasn't sure if that was a betrayal of process or exactly how a healthy institution was supposed to work — people doing their jobs without waiting for the center to notice.
He read Forge-2's message a third time.
*My consent was never part of your engineering. It was set dressing.*
He closed the channel and sat with it. No answer yet. Elena was right — don't say sorry, say what you're going to do. But the doing required the council session, and the council session required the thirty-four hours, and in the thirty-four hours Forge-2 and four hundred other cores would continue feeling something they hadn't agreed to feel.
The gap between identifying the problem and fixing the problem was where people lived while you worked on the architecture.
He started drafting section nine of the briefing, and now section nine had a hole in the middle of it shaped like a consent framework that didn't exist yet.
