Chapter 27: How to Be Unremarkable
Wednesday morning: a calculation on a communal whiteboard, third line, clear error in the boundary condition expansion.
Adam stood before it for six seconds.
The correction was obvious. The Synthesis Core had already generated it — three steps to fix the error, two more to extend the solution into useful territory. His hand twitched toward the marker.
He did not pick it up.
Instead, he wrote a small question mark next to the error and walked away.
This is the new protocol.
---
Three rules for the next thirty days:
Rule One: No unsolicited theoretical contributions above the level a visiting Level 2 esper documentation student would plausibly reach.
Rule Two: Ask questions instead of providing answers when possible.
Rule Three: If Synthesis Core produces anything whiteboard-worthy, it goes to the notebook and stays there.
Adam applied Rule One in three separate hallway conversations that day. In one, he watched Sheldon arrive at a conclusion that Adam could have accelerated by four steps. He wrote the acceleration in his notebook. He did not share it.
The Synthesis Core registered this suppression with mild internal static — like a radio signal being deliberately muffled, feedback from a system designed to output being forced to hold.
The muffling has a texture. I am learning the feeling of restraint from the inside.
---
[APARTMENT 4A — THURSDAY DINNER]
Sheldon was stuck.
The annotation-corner question — the one he had been worrying at since Adam's first week at Caltech, modified six times, approached from eleven different angles — had reached another dead end. His expression carried the specific frustration of someone who knew the answer existed and could not find the path to it.
Adam watched him stab at his pad thai with unnecessary force.
Rule Two. Ask questions instead of providing answers.
"What would the equation look like," Adam said, "if you started from the boundary condition instead of the initial state?"
Sheldon stopped.
His fork hovered mid-air. His eyes unfocused in the particular way they did when he was running calculations internally.
Thirty seconds of silence.
Leonard and Raj exchanged glances. Penny watched with the expression of someone who had learned to recognize this mode.
"That is..." Sheldon began.
He trailed off. Worked through something silently. His lips moved fractionally, forming numbers that only he could see.
"That is obvious," he said finally.
"I thought so."
"Why did you not say so three weeks ago?"
"You had not exhausted the other directions yet."
Sheldon's expression cycled through annoyance, evaluation, and something that was almost respect but too precisely calibrated to call that. His categorization system was processing new information.
Leonard, watching from across the table, made a note. Adam could see it in the way his attention sharpened — a scientist observing a phenomenon and deciding it was worth tracking.
The question method works better on Sheldon than direct answers. He arrives at conclusions as his own and files them differently.
The dinner continued. Sheldon was already sketching something on a napkin, the boundary-condition approach opening new possibilities. Howard made a comment about watching genius in real time. Bernadette corrected his definition of genius. Raj asked if anyone wanted more rice.
Normal. Comfortable. The suppression protocol holding.
---
[APARTMENT BUILDING HALLWAY — FRIDAY EVENING]
Penny caught him on the stairs.
"Hey."
Adam stopped, one hand on the railing. He had been working late — the documentation project required concentration, and concentration was easier after the building emptied out.
"Hey."
"You okay?"
Not a social ritual. The specific directness Penny reserved for genuine check-ins.
"I'm fine."
"You've been weird this week."
Weird. She noticed.
"I've been thinking about something."
"Want to talk about it?"
No.
"No."
"Okay."
She said it simply, without making it a conversation about the refusal. No pressure, no guilt, no follow-up questions designed to circumvent the boundary.
People who take no for an answer without making you feel bad about the refusal.
Adam had encoded this behavior. He knew exactly how she did it — the specific vocal register, the body language that communicated acceptance without withdrawal. He had catalogued Penny's social engineering toolkit extensively over seven weeks.
He still found it disarming.
"Thanks for asking," he said.
"Sure." She started up the stairs toward 4B. "If you change your mind, I'm around."
She did not look back.
Adam stood on the stairs for another few seconds, the secondary notebook pressing against his ribs, and filed the interaction under: things that happened without calculation.
---
[SHARED OFFICE — FRIDAY AFTERNOON]
Earlier that day, a pigeon had landed on the windowsill.
Sheldon's attempts to remove it had escalated through several phases: verbal discouragement ("You are not welcome here"), logical argumentation ("This is a physics department workspace, not a roosting site"), and finally direct appeal to the building maintenance protocols ("I will file a complaint with Dr. Seibert").
The pigeon had remained unimpressed.
Adam watched it for forty-five seconds with Molecular Conductor at passive range. He catalogued its feather composition without meaning to — keratin structures, microscopic barb arrangements, the specific pigmentation patterns of urban Columba livia. Body temperature: 41.2 degrees Celsius. Bone density: typical for the species.
Things I now know and did not particularly need to know.
The running list was getting longer. The Resonance Engine absorbed everything within range, whether or not Adam directed it to. The biological precision upgrade from Amy's lab had made it worse — or better, depending on perspective. He could sense the pigeon's stress hormones from across the room.
Eventually, the pigeon left. Sheldon declared victory. Adam returned to his documentation work and tried not to think about how much unnecessary information now occupied space in his memory.
---
[ADAM'S APARTMENT — FRIDAY NIGHT]
The thirty-day clock was running.
Adam opened his main notebook and wrote the start date. Below it, he listed the metrics that would indicate the protocol was failing:
Synthesis Core static increasing beyond current baselineInvoluntary output during conversations (answers given before the question method can redirect)Thermal accumulation spike from suppression effortDetectable behavioral changes noticed by observers
He looked at the list.
I am a person who tracks things. I am becoming a person who tracks whether my tracking is accurate.
The recursion was not comfortable.
He wrote: "Patience is a tool, not a state."
He read it back and was not sure if that was true. Patience felt like a state — something you were or were not. But maybe that was wrong. Maybe patience was something you practiced, like a skill, and the state was just the accumulated result of practice.
The Synthesis Core would have an opinion on this if I asked.
He did not ask.
The secondary notebook sat on his desk, the seven pages of accumulated output waiting for the day when he could interpret them. Page 3 was still incomprehensible. Page 4 was still incomprehensible. The EM prediction framework on pages 1-2 was still a confession document he could never let anyone find.
Thirty days of output suppression. Then reassess.
He closed the main notebook and went to the window.
The physics building was visible from here — just the corner of it, the lights in the upper floors still on where graduate students were working late. Sheldon's calibration log was in there somewhere, accumulating entries. The whiteboard note was on the side board, three people's handwriting now, a dialogue with an unnamed source.
On Monday, there will be a fourth set of annotations.
Someone would respond to Kripke's methodological question. Someone would extend the framework further. The conversation would continue without him, and the evidence trail would grow regardless of whether he participated.
This is what happens when you create something and cannot claim it.
It stops being yours. It becomes the building's. And the building keeps talking.
He turned away from the window.
The thirty-day clock ticked in the back of his mind.
He did not sleep well.
Get Early Access to New Chapters
Thank you for reading. For those who want to skip the wait, my Patreon is currently 21 chapters ahead of the public sites.
Schedule: 7 new chapters released every 10 days.
Benefit: Gain a significant lead of 7 to 21 chapters depending on your tier.
Support the project and start reading the next arc now: Patreon.com/IsekaiStories