Chapter 74: Someone Changed the Schedule
The safety observation had been moved earlier by three hours.
I found the change before anyone acted on it.
The sealed paper schedule and my responsibility copy showed the approved time. The live system displayed a new one. Its change ticket contained no scientific reason, no safety approval, and no request from the project manager.
Role: TEMPORARY ADMINISTRATOR.
No individual name appeared.
"Hold the sequence," I said.
The project manager froze every task dependent on the observation window. The independent safety observer restored the approved time only after the custodian captured both versions and the change history.
No participant was involved.
No material had been used.
No one was injured.
Those facts mattered more than the motive we did not yet know.
Julian arrived at the scheduling control room after the hold began.
"What do you want me to do?" he asked.
"Authorize an external access review and stay out of its conclusions."
"How broad?"
"Temporary credentials, schedule privileges, reception access, and any linked storage action."
He signed the scope without narrowing it to a convenient suspect.
The system administrator explained that temporary roles could be issued for maintenance, onboarding, or short project coverage. Several offices could request one. The role label did not prove whether an employee, contractor, or misused process stood behind the change.
The active-role list contained twelve temporary administrators issued during laboratory commissioning. Nine had expired. Two belonged to external maintenance teams and were suspended before they could enter the schedule system. The final credential had no person displayed on the review copy because the external auditor had not authenticated its assignment.
"Can you unmask it?" the project manager asked.
"After custody is verified," the auditor said.
The delay frustrated everyone. It also prevented a role field from becoming a public accusation before its source was tested.
Celeste's name did not appear.
Nathan's name did not appear.
I did not add either.
The external auditor preserved the ticket and disabled all temporary schedule authority. Permanent administrators kept only the access required to maintain the hold.
The project manager wanted to announce an attempted sabotage.
"Not yet," I said.
"Someone changed an approved safety schedule."
"That is the fact. Sabotage is a conclusion about purpose."
We issued an internal incident notice describing the unauthorized change and the corrective action. It asked staff to preserve records and avoid speculation.
That choice cost us speed. The validation could not resume until the access review completed. An investor call scheduled for later in the week would receive a delay without a dramatic explanation to soften it.
One director asked Julian to characterize the event as a harmless scheduling error.
"External audit has not classified intent," he said.
"Then call it a corrected discrepancy."
"It was an unauthorized change."
He chose the fact that exposed his own company to scrutiny.
Julian accepted the delay.
"If they ask whether our controls failed?"
"Say one control detected a change and the rest are under review."
"That makes us sound vulnerable."
"We are."
He used the sentence exactly.
I had worked under leaders who treated vulnerability as disloyalty. Their systems looked strong until the day every hidden weakness arrived at once.
Mercer Nova's control had been used. Another control had caught it. The honest description contained both.
By noon, the schedule system had returned to its approved state. The external auditor confirmed the change had been caught before execution. The first scheduled observation had not occurred, and no participant had been exposed to the altered time.
The broader review remained open.
At 12:18, the storage-control team added a second incident to the same preservation hold. A transfer request had already moved one sealed set of research materials between controlled locations.
The request did not use a temporary administrator role.
It used a visitor credential.
The auditor linked the two incidents only for preservation. No evidence yet proved one person or purpose connected them.
The location on the receiving line was the wrong controlled freezer.