The cleanup started before I got there.
I could tell because when I arrived at the community hall — the one the Meridian incident had spilled into, the one with the fluorescent exit signs and the folding chairs still stacked against the wrong wall — two people were already inside, and neither of them looked surprised to see me.
One was a man named Dresser. I knew him from two prior incidents, both of which had involved him explaining to me that the situation required a particular kind of narrative management. The other was a woman I didn't recognize, which probably meant she was new, or from a part of the process I hadn't intersected with yet.
"Ethan," Dresser said.
"You started without me," I said.
"We started for you." He gestured at the table between us, which had a stack of printouts on it. I didn't look at the printouts. "Sit down. This is going to be straightforward."
It wasn't going to be straightforward.
I sat anyway.
The woman I didn't recognize had a notepad but wasn't writing in it yet. She was the kind of person who waited to see what tone the conversation established before she decided how to document it. I appreciated that, in a neutral way.
"Here's the situation," Dresser said. "The Meridian incident is generating traction. The kind that doesn't fade without intervention. We need to shape the information environment before it shapes itself."
"What does that mean."
"It means we need a clear, credible explanation. One that doesn't create more questions than it answers."
I waited.
"Maya Reeves was present at the incident," he said. "Her presence raises questions about her connection to you. About the nature of that connection."
"Her presence was coincidental."
"Her presence looks non-coincidental."
"Because it was."
Dresser tilted his head. He did this when he was about to say something he'd pre-scripted. "What I'm proposing is that we reframe her involvement as a catalyst. Not a victim. Not a bystander. A participant who introduced an unknown variable." He paused. "It redirects the liability narrative."
So. That was it.
Not a request exactly. More like an offer presented in a way that made declining sound irrational.
"You want me to say Maya caused the incident," I said.
"I want you to provide context that allows the review board to reach that conclusion organically."
"That's the same thing."
The unnamed woman wrote something.
SYSTEM NOTICE
Damage Control tab added.
Active cost items: 3.
Reputational fallout estimate: moderate.
Compliance prompt pending your input.
I looked at the new tab on my screen without reacting visibly. The system had built a whole structure for this — a cost breakdown, a fallout projection, and an empty field waiting for me to populate it with whatever I was willing to sign off on. It was waiting the way forms wait. Patient. Ready.
I closed the tab.
"No," I said.
Dresser blinked. Not surprised, exactly. More like he'd had the script for this response ready and was just confirming which version of the conversation we were having. "Ethan, we're not asking you to lie. We're asking you to provide a framing that makes the situation legible."
"You're asking me to shift the narrative onto someone who doesn't deserve it."
"I'm asking you to protect the larger outcome."
"At her expense."
"At a manageable level of her expense," he said.
I actually laughed at that. Not a big laugh — just the kind that happens before you can decide whether it's appropriate. The woman with the notepad stopped writing.
"A manageable level," I repeated.
"These situations require someone to absorb cost," Dresser said. He was getting mildly impatient now, which meant I'd disrupted the script far enough that improvisation was starting. "You know that. The question is always who and how much."
I did know that. I'd known it since the first incident with the system, the first time a consequence had landed on someone adjacent to me who hadn't signed up for it. I'd been thinking about it since — the geometry of cost, the way proximity worked, the way the system treated collateral as a rounding error.
Which was exactly why I wasn't doing this.
"Not Maya," I said. "Not anyone. Find another explanation."
"There isn't one that works."
"Then don't find an explanation."
Dresser looked at me for a moment. Then he picked up his stack of printouts, aligned the edges against the table, and set them back down. The gesture of a man rescheduling rather than abandoning.
"I want you to understand," he said carefully, "that declining to cooperate creates a vacuum. And vacuums get filled. If we don't provide a narrative, someone else will."
"I understand that."
"And you're still declining."
"Yes."
He nodded. Then he looked at the woman with the notepad. She wrote something. Then he looked back at me with the expression of someone recalculating a timeline.
"We'll need to move faster, then," he said. More to himself than to me.
SYSTEM NOTICE
Refusal logged: narrative contribution declined.
Efficiency rating: decreased.
Revised timeline: accelerated.
Active cost items: 4.
I read it and didn't say anything.
Outside, through the smudged glass of the community hall's side window, the pavement was wet from rain that had stopped an hour ago. Takeout containers from somewhere nearby had blown against the curb. A woman walked past with a bag on each arm and didn't look in.
The Damage Control tab was still sitting in my system. Waiting. The cost items were ticking upward.
The system had not asked me to cooperate.
It had simply built the infrastructure for when I did, tightened the deadline, and started counting.
That was worse, somehow, than being asked.