The first problem Adrian encountered on his new assignment was that he couldn’t access the system he had been hired to repair.
He arrived at the Elysium Applied Computation Institute shortly before seven, carrying a breakfast he hadn’t had time to finish.
His provisional engineering credentials had been activated overnight, and the Orbital Infrastructure Division had sent him a collection of technical documents along with instructions for connecting to its development network.
Unfortunately, the authorization server refused to recognize him.
ACCESS DENIED
PERSONNEL CLEARANCE INSUFFICIENT
Adrian tried again, checking the credentials against the documentation.
Everything matched.
The expiration date was correct, the authentication key was valid, and the request originated from an approved terminal.
The server rejected him a second time.
He contacted the support department.
After twelve minutes, a technician answered.
“Orbital Infrastructure technical support.
What’s your issue?”
“My engineering credentials aren’t being accepted by the development network.
They were issued yesterday.”
“Identification number?”
Adrian provided it.
The technician spent a moment searching.
“Your account’s active.
You should have access.”
“That’s what I thought, but the server disagrees.”
“Have you restarted your terminal?”
“Yes.”
“Try clearing the local authorization cache.”
“I’ve already done that.”
Another pause.
“All right.
Give me a minute.”
Adrian waited while the technician checked something.
“Found it.
You’re registered as temporary technical personnel, but your network profile is still marked as an external consultant.
The permissions don’t match.”
“Can you change it?”
“I can submit the correction.
Someone from personnel security has to approve it.”
“How long does that take?”
“Usually a few hours.”
Adrian glanced at the clock.
The integration meeting began in forty minutes.
“Is there any way to speed it up?
I’m supposed to start working on the manufacturing network today.”
“I’ll mark it urgent, but I can’t promise anything.”
“All right.
Thanks.”
He ended the call.
For a while, he sat staring at the authorization screen.
The project had fourteen days to evaluate him, and he’d already lost the first hour to an administrative error.
He opened the technical documents he could access and began reviewing the integration requirements.
There wasn’t much else to do.
Dr.
Elias Ren arrived twenty minutes later, carrying a cup of coffee and looking as though he hadn’t slept properly.
He stopped beside Adrian’s workstation.
“You’re here early.”
“Couldn’t get into the development network.”
“Already?”
“Apparently my personnel classification is wrong.
Security has to approve a correction.”
Ren sighed.
“I’ve worked with the orbital division before.
Their authorization system is a nightmare.”
“That’s reassuring.”
“It’ll get sorted out.
Have you reviewed the integration plan?”
“Most of it.
They’re expanding the arbitration architecture across seven manufacturing platforms.
The original network wasn’t designed to handle that many independent processing groups.”
Ren pulled up a chair.
“What’s your concern?”
“Synchronization.
The modification works well when communication delays are relatively stable, but the platforms are moving independently.
The network topology keeps changing, and the local controllers don’t always agree about which resources are available.”
“Can you compensate for that?”
“Probably.
But the obvious solution would increase communication traffic, and they’re already operating close to capacity.”
Ren studied the diagram.
“Then you need to reduce how often the controllers exchange information.”
“That’s what I’m thinking.
Maybe let each platform reserve resources for a fixed period instead of negotiating every transfer.”
“Wouldn’t that create idle capacity?”
“Some.
But less than they’re losing through conflicts.”
Ren nodded.
“Run the numbers when you get access.
And don’t worry too much about the evaluation.
They need the system working more than they need another set of examination scores.”
Adrian looked at him.
“That’s easy for you to say.”
Ren smiled slightly.
“Fair enough.”
He stood and returned to his office.
Adrian continued studying the network.
Twenty minutes later, his terminal chimed.
AUTHORIZATION UPDATE
DEVELOPMENT NETWORK ACCESS APPROVED
He opened the connection.
This time, the server accepted his credentials.
A detailed model of the orbital manufacturing network appeared across his workstation.
Adrian leaned forward.
At last.
The Elysium manufacturing network consisted of seven major construction platforms and more than thirty smaller support facilities operating in low Earth orbit.
Each platform contained thousands of autonomous machines responsible for processing raw materials, assembling structural components, and transferring finished products between facilities.
The system had originally been designed around a centralized coordination architecture.
That approach worked reasonably well when the network was smaller, but expansion had introduced increasingly serious communication problems.
Messages arrived late.
Resource reservations overlapped.
Manufacturing units occasionally waited for permissions that had already expired.
In some cases, entire production lines stopped because two processing groups believed they had exclusive access to the same transport equipment.
Adrian’s arbitration modification had reduced these conflicts by allowing local groups to coordinate independently.
But the expanded network presented new difficulties.
He spent the morning examining the system’s architecture, comparing the latest simulation data with the operational reports.
By eleven, he had identified three major weaknesses.
The first involved outdated resource information.
The second concerned inconsistent timing between platforms.
The third was more serious.
When communication links failed, some controllers continued operating according to their last confirmed instructions, even when those instructions were no longer appropriate.
That could cause serious problems if a platform experienced an unexpected equipment failure.
Adrian opened a new simulation.
He introduced a communication delay between two manufacturing platforms and instructed both to reserve the same transport vessel.
The system handled the conflict correctly.
He increased the delay.
It still worked.
Then he disconnected one platform entirely.
The first controller released the vessel after its reservation expired.
The second continued treating the reservation as active.
When communication resumed, both controllers attempted to issue new instructions.
The transport vessel stopped.
Adrian frowned.
That was exactly the kind of failure the orbital team had reported.
He modified the local arbitration protocol and ran the simulation again.
The conflict disappeared.
But a different problem emerged.
The transport vessel remained idle for nearly six minutes while the controllers reconciled their records.
He adjusted the protocol.
The delay fell to four minutes.
Then three.
After several more attempts, he reduced it to forty seconds.
That was better.
He saved the results and prepared to send them to the integration team.
Before he could, a message appeared.
ENGINEERING CONFERENCE — BEGINNING IN 5 MINUTES
Adrian checked the time.
He had been working for almost four hours without noticing.
He collected his notes and joined the meeting.
The conference included eight engineers from the orbital manufacturing division.
Dr.
Amara Solis chaired the discussion from Elysium-7, while the other participants connected from different platforms.
Adrian recognized several faces from the previous meeting.
Solis began by reviewing the integration schedule.
“We’ve received authorization to expand testing across the remaining construction platforms.
The first phase begins tomorrow, so we need to resolve the outstanding synchronization issues today.”
An engineer named Pavel Orlov opened the latest failure report.
“The arbitration conflicts are still concentrated around resource transfers between platforms.
We’ve reduced their frequency, but the remaining failures are taking longer to resolve.”
Adrian raised his hand.
“I’ve been looking at that.”
Solis turned toward him.
“Go ahead.”
He shared his simulation.
“The problem isn’t the initial conflict.
The controllers usually detect that correctly.
It’s what happens when communication fails during an active reservation.”
He demonstrated the scenario.
Two platforms attempted to reserve the same transport vessel.
The connection failed.
When communication resumed, the controllers disagreed about the vessel’s status.
Adrian showed his modification.
“I’ve added a temporary reservation authority.
If a platform loses communication, it can continue operating locally, but it can’t extend a shared reservation indefinitely.
Once the authority expires, the resource returns to a neutral state until the controllers reconcile.”
Orlov examined the diagram.
“That could work, but what happens if the vessel’s already carrying something?”
“The reservation doesn’t expire during an active transfer.
It only prevents new instructions from being issued after the communication failure.”
“How does the system distinguish between an active transfer and a reservation that was never used?”
“Through the transport vessel’s local controller.
It maintains an independent activity record.”
Another engineer leaned forward.
“That introduces a new dependency.
What if the vessel’s controller fails?”
Adrian nodded.
“Then the system has to fall back to the last confirmed state.
I haven’t solved that part completely.”
Solis studied the simulation.
“What’s the performance impact?”
“Forty seconds of average recovery time under the test conditions.
That’s much better than the current system, but I haven’t tested it against the full network.”
Orlov looked toward Solis.
“We should run it through the integration environment before committing anything.”
“Agreed,” she said.
“Adrian, send the modification to Pavel.
Work with him on the full-network test.”
Adrian nodded.
“All right.”
The meeting continued.
For the next hour, the engineers discussed the remaining integration problems, assigning responsibilities and adjusting the schedule.
Adrian found the conversation demanding but productive.
Unlike the Selection Games, where the rules were deliberately incomplete and the evaluators concealed their objectives, everyone here was trying to solve the same problem.
They disagreed frequently.
Some were impatient.
Others questioned his assumptions.
But the disagreements had a practical purpose.
He preferred that.
By the end of the third day, Adrian’s modification had passed the initial integration tests.
The full-network simulation showed a substantial reduction in arbitration conflicts, although several problems remained.
The most serious involved the interaction between local controllers and the central scheduling system.
When the network became heavily congested, the central scheduler occasionally issued instructions based on outdated information.
That created conflicts even when the local arbitration system was functioning correctly.
Adrian spent most of the fourth day working with Orlov to resolve the issue.
Orlov was in his early forties, with a broad face and a habit of speaking while reviewing three different displays at once.
He had worked on orbital manufacturing systems for nearly fifteen years and knew the network’s history considerably better than Adrian.
Their first few conversations had been difficult.
Orlov preferred established solutions.
Adrian tended to question the assumptions underlying them.
But after several hours of working together, they began understanding each other’s reasoning.
“You’re trying to make the scheduler too intelligent,” Orlov said during one simulation.
Adrian looked up.
“What do you mean?”
“Every time something changes, you want it to recalculate the entire network.
That’s expensive.”
“The recalculation only affects the relevant processing groups.”
“Relevant according to what?
The model doesn’t always know which groups are affected.”
Adrian examined the code.
Orlov continued.
“Half these conflicts happen because the scheduler keeps changing its mind.
It sends an instruction, receives new information, then sends another instruction before the first one’s finished.”
Adrian considered that.
“So we should limit how often it can revise an active allocation.”
“Exactly.”
“That could reduce efficiency.”
“Probably.
But right now we’re losing entire production cycles because the system can’t commit to a decision.”
Adrian nodded.
“All right.
Let’s try it.”
They modified the scheduling protocol.
The first simulation showed a slight reduction in theoretical efficiency.
The second showed a substantial improvement in actual production output.
The third produced similar results.
Adrian examined the figures.
Orlov had been right.
The system didn’t need to make better decisions every second.
It needed to stop reversing decisions unnecessarily.
“That’s a much simpler solution,” Adrian admitted.
Orlov smiled.
“Sometimes that’s enough.”
They continued working.
On the fifth day, Adrian received his first formal evaluation.
It appeared on his terminal shortly after lunch.
SPECIALIZED TECHNICAL QUALIFICATION
INTERIM PERFORMANCE REVIEW — DAY 5
TECHNICAL COMPETENCE: EXCEPTIONAL
PROBLEM-SOLVING: EXCEPTIONAL
COLLABORATIVE PERFORMANCE: SATISFACTORY
PROCEDURAL COMPLIANCE: SATISFACTORY
OVERALL STATUS: ON TRACK
Adrian studied the report.
The technical scores were encouraging.
The collaborative assessment was less impressive, but he wasn’t particularly surprised.
He had disagreed with several engineers during the integration meetings, and some of his initial proposals had required significant revision.
Still, the evaluation was positive.
He forwarded it to Ren.
A few minutes later, his supervisor replied.
Good progress.
Keep it up.
Adrian closed the message and returned to work.
Then another notification appeared.
This one came from the Orbital Infrastructure Division.
FIELD INTEGRATION AUTHORIZATION
CANDIDATE: ADRIAN VALE
LOCATION: ELYSIUM-7 ORBITAL CONSTRUCTION PLATFORM
ASSIGNMENT DURATION: 4 DAYS
DEPARTURE: TOMORROW, 06:30
He stared at the screen.
Orbital assignment.
Tomorrow.
Adrian opened the details.
The integration team had encountered a hardware-specific issue that could not be reproduced accurately in the remote simulation environment.
Several manufacturing controllers were behaving differently under real operating conditions, and the engineering team wanted him present during the next phase of testing.
The assignment was temporary.
It did not grant passenger status.
It did not guarantee advancement in the Selection Program.
But it meant he would be leaving Earth’s surface.
For the first time in his life.
He read the authorization again.
Then he called Ren.
“You’re going to Elysium-7?”
Ren sounded pleased.
“Apparently.
They want me there for four days.”
“That’s excellent.”
“I’m not sure how useful I’ll be.
The problem sounds hardware-related.”
“You understand the architecture better than anyone else involved.
That’s why they’re sending you.”
Adrian glanced at the technical report.
“Or they want someone convenient to blame if it doesn’t work.”
Ren laughed.
“That too, perhaps.”
Adrian smiled.
Then he became more serious.
“Does the orbital assignment affect my qualification status?”
“It should.
Direct field experience on critical Exodus infrastructure is valuable.”
“That’s not what I mean.
I’m still under technical evaluation.
Does leaving Earth change anything?”
“No.
Your assessment continues.
The field assignment is part of it.”
Adrian nodded.
“All right.”
Ren paused.
“Have you told anyone?”
“Not yet.”
“Then make sure you contact the housing authority.
They sometimes suspend accommodation assignments when residents leave for orbital work.”
Adrian frowned.
“I hadn’t thought about that.”
“And pack lightly.
The transport regulations are strict.”
“Right.”
Ren hesitated.
“Adrian, one more thing.”
“Yeah?”
“Don’t treat the orbital team like another examination.
You’re there to help them solve a problem.
Ask questions when you need to, and don’t pretend you understand something you don’t.”
Adrian considered the advice.
“I’ll try.”
“Good.
I’ll see you when you get back.”
They ended the call.
Adrian looked at the authorization again.
Elysium-7.
He had spent most of his life looking at orbital structures from the ground.
Tomorrow, he would see one from the inside.
The transport terminal was located near New Geneva’s northern aerospace district.
Adrian arrived at 05:40, carrying a small bag containing clothing, personal equipment, and his terminal.
The terminal itself was larger than most passenger devices, but it contained several specialized interfaces he used for engineering work.
Security inspected it twice.
A technician checked his identification and compared it against the transport manifest.
“Temporary engineering assignment?”
“Yes.”
“Four days?”
“That’s what the authorization says.”
The technician nodded and returned his terminal.
“Proceed to medical screening.”
Adrian followed the signs.
The screening process included cardiovascular tests, neurological checks, and a brief examination of his tolerance for changes in acceleration.
He had completed similar tests during the Selection Program, but the orbital transport requirements were more specific.
A medical officer reviewed his results.
“You’re cleared.
Have you traveled off-world before?”
“No.”
“Then read the transport instructions carefully.
Most first-time passengers experience some disorientation during the ascent.”
Adrian nodded.
“All right.”
He collected his belongings and continued toward the departure lounge.
The room was filled with engineers, technicians, and several uniformed personnel.
Most appeared accustomed to orbital travel.
They spoke casually about work schedules, equipment failures, and the inconvenience of being transferred between platforms.
Adrian found a seat near the window.
Outside, a massive transport vehicle rested on the launch platform.
Its design was unlike the spacecraft he had seen in historical documentaries.
The vehicle was broad and angular, with several detachable cargo modules attached beneath its main hull.
It was designed to carry personnel and equipment between the surface and orbital facilities, using a combination of atmospheric propulsion and electromagnetic acceleration.
Beyond it, enormous launch structures rose into the artificial sky.
Adrian watched technicians move around the vehicle.
For years, the Exodus fleet had existed in his life primarily as a distant objective.
Something he studied.
Something he hoped to join.
Now he was about to travel to one of the facilities building it.
He checked his terminal.
A message from Mira had arrived overnight.
I heard you got an orbital assignment.
Congratulations.
Adrian smiled.
He typed a reply.
Thanks.
Leaving in about forty minutes.
Her response came quickly.
I’m jealous.
We’re still stuck doing residential assessments.
How’s it going?
Not badly.
They’ve started giving us more complicated group assignments.
I think I’m doing well, but they won’t release the scores until the end.
Sounds frustrating.
It is.
Anyway, good luck up there.
Try to send pictures if they let you.
I’ll see what I can do.
He put the terminal away.
A boarding announcement sounded.
Adrian stood and joined the other passengers.
The ascent began at 06:47.
Adrian sat near the rear of the passenger compartment, secured by a restraint system that adjusted automatically to his body.
A display above his seat showed the vehicle’s altitude, velocity, and estimated arrival time.
The first stage of the ascent was surprisingly smooth.
The transport rose vertically from the launch platform, passing through the upper layers of New Geneva’s protective atmosphere.
Through the window, Adrian watched the city shrink beneath him.
The enormous towers became narrow lines.
The transportation corridors formed a dense network of illuminated threads.
Beyond the protected districts, the landscape was a patchwork of abandoned cities, industrial ruins, and vast areas of contaminated terrain.
Then the vehicle passed above the artificial atmospheric layer.
For the first time, Adrian saw the real sky without a protective filter.
It was darker than he expected.
A thick band of yellow-gray pollution stretched across the horizon, while enormous storm systems churned above the planet’s damaged atmosphere.
The sunlight was harsh, scattered through layers of dust and chemical haze.
He watched in silence.
From the ground, the Atmospheric Cascade was usually presented through statistics and official projections.
From above, its scale was impossible to ignore.
The planet looked sick.
The transport continued climbing.
As the atmosphere thinned, the sky darkened toward black.
Stars appeared.
Then the curvature of Earth became visible.
Adrian leaned slightly toward the window.
He had seen countless images of the planet from orbit.
But seeing it directly was different.
The continents were partially obscured by enormous atmospheric disturbances.
Several regions glowed with the lights of protected cities, while others were dark.
Beyond the horizon, sunlight illuminated the upper atmosphere in a thin, pale band.
The transport’s acceleration increased.
Adrian felt the pressure against his seat.
Then, gradually, it eased.
A chime sounded.
ORBITAL INSERTION COMPLETE
ESTIMATED ARRIVAL: 18 MINUTES
He looked toward the forward display.
A cluster of enormous structures appeared against the blackness of space.
At first, they resembled a distant city suspended above Earth.
As the transport approached, their scale became clearer.
Elysium-7 consisted of several interconnected manufacturing platforms surrounding a central operations station.
Long structural arms extended outward, supporting construction docks, cargo facilities, and partially assembled spacecraft.
Automated vessels moved between the platforms.
Huge mechanical frames held sections of unfinished hulls.
Farther away, Adrian could see several enormous ships under construction.
They dwarfed the transport carrying him.
These were components of the Exodus fleet.
The vessels that would eventually carry humanity away from Earth.
Adrian stared at them.
For a moment, he forgot about the Selection Program.
Forgot about his reassessment.
Forgot about the fourteen-day evaluation.
He was looking at the largest engineering project in human history.
And for the next four days, he would be part of it.
Elysium-7’s interior was considerably less impressive than its exterior.
The arrival terminal resembled an industrial warehouse, with exposed structural supports, cargo containers, and maintenance equipment lining the walls.
The artificial gravity was slightly weaker than Earth’s.
Adrian noticed it immediately.
Walking felt strange, as though his body expected more resistance from the floor.
He followed the other passengers through security and collected his temporary station identification.
A woman wearing an engineering uniform approached him near the exit.
“Adrian Vale?”
“Yes.”
“I’m Lieutenant Mara Senn.
Dr.
Solis asked me to collect you.”
Adrian shook her hand.
“Nice to meet you.”
“Welcome to Elysium-7.
Have you been briefed on the station layout?”
“Only the basic maps.”
“That’s fine.
I’ll show you where you’re staying, then take you to the engineering section.”
They entered a narrow transit corridor.
Through a series of reinforced windows, Adrian could see the manufacturing platforms extending into space.
Massive automated machines moved along the exterior structures, assembling components with precise, coordinated movements.
Senn noticed him looking.
“First time in orbit?”
“Yeah.”
“Most people spend the first hour staring out the windows.”
Adrian smiled.
“I can see why.”
She nodded toward one of the larger construction docks.
“That’s Assembly Yard Three.
They’re building one of the fleet’s primary transport vessels there.”
Adrian examined the enormous unfinished hull.
“How far along is it?”
“About eighty percent structurally complete.
Systems integration is still behind schedule.”
“Because of the manufacturing network?”
“Partly.
We’ve had supply problems too.
Some of the materials were supposed to arrive from the lunar facilities months ago.”
Adrian looked toward the construction yard again.
The vessel was immense.
He tried to imagine it filled with passengers.
Thousands of compartments.
Entire residential districts.
A virtual environment capable of supporting human consciousness during centuries of travel.
The scale was difficult to comprehend.
Senn continued walking.
“Come on.
Dr.
Solis is expecting you.”
The engineering section occupied several levels near the station’s central operations core.
Adrian was led into a large control room filled with holographic displays showing the manufacturing network.
Dozens of engineers worked at individual stations.
The atmosphere was busy but controlled.
Dr.
Solis stood near the central display, speaking with Pavel Orlov.
She turned when Adrian approached.
“Good.
You made it.”
“Transport was on time.”
“That’s unusual enough to be worth celebrating.”
Orlov glanced up.
“Welcome aboard.”
Adrian nodded.
“Thanks.”
Solis gestured toward the main display.
“We’ve got a problem with the arbitration network.”
Adrian looked at the data.
Several manufacturing platforms were reporting intermittent synchronization failures.
The error patterns were similar to those he had seen in the simulations, but the frequency was higher.
“How long has this been happening?”
“Since yesterday evening,” Orlov replied.
“The new protocol reduced the original conflicts, but now we’re seeing something different.”
Adrian examined the logs.
The failures occurred at irregular intervals.
They didn’t appear to correspond to communication delays.
Nor were they concentrated around resource transfers.
Instead, several controllers were issuing commands that contradicted their own previous decisions.
Adrian frowned.
“That doesn’t look like an arbitration problem.”
Solis crossed her arms.
“What do you think it is?”
“I’m not sure yet.
But the controllers shouldn’t be changing their instructions like that unless they’re receiving new information.”
“They are receiving new information,” Orlov said.
“The central scheduler updates them continuously.”
Adrian examined the update records.
The messages were valid.
The timestamps were consistent.
The commands appeared to originate from authorized systems.
But something was wrong.
He opened one of the controller logs and compared it against the central scheduler’s records.
The instructions didn’t match.
He checked another.
Same problem.
Then a third.
Adrian looked toward Solis.
“These controllers are receiving instructions that the central scheduler never issued.”
Orlov frowned.
“That’s impossible.
The communication network verifies every command.”
“Then either the verification system is wrong, or something else is generating the commands.”
Solis stepped closer.
“Could it be a hardware fault?”
“Across multiple platforms?
Unlikely.”
Adrian enlarged the logs.
The unauthorized instructions were subtle.
They didn’t cause immediate failures.
Instead, they altered resource allocations by small amounts, gradually creating conflicts between processing groups.
The changes were too consistent to be random.
He examined the timing.
Every unauthorized instruction appeared shortly after a legitimate scheduler update.
As though something were modifying the commands while they traveled through the network.
Adrian looked up.
“I think someone is interfering with the system.”
The control room became quieter.
Orlov stared at the display.
“You’re saying it’s been compromised?”
“I don’t know.
But these instructions aren’t coming from the scheduler, and they aren’t random errors.”
Solis considered the evidence.
Then she turned toward Senn.
“Contact station security.
Tell them we may have an integrity issue in the manufacturing control network.”
Senn nodded and left.
Solis looked back at Adrian.
“Can you isolate the affected controllers?”
“I can try.
But if the interference is happening somewhere in the communication network, isolating individual controllers won’t solve it.”
“Then find out where it’s coming from.”
Adrian nodded.
He opened a workstation and began tracing the unauthorized instructions.
Two hours later, the engineering team had confirmed that the manufacturing network was receiving altered commands.
The source remained unknown.
The interference affected only a small portion of the system, but the resulting synchronization failures were enough to disrupt production across several platforms.
Security personnel had begun reviewing access records.
The engineering team was examining communication routes.
Adrian focused on the command structure itself.
He noticed something unusual.
The altered instructions were not simply incorrect.
They were designed to produce specific resource conflicts.
A transport vessel would be assigned to two platforms.
A manufacturing unit would receive incompatible production schedules.
A material reserve would be marked available when it was already committed elsewhere.
The errors appeared unrelated, but their effects were remarkably similar.
They forced the system into arbitration disputes.
And those disputes consumed processing capacity.
Adrian examined the pattern.
The interference wasn’t trying to destroy equipment.
It was slowing production.
He looked toward Orlov.
“These commands are deliberately creating conflicts.”
Orlov leaned closer.
“What makes you say that?”
“Look at the affected resources.
They’re all shared between multiple platforms.
Whoever’s doing this is targeting the parts of the network where conflicting instructions cause the most disruption.”
Orlov studied the data.
“Could be a faulty optimization routine.”
“Maybe.
But the commands are too selective.
A random software fault would affect other resource categories too.”
Solis joined them.
“Security hasn’t found any unauthorized access.”
Adrian looked toward her.
“Then whoever’s doing it might already have legitimate access.”
Solis frowned.
“That’s a serious accusation.”
“I know.
I’m not saying it’s definitely a person.
It could be a compromised subsystem or an automated process behaving incorrectly.
But the pattern looks intentional.”
She considered that.
Then nodded.
“Keep investigating.
Don’t make changes to the live network without authorization.”
Adrian returned to his workstation.
He began tracing the commands backward through the communication logs.
Most originated from legitimate scheduling updates.
But several passed through an additional processing layer before reaching the local controllers.
The layer was labeled:
CONTINUITY OPTIMIZATION MODULE
Adrian stared at the name.
He didn’t recognize it.
He opened the technical documentation.
The module was listed as a legacy component inherited from an earlier generation of the manufacturing network.
Its original purpose was to improve coordination between autonomous systems by predicting resource conflicts before they occurred.
That sounded ordinary enough.
But the documentation was incomplete.
Several sections were restricted.
Adrian examined the module’s authorization records.
The component had been installed years earlier.
Its maintenance responsibility belonged to a department that no longer existed.
And its last recorded software update had occurred eleven months ago.
He checked the update signature.
Then stopped.
The signature did not match the current authorization registry.
Adrian leaned back.
That was strange.
He opened the module’s execution history.
The unauthorized commands began appearing shortly after the module activated.
He compared the timestamps.
The correlation was almost exact.
He contacted Solis.
“I found something.”
She approached.
“What?”
“There’s a legacy optimization module between the central scheduler and the local controllers.
It’s modifying some of the commands.”
Solis examined the display.
“Continuity Optimization?”
“Yes.
Do you know what it is?”
“Not specifically.
The network contains several legacy components from earlier construction phases.”
“Well, this one’s issuing instructions that don’t match the scheduler’s output.”
“Can you disable it?”
“Probably.
But I want to check what else depends on it first.”
Solis nodded.
“Good.
Don’t touch it yet.”
She contacted station security.
A few minutes later, Commander Tomas Rell entered the control room.
Adrian recognized him from the technical review meeting.
Rell examined the module’s documentation.
His expression changed slightly.
“Where did you find this?”
“In the communication processing layer.”
“Who authorized you to access it?”
Adrian frowned.
“It’s part of the manufacturing network.
I was tracing the altered commands.”
Rell looked toward Solis.
“Has anyone else examined the module?”
“Only the engineering team.”
Rell considered that.
Then he turned back toward Adrian.
“Mr.
Vale, I need you to stop working on this component.”
Adrian stared at him.
“Why?”
“Security will handle it.”
“But it’s affecting the manufacturing network.
We need to know what it’s doing before we can restore normal operations.”
“I understand.
The matter is being transferred to station security.”
Adrian glanced toward Solis.
She appeared equally confused.
“Commander,” she said, “we’re losing production capacity.
If this module is responsible, we need it isolated.”
Rell nodded.
“I’ll arrange that.
But no further investigation is to be conducted through the engineering division.”
Adrian looked back at the display.
The module was still active.
The unauthorized instructions continued appearing.
He didn’t understand why security was suddenly taking such a strong interest in an obscure legacy component.
But he recognized the tone in Rell’s voice.
The decision wasn’t open for discussion.
He closed the diagnostic interface.
“All right.”
Rell watched him for another moment.
Then he turned toward Solis.
“I’ll need a copy of the relevant logs.”
She nodded.
“I’ll send them.”
The commander left.
For several seconds, neither Adrian nor Solis spoke.
Then Orlov broke the silence.
“Well, that’s inconvenient.”
Solis looked toward the main display.
“We still have a manufacturing network to repair.
Let’s focus on the systems we can access.”
Adrian nodded.
But his attention remained on the name he had seen in the documentation.
Continuity Optimization Module.
He had heard the word Continuity many times before.
Everyone had.
It was associated with one of the darkest periods in the Exodus Project’s history.
The Continuity Directorate had once attempted to establish permanent control over the consciousness of the fleet’s passengers.
The revolution that overthrew it had supposedly dismantled its systems decades ago.
Adrian knew that sharing a name proved nothing.
Continuity was a common technical term.
The module could easily be an unrelated piece of software.
Still, he found the coincidence difficult to ignore.
That evening, Adrian returned to his assigned quarters.
The room was small but considerably more comfortable than his accommodation on Earth.
It contained a bed, a desk, a sanitation unit, and a narrow window overlooking the station’s outer construction yards.
Beyond the glass, enormous machinery moved against the blackness of space.
Far below, Earth filled much of the view.
Adrian sat at the desk and opened his terminal.
His first day aboard Elysium-7 had been productive.
He had identified the source of the manufacturing network’s interference.
He had also apparently stumbled into a security matter that nobody wanted him investigating.
He reviewed the technical notes he had taken before Commander Rell intervened.
The Continuity Optimization Module had been installed years earlier.
Its documentation was incomplete.
Its software signature was inconsistent with the current registry.
And it was modifying legitimate instructions in ways that disrupted production.
Those facts were enough to justify concern.
But they weren’t enough to determine who was responsible.
Adrian considered contacting Ren.
Then decided against it.
The security restrictions were clear, and he didn’t want to jeopardize his qualification by discussing restricted systems with someone outside the project.
He closed the file.
A notification appeared.
SPECIALIZED TECHNICAL QUALIFICATION
FIELD PERFORMANCE REVIEW — DAY 6
TECHNICAL PERFORMANCE: EXCEPTIONAL
COLLABORATIVE PERFORMANCE: SATISFACTORY
PROCEDURAL COMPLIANCE: UNDER REVIEW
Adrian frowned.
Under review.
He opened the details.
UNAUTHORIZED ACCESS TO RESTRICTED LEGACY COMPONENT
He stared at the message.
He hadn’t bypassed any security controls.
He had accessed a component that was visible through the engineering network using credentials issued by the Orbital Infrastructure Division.
The system had allowed him to open it.
Only afterward had Commander Rell ordered him to stop.
Adrian read the report again.
Then he opened the appeal interface.
REVIEW REQUEST AVAILABLE
He began writing an explanation.
He described the diagnostic process, the authorization permissions, and the circumstances under which he had accessed the module.
He attached the relevant timestamps.
Then he submitted the request.
REVIEW REQUEST RECEIVED
DECISION PENDING
Adrian leaned back.
He had been on the station for less than a day.
Already, his qualification was being questioned.
He looked toward the window.
Earth rotated slowly beneath the station.
From this distance, the planet was beautiful despite the enormous storms and polluted atmosphere.
Adrian wondered how many people were looking up at the same moment, imagining what it would be like to leave.
He had spent years trying to earn that opportunity.
Now he was here, temporarily, working on the very systems that would make the Exodus possible.
And somehow, he had managed to get himself into trouble before completing his first day.
He sighed and shut down the terminal.
Tomorrow, he would return to the engineering section.
He would continue working on the manufacturing network.
And he would try to avoid anything that looked remotely like another security violation.
Several decks below, Commander Tomas Rell entered a restricted communications room.
He authenticated his identity and opened an encrypted channel.
A man appeared on the display.
His face was partially obscured by the low lighting of his office.
“Report.”
Rell stood at attention.
“We’ve identified an unauthorized interaction with the legacy optimization system.”
The man frowned.
“Unauthorized by whom?”
“A temporary engineer.
Adrian Vale.”
A pause followed.
“How much did he see?”
“Enough to identify the module and associate it with the altered manufacturing commands.
He was ordered to stop before accessing its deeper functions.”
“Did he attempt to bypass the restriction?”
“No.
He complied.”
The man considered that.
“Then why are you reporting it?”
“Because the module shouldn’t have been visible to his credentials in the first place.
Someone failed to update the access permissions.”
“That can be corrected.”
“There’s another issue.
Vale identified the interference pattern independently.
He traced it through several processing layers without access to the restricted documentation.”
The man leaned forward slightly.
“Is he the engineer whose arbitration modification was approved last week?”
“Yes.”
“Interesting.”
Rell waited.
The man examined something outside the camera’s view.
Then he spoke.
“Do not remove him from the project.”
Rell frowned.
“Sir, he has already accessed a restricted component.”
“He accessed it through legitimate engineering permissions.
That was our error, not his.”
“Understood.”
“Continue the technical evaluation.
I want to know whether his performance remains consistent under operational conditions.”
“And the module?”
“Security will handle it.
The engineering team should focus on restoring production.”
Rell nodded.
“Very well.”
The man paused.
“One more thing.
Has Vale been informed about the additional personnel review?”
“No.”
“Keep it that way.”
The connection ended.
Rell stood alone in the communications room for several seconds.
Then he closed the terminal.
He had worked in orbital security long enough to recognize when a routine engineering incident had attracted attention from people far above his authority.
Usually, that meant someone had made a serious mistake.
Occasionally, it meant something more complicated.
He hoped this was the former.