Hidden Load#
I — Maintenance Window#
I keep meaning to shut the alerts down.
I think about it in the abstract, the way you think about replacing a roof that hasn’t leaked yet. It’s the correct thing to do eventually. It’s just not urgent. Nothing is on fire. Nothing is screaming.
The permit queue is quieter than it used to be. That’s not good. Quiet in a system like this means work is happening somewhere else, badly.
I log in using the old credentials. They still work. I make a note to tell someone. Later.
The automated compliance checker flags three inspection notes for missing attachments. One of them is from leadership. I downgrade the severity. The checker isn’t wrong—it’s just literal. Context matters.
Someone in plan review has updated a template without checking downstream load cases. That used to be my job. Not updating it—preventing the need. I revert the change and leave a comment explaining why. I don’t include my name. The explanation is sufficient.
This company didn’t get acquired because of branding or vision. It got acquired because it worked. Startups trusted it. Regulators tolerated it. Private equity noticed it because the failure rate was low enough to monetize.
That wasn’t culture. That was architecture.
Most of that architecture isn’t visible. It lives in glue work, quiet checklists, worksheets, things nobody thinks about until they’re gone. I wrote a lot of those things. Not because I wanted to. Because nobody else would.
I could let it fail. That would be clean. Failure produces accountability. Someone would panic, hire consultants, spend months rebuilding something inferior. That’s how these things usually end.
But then the work would be gone. Not replaced—lost. All the small decisions that made it stable would evaporate. The system would regress. People would suffer, not dramatically, just inefficiently. More meetings. More errors. More blame.
That feels wrong.
So I update the template dependencies. I fix the logging issue in the intake ledger. I rewrite one calculation sheet that’s been bothering me for years. I leave it better than I found it.
I tell myself this is temporary.
I tell myself someone will notice and ask for a handoff. That I’ll explain everything properly. That I’ll finally document the parts that only exist in my head.
No one asks.
The system keeps working.
That’s the problem with doing a good job. It erases evidence that you were ever needed.
I close my laptop. I should stop. I know that. The thought passes cleanly through me — like a checklist that passes but isn’t enforced, I suppose.
I don’t feel angry. I feel aligned.
If I ever do stop, it should be because the work no longer needs me. Not because someone got uncomfortable.
That would be irrational.
II — Discovery#
Emergency Architecture Review#
(Conference Room, late afternoon)
“We’re not saying it’s broken,” the consultant says.
She’s already defensive. That’s new.
“Then why are we here?” the CEO asks.
“Because you asked for a health check.”
“And?”
“And the patient is… unusually stable.”
Legal clears his throat. “Stable is good.”
“Stable after a termination,” the consultant says. “That’s what’s unusual.”
The CEO leans back. “You’re saying Jeff left landmines.”
“No,” she says immediately. “I’m saying the opposite.”
Silence.
IT speaks up, cautiously. “We haven’t rolled out anything major since he left.”
“That’s not true,” Ops says. “We patched the review workflow.”
“And it didn’t explode,” Legal says. “So?”
“So,” the consultant says, tapping the table, “someone corrected the patch before it propagated.”
The CEO frowns. “How?”
She hesitates.
“Who?” he asks.
She slides a printout across the table.
Nobody touches it at first.
“That’s… revision metadata,” IT says finally.
“Yes.”
Legal squints. “Why is his name on this?”
“It’s not just his name,” she says. “It’s his idioms. Calculation sheet structure. Safety factors.”
“So he left a backdoor,” the CEO says.
“No,” she says again, firmer. “There’s no exploit. No data exfiltration. No privilege escalation.”
“Then how—”
“He never left.”
That lands badly.
“He was terminated,” HR says.
“Yes,” the consultant says. “But the system doesn’t know that.”
Ops laughs, once. “That’s not how systems work.”
She looks at him. “That’s exactly how systems work.”
The CEO leans forward. “How much to replace it?”
The consultant exhales. “Eight figures. Maybe more.”
“Months?” Legal asks.
“Eighteen, minimum.”
“Jesus.”
“And that’s if nothing fails in the meantime.”
IT looks pale. “What happens if these routines stop?”
The consultant doesn’t answer immediately.
“Say it,” the CEO says.
“Intake slows. Review backs up. Regulatory reporting drifts. Nothing crashes. You just… quietly fall out of compliance.”
“Can we reassign ownership?” HR asks.
“That won’t help.”
“Why not?”
“Because ownership isn’t authorship.”
The CEO pinches the bridge of his nose. “Could we hire him back?”
Everyone looks at him.
“As a consultant,” he adds quickly.
Legal nods. “That’s clean.”
HR nods. “That’s manageable.”
Ops says, “That’s expensive.”
The consultant says nothing.
“Would that work?” the CEO asks her.
She chooses her words carefully. “It would be the cheapest option.”
“Then do it.”
She finally looks uncomfortable.
“I don’t think money is the issue.”
The CEO frowns. “Money is always the issue.”
She shakes her head. “He doesn’t experience this as a transaction.”
“Everyone does.”
“No,” she says. “Some people experience it as responsibility.”
Silence again.
Legal flips a page. “There’s another problem.”
“What.”
“Alert routing.”
Ops groans. “Jesus, what now.”
“Several automated warnings are being sent to a personal address.”
“Whose.”
Legal looks up. “Chen.”
HR straightens. “Why?”
The consultant answers quietly. “Redundancy. Jeff doesn’t like single points of failure.”
“That’s a security risk,” Legal says immediately.
“She didn’t do anything,” Ops says.
“That’s not the standard.”
The CEO closes his eyes.
“If regulators see this—” Legal starts.
“We terminate her,” HR says. “Stop the bleeding.”
The consultant opens her mouth.
“No,” Ops says. “Wait.”
“We can’t wait,” HR says. “She’s compromised.”
“She doesn’t even like him,” Ops snaps.
“That’s irrelevant.”
The CEO holds up a hand.
“She goes,” he says.
Nobody argues after that.
Corridor Outside the Conference Room#
“You’re making this worse,” the COO says, keeping her voice low.
“We’re containing risk.”
“You’re amputating signal.”
“He’s trespassing.”
“He’s maintaining infrastructure.”
The CEO stops walking. “You’re taking his side?”
“I’m taking reality’s.”
“He’s undermining authority.”
“He doesn’t think authority is real.”
“That’s the problem.”
“No,” she says. “That’s your problem.”
They stop outside his office.
“You think he wants leverage,” she says. “He doesn’t. He wants stewardship.”
“And you think I should just—what—thank him?”
She stares at him. “Yes.”
“That’s insane.”
“No,” she says. “What’s insane is firing the only person who understands why this place works.”
“We fired her,” he says. “Not him.”
She closes her eyes.
“You just told him the system eats its caretakers.”
Text Exchange#
(Jeff — early morning)
Chen: They fired me.
Jeff: Why?
Chen: Security risk.
Jeff: For what.
Chen: You.
Jeff types. Deletes. Types again.
Jeff: That’s incorrect.
Chen: I know.
Jeff: Did they reassign the alerts?
Chen: I don’t think so.
Jeff opens his laptop.
Chen: Jeff, don’t—
Jeff: It’s fine.
Chen: I never even liked you.
A pause.
Jeff: I know.
Chen: You make people uncomfortable.
Another pause.
Jeff: Is the intake workflow still misfiring?
Chen: …yes.
Jeff: Okay.
Chen: That’s it?
Jeff: Yes.
Chen: I got fired and that’s all you have to say?
Jeff looks at the logs.
Jeff: They removed the wrong dependency in the load chain.
Chen: Jesus Christ.
Jeff: I’ll fix it.
Chen: You can’t fix everything.
Jeff stops typing.
Jeff: I can fix systems.
Chen: That’s not the same thing.
Jeff considers this.
Jeff: It should be.
Chen doesn’t reply.
Jeff disables the alert routing. He doesn’t reassign it.
They’ve mistaken care for threat.
That means the system can’t be corrected from inside.