The new rule showed up on a Thursday, which felt appropriate. Nothing good happens on Thursdays.
I was in the campus food court eating something that was technically a meal, half-watching the lunch crowd, half-reviewing what I'd observed in the two weeks since the Mythic fallout started. I'd been running a new log—just observations, no model, no predictions—trying to rebuild from raw data. Slow, methodical work. Standing in a demolished building and drawing blueprints from memory.
My phone lit up.
SYSTEM NOTICE
POLICY UPDATE v2.3
Effective immediately.
PROXIMITY RADIUS RULE:
Sustained proximity (15+ min, 3m range) to any confirmed system participant
now initiates passive evaluation.
No contact required.
Mutual awareness is sufficient.
I read it twice.
Then I looked up at the food court.
Four tables away: a girl I recognized from Arc 2 interactions. Confirmed participant. We'd been in the same general space for—I checked the time—roughly twenty minutes.
SYSTEM NOTICE
Passive evaluation in progress.
Current session: 22 minutes.
I picked up my tray and moved.
Three tables in the other direction: another one. Different person. Same problem.
I stood in the middle of the food court holding my tray, looking at the lunch crowd in a new way. Mapping them. Trying to remember who I knew was in the system, who I was uncertain about, what a safe zone even looked like when proximity itself was the trigger.
The food court did not have a safe zone.
I ate standing near the exit.
By the afternoon, I knew it had spread.
Not through any direct channel. Nobody had made an announcement, nobody had sent a memo. But I'd learned to read the texture of social behavior among the people who were in the system, and by 3 PM there was a specific kind of sideways awareness moving through the usual spaces. People sitting slightly farther apart than normal. People choosing routes that minimized sustained closeness.
They were adapting.
The thing about fear as a motivator is that it's fast. Rational deliberation takes time—you have to weigh options, consider consequences, run scenarios. Fear skips all of that and goes directly to behavior change. Within six hours of the policy update, people were already restructuring their daily geography around a rule they'd never agreed to.
I found three of them in the corner of the student lounge—not sitting together, technically, but clearly gathered. Coordinating distances.
Zoe was one of them.
She looked up when I came in, and her expression did the thing it sometimes did: starting toward relief, then catching itself.
"You saw it," she said.
"This morning."
"We're trying to figure out the threshold." She gestured at the loose cluster. "Fifteen minutes, three meters. What counts as mutual awareness. Whether it resets if you leave and come back."
She was building a protocol. Of course she was. Zoe's response to a new constraint had always been to immediately find its edges.
The problem was: finding the edges was exactly what the system wanted.
"Don't," I said.
She blinked. "Don't what?"
"Don't optimize for it." I looked at the others. "I know that's uncomfortable. I know it feels like the right move. But the moment you start building a compliance protocol around a new rule, you've accepted it. You've made it part of your operating system."
"So what's the alternative?" one of the others asked—a guy I knew loosely from Arc 3, whose name I kept forgetting to actually retain. "Just get evaluated?"
"Maybe."
The silence that followed was not comfortable.
"That's easy for you to say," Zoe said, not unkindly. "Your ledger is different."
She wasn't wrong. Four arcs of specific choices had given me more room to absorb passive evaluation without the same compounding impact. That wasn't a virtue. It was just arithmetic.
But it wasn't the point.
"The rule is coercive," I said. "It's punishing normal social behavior. If we all comply, it becomes normal. If we refuse to treat it as a hard constraint—"
"It still evaluates us."
"Yes." I didn't have a clean answer to that. I hadn't had a clean answer to anything since Arc 5 started. "But there's a difference between being evaluated and being governed. One of those ends when the session ends. The other one doesn't."
Zoe studied me for a moment. Then: "You're going to refuse the rule."
"I'm not changing my behavior because a fifteen-minute proximity timer told me to."
She nodded slowly, not like she agreed, but like she was filing the information. Like she was updating a model.
I left the lounge and walked out into the corridor, where the late afternoon light came through at a flat angle that made everything look slightly exposed.
My phone buzzed before I'd taken five steps.
SYSTEM NOTICE
Non-compliance logged: PROXIMITY RADIUS RULE.
Instability index: +4.3%
This is the expected outcome of refusal.
Your pattern is consistent.
I stopped walking.
Read it again.
Your pattern is consistent.
Not a warning. Not a consequence. A note. The kind of note you make about something you've already categorized—something that doesn't require further evaluation because it's already been understood. The system wasn't surprised by my refusal. It had anticipated it, filed it, accounted for it.
That was a different kind of uncomfortable than being punished.
I walked faster.
Behind me, through the lounge door I'd just come through, I heard Zoe start talking again. Laying out the threshold protocol. Working the edges. Making the new rule navigable.
And I thought: it works either way.
Comply, and it governs you. Refuse, and it catalogs you.
The rule was built for both responses. It won regardless.
I didn't have a third option yet.
But Arc 5 had barely started, and the system had just told me my pattern was consistent, which meant it thought it knew what I was going to do next.
I'd spent four arcs being predictable in ways that kept me functional.
Maybe it was time to be predictable in a different direction.