The temp looked surprised.
“That’s it?”
“That’s it.”
“What if payroll says no?”
“You’ll get notification and appeal.”
The facilities worker kept wiping tables.
Nobody looked at her as symbol.
Nobody called cleaning punishment.
Nobody told temp he was replaceable.
Nobody said supervisor decided whether he got paid.
Fifteen minutes later correction was approved.
$5.63.
Not a lot.
The worker noticed.
Money earned.
Money paid.
The supervisor returned to production.
The cleaner emptied trash.
Coffee machine hissed.
People talked.
No finance executive opened door.
No CEO removed yellow gloves.
No room froze.
Nothing happened.
And that was the best ending Naomi Carter could have asked for.
Because the goal was never to create a workplace where everyone feared that the temporary cleaner might secretly be the chief executive.
It was to create one where nobody needed to be.
But even after Naomi Carter was gone, the system she had helped rebuild faced a test she had never lived long enough to see.
It arrived without a shouting supervisor.
Without a toilet brush.
Without anybody pushing a yellow cart across a break room.
There was no humiliating phone video.
No furious CEO in an apron.
No executive running through a hallway with a payroll folder.
This time the problem arrived quietly, inside software.
And because no one could point to a single person and say that employee did it, the problem almost became harder to see.
Twenty-eight years after the Dayton confrontation, Carter Manufacturing no longer scheduled most temporary labor by hand.
A workforce-planning platform handled much of it.
The system estimated which workers were likely to report on time, complete shifts, accept overtime, and eventually qualify for permanent employment.
Managers still had final authority.
At least officially.
But the algorithm generated something called a Reliability Index.
Green.
Yellow.
Red.
Workers with high scores received more shift offers.
Workers with low scores received fewer.
Nobody at the plant called it punishment.
The software company called it optimization.
For nearly two years, nobody questioned it seriously.
Then a temporary worker named Brianna Cole noticed something strange.
Brianna was twenty-six.
A Black single mother with a six-year-old son and an associate degree she was trying to finish at night.
She had worked at Dayton for nine months.
Her attendance record was not perfect.
But neither was it bad.
She had missed two shifts when her son had pneumonia.
She had been late four times because the city bus arrived after the factory shuttle had already left.
She had accepted overtime whenever childcare allowed.
Her supervisors liked her work.
Her quality score was excellent.
Her safety record was clean.
And still, one month, her shifts suddenly dropped from five days a week to three.
She asked the staffing coordinator.
The coordinator looked at a tablet.
“The system reduced your availability priority.”
Brianna frowned.
“My availability didn’t change.”
“No.”
“Your reliability classification did.”
“What does that mean?”
The coordinator hesitated.
“It’s automated.”
“That didn’t answer me.”
The coordinator turned the screen slightly.
A yellow box showed beside Brianna’s name.
PREDICTED SHIFT COMPLETION: MODERATE RISK
Brianna stared.
“Predicted by what?”
“I don’t know.”
“Can you change it?”
“Not directly.”
“Who can?”
The coordinator shrugged.
“Corporate maybe.”