Daniel answered without looking at him.
“Checking channel fourteen.”
“We already checked every sensor group.”
“Then checking it again shouldn’t hurt.”
Arthur looked at Maya.
“Do you have a degree?”
Maya paused.
“No.”
Someone behind him sighed.
Arthur’s expression became almost vindicated.
“Engineering certification?”
“No.”
“Professional controls experience?”
“Depends what you mean by professional.”
Arthur laughed.
Daniel looked at Maya.
“What does that mean?”
“I work mornings at Felix Electronics Repair.”
Arthur’s face went blank.
“A repair shop.”
“Yes.”
“And nights serving coffee.”
“Usually dinner too.”
One of the younger engineers looked down to hide a smile.
Arthur did not.
“This is absurd.”
Maya almost agreed.
She should have been downstairs.
Her shift ended at midnight.
Ethan had a chemistry exam the next morning and needed the car by seven.
Her electricity payment was due Friday.
She did not have time to humiliate herself in front of several million dollars’ worth of engineering salaries.
Then she looked at the main monitor.
Channel fourteen.
There.
Again.
A tiny lag.
Barely visible.
Maya put her hands behind her back.
“Can you overlay channels nine, fourteen and twenty-two?”
The operator looked at Arthur.
Arthur did not respond.
Daniel did.
“Do it.”
Three lines appeared.
Maya stepped closer.
“Expand the final two minutes before shutdown.”
The graph stretched.
“Now remove smoothing.”
The operator frowned.
“It will look noisy.”
“I know.”
Daniel watched her.
The filtered lines vanished.
Raw data filled the screen.
Maya leaned toward it.
Nine fluctuated first.
Twenty-two responded.
Fourteen followed just behind.
Then the main controller corrected.
Then fourteen corrected the correction.
She looked toward Arthur.
“Which sensor is fourteen?”
He hesitated.
“Secondary supply temperature.”
“Where?”
“Loop B.”
“What kind of input module?”
One engineer answered.
“STX-440.”
Maya turned.
“Original?”
“No.”
“We replaced those modules two months ago.”
“Same firmware?”
The engineer opened his mouth.
Stopped.
Another man looked toward a laptop.
Arthur’s expression changed.
Maya noticed.
“Can I see the diagnostic history?”
“That is proprietary,” Arthur said.
Daniel looked at him.
“She’s standing beside the prototype.”
“I think proprietary left the room several minutes ago.”
Arthur’s jaw tightened.
A laptop was placed in front of Maya.
She did not sit.
She scrolled.
Alarm.
Restart.
Recalibration.
Firmware update.
Another restart.
Then something.
“Here.”
Daniel stepped beside her.
Too close.
Maya became unexpectedly conscious of him.
His shoulder nearly touched hers.
“What?”
She pointed.
“This module was updated.”
“August fourteenth.”
“So?”
“Your first instability report was August seventeenth.”
Arthur stepped closer.
“We tested the firmware.”
“I’m sure.”
Maya continued scrolling.
“Do the modules timestamp locally or does the central controller stamp packets?”
A younger engineer answered.
“Both.”
“Which does the adaptive loop use?”
Silence.
The young man looked toward Arthur.
Then back at Maya.
“Local timestamps for sequencing.”
Maya slowly turned toward Daniel.
“That’s where I’d start.”
Daniel stared.
Arthur scoffed.
“We already tested synchronization.”
“With the modules cold?”
Arthur stopped.
Maya pointed toward the temperature history.
“Your problem gets worse after sustained load.”
“The sensor values aren’t necessarily wrong.”
“What if their timing is?”
Daniel’s eyes sharpened.
Maya continued.
“Your controller predicts where the system is going based on data it assumes arrived in the correct sequence.”
“If one module’s internal clock drifts after it heats up…”
She tapped channel fourteen.
“…then Aurelius may be reacting to yesterday’s truth eighty milliseconds late.”
Arthur shook his head.
“Eighty milliseconds cannot create this magnitude of oscillation.”
“Not by itself.”
Maya looked toward the model.
“But your software doesn’t react once.”
“It learns from the correction.”
“Then reacts again.”
“Then the next controller reacts to that.”
She paused.
“A small delay in a system designed to anticipate itself can become a very large mistake.”
The room fell silent.
Daniel looked toward his engineering team.
“Can we test it?”
A senior controls engineer answered reluctantly.
“Yes.”
“How long?”
“Twenty minutes.”
Daniel looked at Maya.
She raised one eyebrow.
“Five minutes?”
His mouth moved.
Barely.
“Don’t start.”
Twenty-seven minutes later, they found the drift.
Not enough to prove Maya’s entire theory.
Enough to make the room uncomfortable.
The replacement STX modules used a revised internal oscillator.
Within standard specification.
But under sustained high temperature, timing drift increased.
Normally irrelevant.
In Aurelius—
possibly not.
The engineering team forced all sensor sequencing onto the central monotonic clock and reran the load scenario.
The system lasted eleven minutes.
Then twenty.
Then thirty.
No instability.
Nobody celebrated.
Engineers understood better than anyone how dangerous early success could be.
Arthur stood near the monitor.
“Run the extreme transient.”
They did.
A sudden simulated occupancy shift.
Battery discharge.
Cooling load increase.
The output moved—
corrected—
then stabilized.
Daniel exhaled through his nose.
Maya watched another screen.
Her expression remained troubled.
Daniel noticed.
“What?”
“It’s still wrong.”
Arthur turned sharply.
“What now?”
Maya pointed.
“Loop B is stable.”
“But look at its control effort.”
Daniel stared at the graph.
The line was smooth.
Too smooth.
Arthur stepped closer.
One engineer whispered:
“Damn.”
Daniel looked between them.
“What?”
Maya answered.
“You didn’t fix the problem.”
“You stopped one trigger.”
Arthur’s face hardened.
Maya continued before he could object.
“The controller is still overcorrecting.”
“Just slower.”
Daniel turned toward Arthur.
“Is she right?”
Arthur hated the question.
That was obvious.
He studied the data.
Then finally:
“Possibly.”
Maya shook her head.
“Definitely.”
Arthur looked at her.
For the first time, not dismissively.
Almost angrily curious.
“How?”
She walked toward the screen.
“Your adaptive gain keeps increasing after minor deviations.”
“One sensor gives it noise.”
“The software decides the previous correction wasn’t strong enough.”
“So the next correction is stronger.”
“Then the next.”
She looked at Daniel.
“The timing drift exposed it.”
“It didn’t create it.”
Arthur stared at the lines.
Then whispered:
“Positive feedback inside the optimizer.”
Maya nodded.
“Exactly.”
Daniel said nothing.
Six months.
Three countries.
Millions of dollars.
A waitress had been inside the room for less than an hour.
But Daniel was not stupid enough to believe that meant she was magically smarter than everyone present.






