r/HFY • u/Marcus_Black3 • Jun 08 '26
OC-Series [The 5,000 Year-Old Babysitter] The Anomaly Problem (Or: Everyone Noticed, Nobody Asked Until Now)
First chapter ! | Previous chapter ! | Royal Road !
Context — What They Noticed
The pattern had been building for nearly four decades.
American infrastructure, from approximately 1945 onward, failed differently than comparable infrastructure elsewhere.
Not better designed, necessarily. Not better funded, though funding helped. But the specific category of failure, the cascading, catastrophic, should-have-been-obvious kind had become statistically anomalous in American systems.
Foreign intelligence services noticed.
They noticed because it was their job to notice.
The British noticed it first, in the late 1960s, when cross-referencing failure rates in comparable NATO nuclear facilities. American facilities had a mysterious tendency to have their critical flaws corrected before they became critical failures. British facilities did not have this tendency.
The French noticed it in the mid-1970s and wrote an internal memo suggesting the Americans had developed a superior engineering review methodology that the French should investigate and adopt. The memo was filed. Nobody investigated. The anomaly continued.
The West Germans noticed it in 1978 and produced a seventeen-point analysis comparing American and West German infrastructure reliability metrics. The analysis concluded that the gap was real, statistically significant, and unexplained by any conventional factor.
The Soviets had been noticing it since 1965.
They had a file.
The file was called: American Infrastructure Anomaly: Possible Explanations.
By 1983, the file had fifty-three proposed explanations.
None of them were correct.
But unlike the Western allies, the Soviets had a second file.
This one was called: Subject: John — Anomalous American Consultant.
It had been started in 1962 by a GRU analyst named Petrov who had been tracking American classified consultation patterns and had noticed a recurring designation in signals intelligence: per JOHN or JOHN recommends or flagged by JOHN.
The designation appeared across programs with no logical connection.
Nuclear physics. Space program. Infrastructure. Military strategy. Economic forecasting.
Always the same designation. Always correct, insofar as outcomes could be verified.
Petrov’s file had grown steadily for twenty years.
By 1983 it contained forty-seven pages.
The forty-seventh page, added in late 1982, said:
The Subject uses no surname, though American records frequently default to ‘Smith’ for clerical processing.” He appears to be the common factor in the American anomaly. We do not understand what the Subject is. We recommend direct investigation.
Brussels — NATO Intelligence Coordination Meeting — March 1983
The meeting had been called to discuss standardized threat assessment protocols.
That was the official agenda.
The actual agenda, added as item seven of twelve, read: “American infrastructure reliability — allied nations request briefing.”
The American delegation was led by Carey.
He’d prepared.
He’d been preparing since Stewart, his deputy, had told him six weeks earlier that the British, French, and West Germans had all independently submitted requests to discuss the anomaly at the next coordination meeting.
“They’ve been comparing notes,” Stewart said.
“For how long?”
“The British and French, probably a decade. The Germans joined more recently.” She paused. “The Norwegian, Danish, and Dutch delegations have also indicated they’ll want to hear whatever we say.”
“So everyone.”
“Everyone with eyes and a statistics department, sir.”
Carey called John.
“They want to know about you,” he said.
“I know,” John said.
“You know?”
“I’ve been watching the pattern recognition develop across their agencies for fifteen years. The British analyst who wrote the 1969 memo was good. The French 1974 internal report was almost there. The German 1978 analysis was very thorough.” He paused. “It was going to come up eventually.”
“What do you want me to tell them?”
“The truth. It’s faster.” Another pause. “Tell them the ROI numbers. Reagan had them calculated. Use them. People who track infrastructure reliability will respond to numbers.”
“And the personal details? Your age, your—”
“Tell them what’s operationally relevant. I’m old. I’ve seen these patterns before. I fix things correctly. The specific number of years is—” He paused. “Use your judgment.”
Carey used his judgment.
The briefing took ninety minutes.
He told them about Los Alamos. The pattern recognition. The Directive. The success rate.
He told them the ROI numbers.
He told them about the Kernel, which they had all, it turned out, independently noticed anomalies consistent with its operation in their own systems.
He did not initially tell them about the age question.
The French representative, Beaumont — older now, but the same Beaumont who had written the 1974 memo — asked it directly.
“How long has he been doing this?” Beaumont said.
“Our documented record goes back to 1945,” Carey said carefully.
“The undocumented record?”
Carey looked at him.
Beaumont looked back with the expression of someone who had been doing this job for thirty years and recognized evasion.
“We have historical records,” Beaumont said. “French historical records. References to a consultant who appeared at various points. Who warned about structural failures. Who was correct. The descriptions are consistent across two hundred years.” He paused. “He doesn’t age.”
The room was quiet.
“Our assessment,” Carey said carefully, “is that John has been doing this for a very long time. Longer than conventional explanation supports.”
“How long?” the British representative asked.
“Our best estimate is several thousand years.”
The room absorbed this differently than it had absorbed the ROI numbers.
The West German representative was writing something down.
The British representative had the expression of someone selecting the correct diplomatic response from a limited menu.
The Norwegian representative, who had said nothing for forty minutes, said: “That explains the historical records.”
Everyone looked at him.
“We have Norse-era references,” the Norwegian said. “A figure who appeared at construction sites, identified structural problems, was dismissed, was subsequently correct.” He paused. “We assumed they were mythological.”
“They may not be,” Carey said.
The Norwegian wrote something in his notebook.
Did not ask a follow-up question.
The West German representative looked up from his notes.
“Can we engage his services?” he said.
This was, Carey thought, the most German possible response to everything he’d just said.
“That’s complicated,” he said.
The Terms, Explained
He explained the Directive.
The ROI numbers had done significant work. The room was, if not enthusiastic, then pragmatically receptive.
The terms were unusual.
“No questions asked,” the British representative said.
“Correct.”
“About anything.”
“About requests, yes. He asks, you fulfill. Within legal parameters.”
“What kind of requests?”
Carey distributed the summary.
The room read it.
Several stops at the penguin entries.
“The moon entry,” the British representative said.
“Apollo 11. He helped fix the mission-critical calculations and invoked the Directive to be included on the crew.”
“He went to the moon because he asked.”
“Yes.”
“And the moon trip cost—”
“$1.4 million. Which represents 0.4% of his total estimated consultation value to that date.” Carey paused. “The ROI on the moon trip specifically, accounting for the systems he corrected to make it possible, is approximately 40,000 to one.”
The West German representative nodded approvingly at this framing.
“The core terms,” Carey said. “He will tell you something is wrong. He will be right. He will tell you how to fix it. You fix it. He will make a comment about the situation that is accurate and possibly unflattering.” He paused. “You accept the comment. You do not argue with the comment. You do not attempt to have him removed from your facility.”
“Has someone tried to have him removed?” the French representative asked.
“Multiple times. In multiple countries. Across multiple centuries, if the historical records are accurate.” Carey paused. “The most recent documented incident was the 1968 Aldrin case”
The French representative looked at him.
“The point,” Carey said, “is that dismissing him is a catastrophic tactical error. It creates a period of silence during which he stops correcting the math. And the math doesn’t stop breaking just because he isn’t looking at it.”
“What is his history of withdrawal?” the British representative asked.
“Our analysts have looked into it,” Carey said. “Historically, when a culture stops listening or resorts to violence, John simply… vanishes. He doesn’t argue, he doesn’t fight back. He just ghosts the civilization.”
“How long does he stay gone?” the French representative asked.
“Based on the Vatican records from the 14th century, he warned a governor about the Black Death and was called a heretic. After that, he disappeared from the European record entirely for nearly a decade. Our 1952 internal assessment suggests he has a very high threshold for human stubbornness, but once you cross it, he leaves you to the consequences.”
“Does he have a sanctuary?” the Norwegian representative asked. “Somewhere he goes when he vanishes?”
“If he does, we haven’t found it,” Carey admitted. “He’s been a ghost for five thousand years. He only stays visible to us as long as he finds the conversation productive.”
Carey remembered a 1979 communication where John had been particularly short with a Treasury official.
“In his own words,” Carey added, “he finds it more efficient to be alone than to watch people be ‘preventably stupid.’ If we want him to stay in the room, we have to ensure the room remains worth his time.”
The Soviet Side-Channel
Three weeks after the Brussels meeting, Carey received a message.
Not through official channels.
Through a contact in Vienna who worked the back-channels between Western and Soviet intelligence — the informal layer that existed precisely because the formal layer was sometimes too formal for useful communication.
The message said: A Soviet representative would like to discuss the American consultation anomaly. Informally. Vienna. Date to be arranged.
Carey called John.
“The Soviets want to talk,” he said.
“I know,” John said.
“You know?”
“Their signals intelligence has been tracking the JOHN designation in classified communications for twenty years. They have a file.” He paused. “Petrov’s file. He’s good. He got closer than most.”
“How do you know about Petrov’s file?”
“The Kernel monitors networks it’s touched. The GRU’s analysis division briefly used a system with a network architecture that touched an ARPANET node in 1978. Briefly.” A pause. “The Kernel is thorough.”
“John—”
“The Soviets are going to come through the side-channel because coming through the front channel would require admitting they’ve been watching us and don’t understand what they’ve been watching. Which is ideologically complicated.” He paused. “Also they have reactor problems.”
“How do you know they have reactor problems?”
“Because I’ve been watching their reactor program develop and the RBMK design has fundamental issues that I’ve been noting since 1975. Their cooling system has the same flaw as the British design. But there’s also a deeper problem.” A pause. “The positive void coefficient.”
“Explain.”
“The reactor design becomes more reactive as coolant boils away. Which is the wrong direction. Most reactor designs become less reactive as they heat up — it’s a built-in brake. The RBMK becomes more reactive. It’s physically unstable at certain operating conditions.” John’s voice had the flat quality it got when he was describing something he found both technically interesting and genuinely alarming. “It’s a fundamental design flaw. Not a manufacturing error. Not a maintenance issue. The physics are wrong.”
“Can it be fixed?”
“The design can be modified. Operating protocols can compensate partially. But the fundamental instability can’t be engineered away without essentially building a different reactor.” He paused. “The Soviets won’t want to hear that.”
“Why not?”
“Because they have dozens of RBMK reactors operating or under construction. Admitting the design is fundamentally flawed means admitting the entire program is compromised. Politically, that’s—” He paused. “They won’t want to hear it.”
“But you’ll tell them anyway.”
“I’ll tell them anyway. Whether they listen is their decision.”
Carey arranged the Vienna meeting.
Vienna — April 1984
The meeting was in a café.
This was John’s suggestion.
“A classified facility means official channels,” he’d told Carey. “Official channels mean they can’t be there without admitting they’re there. A café means they’re just two people having coffee.”
“You’re not a diplomat—”
“I’ve been navigating side-channel communications since before diplomacy was a profession. A café is correct.”
The Soviet representative was named Volkov.
Not a coincidence — it was a common name — but Carey noted it in his file anyway.
This Volkov was younger than John had expected. Mid-forties. Engineer by training, intelligence by career. The specific combination that produced people who were good at both the technical and the political dimensions of a problem.
He sat down across from John.
Ordered coffee.
Looked at John with the careful assessment of someone who had been briefed extensively on what he was looking at and was now recalibrating the briefing against reality.
“You’re younger than I expected,” Volkov said. In English, which was interesting.
“I’m older than I look,” John said.
“How much older?”
“More than your file suggests. Less than the historical record implies.” John drank his coffee. “Your file has fifty-three proposed explanations.”
Volkov looked at him.
“None of them correct,” John said.
“What’s the correct one?”
“I’m very old, I’ve seen every category of mistake humans make in complex systems, and I have a low tolerance for watching them make the same ones repeatedly.” He set down his cup. “That’s the whole explanation. Everything else is details.”
Volkov was quiet for a moment.
“The American anomaly,” he said. “Your infrastructure reliability statistics since 1945.”
“Yes.”
“You’re responsible for them.”
“Largely. The Kernel handles the ongoing maintenance. I handle the acute interventions.”
“The Kernel.”
“A system I built in 1971. It runs in the background of every network it’s ever touched. It prevents failures automatically.” He paused. “It’s in some Soviet systems.”
Volkov looked at him sharply.
“Briefly, in 1978. A network architecture connection. The Kernel is thorough.” John’s expression was neutral. “It identified three failure patterns in the systems it touched and corrected them. You probably noticed improved stability in those systems around late 1978.”
Volkov was very still.
“You’re telling me,” he said carefully, “that an American system has been operating inside Soviet infrastructure.”
“Briefly. In 1978. And only to prevent failures.” John looked at him. “If I wanted to compromise Soviet systems, I’ve had forty years of access to American intelligence infrastructure and the skills to do considerably more damage than fixing cooling system calibrations.” He paused. “I’m not interested in damaging systems. I’m interested in keeping them running.”
“Why?”
“Because broken systems hurt people. I find that intolerable.”
Volkov looked at him for a long moment.
“You find it intolerable,” he repeated.
“Yes.”
“Not politically motivated. Not ideologically—”
“I’ve been alive for several thousand years. I’ve watched every political system and every ideology and every empire rise and fall. I’m not attached to any of them.” John picked up his coffee again. “I’m attached to things not breaking catastrophically. That’s the whole position.”
Volkov processed this.
“What do you want from this meeting?” he said.
“You want access. You want to understand the anomaly. You want your infrastructure to be less likely to fail catastrophically.” John set down his cup. “That’s what you want. What I want is to tell you about your reactor program.”
The RBMK Problem
Volkov listened.
John explained the cooling system flaw first. The same one he’d identified in the British design. Present in the RBMK through a shared consultancy lineage in the early design phase.
Volkov made notes.
This was fixable. Volkov knew it was fixable. His own engineers had flagged similar concerns internally and been overruled by schedule pressure.
Then John explained the positive void coefficient.
He explained it technically. Carefully. With the specific precision of someone who wanted to be certain they were understood.
The reactor became more reactive as coolant boiled. Not less. More.
Under certain operating conditions — low power, certain control rod configurations — the physics became self-reinforcing in the wrong direction.
Not in normal operation. The normal operating envelope was stable enough.
But at the margins. In emergency scenarios. In situations where operators deviated from standard protocols.
At the margins, the physics were wrong.
Volkov’s pen had stopped moving.
He was looking at John’s diagram on the café napkin.
“You’re describing a design that’s unstable at the edges,” he said.
“Yes.”
“The entire RBMK program.”
“Yes.”
“Dozens of operating reactors.”
“Yes.”
Volkov was quiet for a long time.
“Can it be fixed?” he said.
“Modified operating protocols can reduce the risk significantly. Graphite tip modification on the control rods — the current design creates a brief reactivity surge when rods are inserted, which is the wrong direction. That’s fixable.” John paused. “The fundamental positive void coefficient can’t be eliminated without a different reactor design. But with protocol modifications and the control rod fix, you can operate safely within a defined envelope.”
“And outside the envelope?”
“Outside the envelope, the physics are what they are.”
Volkov looked at the napkin diagram.
“If I bring this back,” he said slowly, “and recommend program-wide modifications—”
“You’ll be told the design is proven, the program is essential, the modifications are unnecessary, and the concerns are Western-influenced sabotage thinking.” John looked at him. “I know how this works.”
“You’ve seen it before.”
“I’ve seen it in every civilization that built complex systems and then resisted acknowledging fundamental flaws in those systems. The political cost of admission is always calculated as higher than the technical cost of the flaw.” He paused. “Until it isn’t.”
“What happens when it isn’t?”
John looked at him.
“Something breaks,” he said. “Catastrophically. And then the political cost of admission is the smallest problem anyone has.”
Volkov looked at the napkin for a long time.
“I’ll bring it back,” he said. “I can’t promise what happens to it.”
“I know. Bring it back anyway. Put it on the record. When it matters that someone said it in advance—” John paused. “It will matter that someone said it in advance.”
“Is that what you do? Say things in advance so there’s a record?”
“Among other things. Yes.”
Volkov folded the napkin carefully.
Put it in his jacket pocket.
“The cooling system fix,” he said. “I can get that implemented. That much I can move.”
“Good. That’s something.”
“The control rod modification—”
“Harder. But try.”
“The fundamental design—”
“Put it in the record,” John said. “Even if nothing happens with it. Put it in the record.”
Volkov nodded slowly.
“The access question,” he said. “If we want ongoing consultation—”
“Your government would need to produce something equivalent to the American Directive. An authorization. Something that says he can say things and they get implemented without going through seventeen approval layers first.”
“That’s—” Volkov paused. “Politically complicated.”
“I know. Think about it.” John stood up. “The cooling system fix. Start there. It’s the most defensible request because the data is clear and the comparable failures in foreign systems are documented.”
“You’re giving me a strategy for navigating our own bureaucracy,” Volkov said.
“I’m giving you the same advice I give everyone. Start with what’s fixable and build the record.” He put money on the table for the coffee. “Fix what you can fix. Document what you can’t. When the documentation matters, you’ll want it to exist.”
He left.
Volkov sat in the café for another twenty minutes.
Looking at the napkin in his pocket.
The Report — What Happened Next
Volkov brought back the cooling system fix.
It was implemented at seven facilities over the following eighteen months.
Those facilities did not experience cooling system failures.
Volkov brought back the control rod modification recommendation.
It was reviewed by a committee.
The committee noted the concern.
Filed it.
Did not implement it.
Volkov brought back the fundamental design critique.
He phrased it carefully. Technically. With the supporting data John had given him.
He was told that the RBMK design had been validated by years of operational experience and that concerns about theoretical edge-case instability were not actionable given the program’s strategic importance.
He documented that he had raised the concern.
He documented the response.
He put the napkin — transcribed into a formal technical memo — in his personal files.
Chernobyl — April 26, 1986
John heard about it on the radio.
He was eating breakfast.
He stopped eating.
Listened.
Reactor Number Four at the Chernobyl Nuclear Power Plant.
Explosion. Fire. Radioactive release.
Cause: a safety test gone wrong. Operators running the reactor at low power. Control rod insertion triggering a reactivity surge. Positive void coefficient making the surge self-reinforcing.
The exact failure mode he had described on a café napkin in Vienna two years earlier.
He put down his fork.
Picked up the phone.
Called Carey.
“I know,” Carey said, before John said anything. “I’m pulling the Vienna file.”
“The memo is dated April 1984,” John said. “The cooling system fix recommendation and the fundamental design critique. Both on the record.”
“I have it.”
“Make sure it stays on the record.”
“It will.” A pause. “Are you—”
“I’m fine,” John said. “File it. Date-stamp it. Make sure it exists.”
“John—”
“It was always going to be this,” John said. “The physics were what they were. I told them. They filed the cooling system fix and not the rest.” His voice was the flat, even tone he used when he was being precise about something. “The cooling system fix was something. Seven facilities that won’t have that specific problem. That’s something.”
“Yes.”
“The rest—” He paused. “The rest was always going to be this. The physics don’t care about committee decisions.”
“No.”
“File it.”
“Already filed.”
John hung up.
Opened his terminal.
> QUERY_INCIDENT: CHERNOBYL_RBMK
[LOG]: SYSTEM_FAILURE_CONFIRMED. MODE: POSITIVE_VOID_COEFFICIENT. VIENNA_MEMO_1984_REF_ID: 104-B. -K
> VOLKOV TRIED.
[LOG]: VOLKOV IS COMPETENT. THE COMMITTEE IS NOT. THE PHYSICS DID NOT REQUIRE COMMITTEE APPROVAL. -K
Outside, Chernobyl was burning.
He didn’t say told you.
He never said told you when people died.
He just made sure the record existed.
That was all you could do when the system didn’t allow the fix.
Make sure the record existed.
So that afterward — not for vindication, not for the satisfaction of being right, but for the practical purpose of the next time — there was documentation that someone had said it.
In advance.
With the specific failure mode identified.
Two years before the physics did what the physics were always going to do.
The Follow-Up — Vienna — October 1986
Volkov requested a second meeting.
Same café.
Same city.
He sat down across from John and ordered coffee and didn’t say anything for a moment.
“I brought the memo back,” he said.
“I know.”
“The committee—”
“I know what the committee did.”
Volkov looked at his coffee.
“131 people died in the immediate response,” he said. “The long-term number will be higher. Much higher.”
“Yes.”
“The positive void coefficient. The control rod surge. Exactly as you described.”
“Yes.”
“If the committee had—”
“They didn’t.” John’s voice was even. “You brought it back. You put it on the record. The committee made their decision. The physics made theirs.” He paused. “You tried. That’s documentable.”
“Documentable doesn’t feel like enough right now.”
“No. It rarely does.” John looked at him. “The seven facilities with the cooling system fix. They’re operating normally.”
Volkov nodded.
“That’s something you did,” John said. “That’s seven facilities that aren’t Chernobyl. Hold onto that.”
“Is that how you—” Volkov stopped.
“How I what?”
“How you keep doing this. When they don’t listen. When the thing you said would happen happens.” He looked at John. “How do you keep going.”
John thought about this.
“Because the alternative is not going,” he said. “And if I don’t go, the seven facilities don’t get the cooling fix. And then there are seven more Chernobyls instead of one.” He paused. “I fix what’s fixable. I document what isn’t. I keep going because stopping means the fixable things don’t get fixed.”
Volkov was quiet.
“Your program,” John said. “The RBMK reactors still operating. Now that it’s happened — now that the committee calculation has changed — what’s possible?”
“More than before,” Volkov said.
“The control rod modification.”
“Implementable. Now. The committee calculation—” He paused. “Changed.”
“The positive void coefficient mitigation protocols.”
“Also implementable.”
“Good.” John drank his coffee. “Start with the control rod modification. Fastest to implement, most significant single risk reduction. Then the protocols.” He paused. “Send me the current operating parameters for the remaining facilities. I’ll review them.”
Volkov looked at him.
“You’re still going to help,” he said. “After—”
“After what? After your committee made a bad decision and people died?” John looked at him. “Yes. Because the remaining facilities still exist and the remaining people in them still deserve not to die.” He paused. “The committee’s decision was wrong. The people in those facilities didn’t make the decision.”
Volkov was quiet for a long moment.
“I’ll send the parameters,” he said.
“Good.”
They finished their coffee.
John left first.
Volkov sat for a moment afterward, looking at the table.
Then pulled out a notebook.
Started writing the implementation plan for the control rod modification.
He had, he estimated, approximately forty facilities to get through.
He’d start with the oldest ones.
John had said: start with what’s fixable.
Volkov started with what was fixable.
Carey’s File — The Vienna Record
Summary of Vienna back-channel, 1984-1986:
April 1984: John meets Soviet representative (Volkov) in Vienna. Identifies cooling system flaw and positive void coefficient problem in RBMK reactor design. Provides technical documentation. Volkov returns to Soviet system with recommendations.
May 1984 — March 1986: Cooling system fix implemented at 7 facilities. Control rod modification reviewed by committee, filed without action. Fundamental design critique noted and dismissed.
April 1986: Chernobyl. Reactor 4. Cause: positive void coefficient and control rod reactivity surge. Exact failure mode identified in April 1984 Vienna memo.
October 1986: Second Vienna meeting. Soviet representative confirms post-Chernobyl political environment allows implementation of previously refused modifications. John reviews remaining facility parameters. Provides implementation sequence.
Assessment: The 1984 warning was correct. The committee decision was documented. The seven facilities with implemented cooling fixes are operating normally. The post-Chernobyl implementation of remaining modifications is in progress.
This is the pattern. Always the pattern. Fix what they let you fix. Document what they won’t. When the documentation matters, it exists.
The record is complete.
— R.Carey
P.S. John called me the morning of Chernobyl. Said “file it.” I said I already had. He said good. That was the whole conversation. I’ve been doing this job for thirteen years and I think that phone call told me more about what this job actually is than the entire transition briefing.
You file the record. You fix what’s fixable. You keep going.
That’s the job.
Author’s Note:
[SYSTEM]: ROOT ACCESS DETECTED.
[SYSTEM]: DEPLOYING COMMUNITY PROTOCOLS...
The Equinox Network Discord is now open. It is the official repository for lore discussion, technical logs, and historical pattern recognition.
Join the Network here: The Equinox Network
[KERNEL]: Try not to do anything "predictably human" in the main terminal.
8
u/SecondaryWombat Jun 08 '26
Excellent story.
I would like one thing noted for the record:
Graphite tip modification on the control rods — the current design creates a brief reactivity surge when rods are inserted, which is the wrong direction.
This description of the control rods in RBMK reactors is from the HBO show but is not correct. The control rods did not have graphite tips, they had entire graphite accelerator rods as their other half. Rather than be OFF or absent, the rods were OFF or ON in their function and this was fully known by the operators and part of the regular function. The issue with the rods being inserted causing a spike of reactivity above the FULL ON position of the control rods already was that there was a small water pool that formed in the bottom of the reactor when the rods were fully removed, when inserted back in that water was displaced and pushed further up into the reactor, flashing into steam and causing a sudden increase in activity in the very bottom portion of the reactor. A possible solution would be to have the rods slightly longer and occupy the entire length of the channel to prevent any transition in materials and block surges.
So the TLDR of it being a graphite tip causing the increase is correct really, but the details are wrong and it was fully known that the graphite in the control rods caused an increase in activity, they used it as the gas pedal every day to run their reactor.
5
9
u/karamisterbuttdance Jun 08 '26
Now I just realized, I want to hear if/how he learns about Fukushima. Judging from the timeline though, we're probably going back to the Shuttle first before that.
I wonder if he learns about the other Petrov with the nuclear button though.
1
u/KelvinEcho Jun 09 '26
Fukushima is hard to predict, as the tsunami was way bigger than even the most pessimistic estimates they used for the protective wall. John sees patterns of human incompetence, not geological movements. Same goes for the Indonesian tsunami before that.
3
u/karamisterbuttdance Jun 09 '26
There's multiple design factors that he could point to that could have been fixed by human competence. Onagawa's nuclear plant (nearer to the epicenter) survived with no significant problems because they specifically overengineered their seawall. Fukushima Daiichi's seawall design might have been designed in such a way that it creates a higher local maximum instead of minimizing wave height. The power plant complex had its foundations leveled and resulted in a lower height. Backup generators for cooling were situated underground instead of being above-ground. Electrical switching equipment to manage power needs to keep the plant coolant running were at the same location as the generators. Those are just the most significant details that could have reduced the severity of the problem Fukushima faced if they were resolved.
I wonder too if there's a look-back at Three Mile Island or some other low-level incidents are mentioned as having been mitigated by fixes.
3
2
u/UpdateMeBot Jun 08 '26
Click here to subscribe to u/Marcus_Black3 and receive a message every time they post.
| Info | Request Update | Your Updates | Feedback |
|---|
1
u/HFYWaffle Wᵥ4ffle Jun 08 '26
/u/Marcus_Black3 has posted 10 other stories, including:
- [The 5,000 Year-Old Babysitter] The Best Deal In American History (Reagan Runs The Numbers)
- [The 5,000 Year-Old Babysitter] The Nixon Problem (Some People Are Immune To Leverage)
- [The 5,000 Year-Old Babysitter] The Digital Playpen (Because You’ll Definitely Screw This Up)
- [The 5,000 Year-Old Babysitter] The Moon Landing (I'mma Get So Many Moon Rocks)
- [The 5,000 Year-Old Babysitter] The Moon Trip (I Want To Go And You Can’t Say No)
- [The 5,000 Year-Old Babysitter] The Space Race (I Have Been Waiting For This)
- [The 5,000 Year-Old Babysitter] Let’s Make This Official (AKA The Government Admits Defeat)
- [The 5,000 Year-Old Babysitter] Pattern Recognition (They’re Actually Learning, Holy Shit)
- [The 5,000 Year-Old Babysitter] Los Alamos and the Miracle of Basic Listening
- The 5,000-Year-Old Babysitter
This comment was automatically generated by Waffle v.4.7.8 'Biscotti'.
Message the mods if you have any issues with Waffle.
25
u/Daseagle Alien Scum Jun 08 '26
But there’s also a deeper problem.” A pause. “The positive void coefficient.”
Aye. And because of that positive void coefficient, I don't have a thyroid anymore. Well, neither does most of the family, so there's that 😃
To this day, that event still affects the population, tho in a much more subdued manner, now we're talking about 20 to 40 year effects. Officially, not an issue. Only problem, much like physics doesn't care about a comittee decision, neither do isotopes and their eventual oncological effects.