Adrian woke at 05:40 to a notification informing him that his access to the manufacturing network had been temporarily restricted.
He lay in bed for a moment, reading the message through the dim light of his terminal.
The restriction covered all legacy control systems, several diagnostic tools, and portions of the central scheduling network.
His authorization for ordinary engineering work remained active, but nearly half the interfaces he had used the previous day were now unavailable.
A second notification concerned his qualification assessment.
PROCEDURAL COMPLIANCE REVIEW: PENDING
FIELD ASSIGNMENT: CONTINUES AS SCHEDULED
At least he hadn’t been removed from the project.
Adrian got out of bed and went to wash his face.
The station’s artificial gravity was slightly weaker than Earth’s, and he still hadn’t adjusted to the sensation.
Every movement felt a little too easy, particularly when he turned quickly or reached for something.
His assigned quarters were comfortable enough, although the ventilation produced a constant low-frequency hum.
Through the narrow window, Earth occupied most of the view, its enormous cloud systems illuminated by the approaching sunrise.
He watched for a few seconds before turning away.
The previous day’s events had left him with more questions than answers.
He had discovered a component that appeared to be modifying legitimate manufacturing instructions.
Security had intervened almost immediately, and his evaluation had been affected despite his having used authorized engineering credentials.
It was possible that the situation was simply an administrative mistake.
Large systems often contained poorly documented legacy components, and security departments tended to be cautious when unfamiliar personnel accessed them.
Still, the speed of the response bothered him.
He had reported a problem affecting production.
Rather than asking him to explain what he had found, Commander Rell had ordered him to stop investigating.
Adrian understood the need for security restrictions.
What he didn’t understand was why a manufacturing optimization module required that level of protection.
He finished dressing and headed toward the engineering section.
The station was already busy.
Automated cargo vehicles moved through the main transit corridors, carrying equipment between storage facilities and construction docks.
Maintenance workers were replacing damaged wall panels near one of the freight elevators, while a group of technicians argued over the delivery schedule for a shipment of specialized processors.
Adrian stopped at a food dispenser and purchased a breakfast package.
It contained two pieces of synthetic bread, a protein filling, and a small container of fruit substitute.
The food was considerably better than the standard rations available in New Geneva, although the price was nearly three times higher.
He ate while walking.
At the engineering section, Pavel Orlov was sitting at his workstation with a cup of coffee and three open displays.
He looked up when Adrian approached.
“Morning.
Heard you got locked out of half the network.”
“That obvious?”
“Security sent us a notice.
Apparently, you’re not supposed to access legacy components anymore.”
Adrian sat down.
“Did they say anything about the interference?”
“No.
They took copies of the logs and told us to continue with the integration.”
“Has the problem stopped?”
Orlov shook his head.
“Not entirely.
The affected controllers are still receiving inconsistent instructions, but the frequency dropped overnight.”
Adrian opened the available diagnostic tools.
The latest reports showed that the manufacturing network had recovered some of its lost capacity.
Several of the affected processing groups were operating normally again.
But the underlying problem hadn’t disappeared.
“Did security disable the module?” Adrian asked.
“Couldn’t tell you.
They’ve restricted the relevant logs.”
“That’s inconvenient.”
“Welcome to orbital engineering.”
Orlov took another sip of coffee.
“Look, I know you’re worried about your evaluation.
Solis has already contacted the Selection Directorate.
She doesn’t think you violated anything.”
Adrian glanced toward him.
“She told you that?”
“She mentioned it yesterday.
Said you were doing your job and security should’ve configured the permissions properly.”
“That’s good to hear.”
“Don’t get too comfortable.
We’ve still got three platforms that can’t agree on resource allocations.”
Adrian opened the latest reports.
“All right.
Show me what’s happening.”
The morning passed in a series of technical discussions and simulation tests.
Without access to the restricted processing layer, Adrian couldn’t investigate the altered commands directly.
Instead, he focused on making the arbitration network more resilient to inconsistent information.
The problem was difficult because the system needed to distinguish between genuine changes in resource availability and instructions that had become outdated or corrupted.
A manufacturing controller might receive an order to transfer a shipment of structural components to another platform.
Under normal conditions, it would verify the request and begin the transfer.
But if the central scheduler later issued a contradictory instruction, the controller had to decide which command to follow.
Adrian proposed a verification mechanism requiring major resource transfers to be confirmed by both the originating platform and the receiving platform.
Orlov disliked the idea immediately.
“That’ll double the confirmation traffic.”
“Only for transfers above a certain threshold.”
“Those are the transfers that already cause most of our congestion.”
“Then we can reduce the verification frequency for smaller transactions.”
Orlov examined the proposal.
“You’re treating the communication network as if bandwidth is free.”
“I’m not.
I’m trying to prevent a single incorrect instruction from disrupting three production lines.”
“Then put the verification at the scheduling level, not the transport level.”
Adrian considered that.
“If the scheduler’s the source of the incorrect instruction, that won’t help.”
“True.
But if we verify every transfer independently, we’ll create a bottleneck even when the network’s functioning normally.”
They spent another twenty minutes comparing the two approaches.
Eventually, Adrian suggested a compromise.
The system would verify high-impact resource transfers independently, while allowing smaller transactions to proceed under the existing protocol.
The threshold would change dynamically according to network conditions.
Orlov ran the first simulation.
The results were disappointing.
Production efficiency fell by nearly six percent.
Adrian examined the traffic logs.
“The verification requests are arriving in bursts.
We need to spread them out.”
“Can you do that without delaying the transfers?”
“Maybe.
Let the receiving platform issue a confirmation before the transfer’s scheduled to begin.”
Orlov adjusted the model.
The next simulation performed better.
The third improved further.
By midday, they had reduced the additional communication overhead to less than one percent.
Orlov leaned back.
“That’s workable.”
Adrian nodded.
“It still doesn’t solve the source of the problem.”
“No.
But if it keeps the network running until security sorts things out, I’ll take it.”
They sent the modification to Solis for review.
At 13:20, Adrian was summoned to the station’s administrative section.
The message came from Commander Rell.
It contained no explanation beyond a request to discuss the previous day’s security incident.
Adrian saved his work and informed Orlov that he would be gone for a while.
“Good luck,” Orlov said.
Adrian looked at him.
“Do I need it?”
“Probably not.
But I’d rather be working on the network than explaining myself to security.”
Adrian couldn’t disagree.
The administrative section occupied a quieter part of the station, several levels away from the manufacturing control room.
The corridors were wider, the walls cleaner, and the lighting less harsh.
At the reception desk, an officer verified Adrian’s identification and directed him into a small conference room.
Commander Rell was waiting inside.
He sat behind a table with a terminal and several documents.
“Mr.
Vale.
Have a seat.”
Adrian sat down.
Rell opened a file.
“I’ve reviewed your explanation of yesterday’s incident.”
“All right.”
“Your account is consistent with the access logs.
You didn’t bypass any authorization controls, and you stopped investigating when instructed.”
Adrian waited.
“However, you accessed a component that should not have been available through your engineering credentials.”
“I understand that.
But I had no way of knowing it was restricted.”
Rell nodded.
“That’s been acknowledged.
The permissions have been corrected.”
“Does that mean the procedural review is finished?”
“Not yet.
The Selection Directorate handles your qualification record.
I’ve submitted my findings, but the final decision is theirs.”
Adrian looked at the file.
“Will your report say I violated the security rules?”
“No.”
That was reassuring.
Rell continued.
“I do need to ask you a few questions about what you observed.”
Adrian nodded.
“Go ahead.”
“What led you to examine the legacy optimization module?”
“I was tracing inconsistent commands through the manufacturing network.
Several controllers were receiving instructions that didn’t match the central scheduler’s output.”
“Why did you conclude the commands were being altered?”
“Because the scheduler logs showed one set of instructions, and the receiving controllers recorded another.
The differences were consistent across multiple platforms.”
“Could that have been caused by ordinary software errors?”
“Possibly.
But the changes weren’t random.
They affected shared resources in ways that increased arbitration conflicts.”
Rell made a note.
“Did you identify the source of the alterations?”
“The legacy module was the last processing layer I could trace them through.
I didn’t have enough information to determine whether it was generating the changes or passing them along from somewhere else.”
Rell looked up.
“That’s an important distinction.”
“I know.”
“Did you recognize the module’s name?”
Adrian hesitated.
“Continuity Optimization?”
“Yes.”
“I recognized the word.
I didn’t recognize the component.”
“Did the name suggest anything to you?”
Adrian considered his answer.
“The Continuity Directorate, obviously.
But that doesn’t mean they’re connected.
Continuity is a common term in computational systems.”
Rell watched him for a moment.
“Good.
I wanted to establish that you hadn’t made assumptions based on the name alone.”
“I hadn’t.”
Rell closed the file.
“One final question.
Have you discussed the module with anyone outside the engineering team?”
“No.”
“Not your supervisor on Earth?”
“No.”
“Not other candidates in the Selection Program?”
“No.”
Rell nodded.
“Very well.
You’re free to return to work.”
Adrian remained seated.
“Can I ask something?”
“Go ahead.”
“Is the module responsible for the manufacturing failures?”
Rell considered the question.
“The investigation is ongoing.”
“Do you know whether the interference is intentional?”
“I can’t discuss the findings.”
Adrian nodded slowly.
“All right.”
Rell leaned back.
“Mr.
Vale, I understand your frustration.
You identified a problem and were told to stop investigating it.
But there are systems aboard this station that fall outside the engineering division’s authority.”
“Even when they’re affecting the engineering systems?”
“Especially then, sometimes.”
Adrian didn’t find that answer particularly satisfying.
But he could tell the conversation was finished.
He stood.
“Thank you for reviewing the incident.”
Rell nodded.
“Continue your assignment.
Dr.
Solis has spoken highly of your work.”
Adrian left the room.
That evening, the manufacturing network suffered another major disruption.
Adrian was eating dinner in the station cafeteria when his terminal displayed an emergency engineering notification.
MANUFACTURING NETWORK ALERT
ASSEMBLY YARD THREE — PRODUCTION HALTED
RESOURCE COORDINATION FAILURE
ALL ASSIGNED ENGINEERS REPORT TO CONTROL
He abandoned the rest of his meal and hurried toward the engineering section.
Several engineers were standing around the central display, examining a network diagram covered in red warning indicators.
Dr.
Solis was speaking with a station operations officer.
Orlov waved Adrian over.
“Three platforms have stopped production.
The controllers are rejecting each other’s resource allocations.”
Adrian opened the diagnostic interface.
The problem was worse than anything they had encountered during testing.
Hundreds of manufacturing units were waiting for resource confirmations.
Several transport vessels had been reassigned repeatedly, creating conflicts between production lines.
The central scheduler was attempting to resolve the situation by issuing new instructions, but those instructions were making the network increasingly unstable.
Adrian examined the logs.
“Why hasn’t the scheduler stopped issuing new allocations?”
Orlov shook his head.
“It thinks the network’s still operating normally.
The local controllers are reporting inconsistent states, but the scheduler keeps trying to optimize around them.”
Adrian looked toward Solis.
“We need to suspend automatic rescheduling.”
She turned.
“What happens if we do?”
“Existing production lines can continue using their current allocations.
New transfers will be delayed, but we can stop the conflicts from spreading.”
“How much production capacity would we lose?”
“Probably fifteen to twenty percent temporarily.
Maybe more.”
Solis considered the figures.
They were already losing considerably more than that.
“Do it.”
Adrian opened the scheduler controls.
Then stopped.
ACCESS DENIED
AUTHORIZATION LEVEL INSUFFICIENT
He stared at the message.
The security restrictions imposed that morning prevented him from modifying the central scheduling system.
He looked toward Orlov.
“I can’t access the controls.”
Orlov moved to the workstation.
He tried.
The system rejected him as well.
Solis approached.
“What’s happening?”
“Security restricted the scheduler interface,” Adrian said.
“We can’t suspend automatic rescheduling.”
Solis frowned.
“That’s supposed to be an engineering control.”
“Apparently not anymore.”
She contacted station operations.
A minute later, an officer answered.
“Operations control.”
“This is Dr.
Solis.
We need emergency access to the manufacturing scheduler.
Our engineering credentials have been restricted.”
The officer checked the system.
“That interface is currently under security authority.”
“Then transfer me to whoever can authorize it.”
“One moment.”
The connection went silent.
Adrian watched the network diagram.
Another production line stopped.
Then another.
The central scheduler continued issuing new allocations.
He examined the available controls.
There was still one function he could access.
LOCAL RESOURCE RESERVATION MANAGEMENT
The security restrictions prevented him from changing the central scheduler, but they hadn’t disabled the local arbitration controls.
He opened the interface.
If he couldn’t stop the scheduler from issuing instructions, perhaps he could prevent the local controllers from accepting them.
He began constructing a temporary protocol.
Orlov noticed.
“What are you doing?”
“Trying to isolate the local controllers from the scheduler.”
“Can you do that?”
“Not directly.
But I can change how they validate new allocations.”
Orlov examined the code.
“You’re going to reject every instruction that conflicts with an active reservation.”
“Yes.”
“That’ll create a backlog.”
“Better than letting the scheduler keep changing the allocations.”
Orlov considered it.
Then nodded.
“I’ll help.”
They worked quickly.
The modification was simple in principle.
Each local controller would maintain its existing resource reservations and refuse new instructions that contradicted them until the conflict could be reviewed.
It wouldn’t restore normal production.
But it could prevent further disruption.
Adrian completed the protocol.
Orlov checked it.
They ran a short simulation.
The results were promising.
Solis returned.
“Security’s still reviewing the authorization request.”
Adrian looked up.
“We have another option.
We can apply a temporary validation rule through the local arbitration system.”
He explained the modification.
Solis examined the simulation.
“How long will it take to deploy?”
“Five minutes, maybe less.”
“Risks?”
“Some transfers will be delayed.
We could also end up preserving incorrect reservations, but the system won’t issue new conflicting ones.”
Solis looked toward the main display.
Production capacity continued falling.
“Deploy it.”
Adrian initiated the update.
The controllers began accepting the new validation rules.
For the first minute, little changed.
Then the number of new arbitration conflicts began declining.
Several production lines stabilized.
The central scheduler continued issuing instructions, but the local controllers rejected those that contradicted existing reservations.
After five minutes, the network stopped deteriorating.
After ten, production capacity began recovering.
Orlov watched the figures.
“That worked.”
Adrian nodded.
“For now.”
Solis examined the network.
“We’re still operating at sixty-eight percent capacity.”
“Better than forty-two,” Orlov said.
She nodded.
“Keep monitoring it.
I want the remaining conflicts resolved before the next shift.”
Adrian leaned back.
His hands were trembling slightly from the intensity of the last twenty minutes.
He hadn’t noticed until now.
He took a drink of water and returned to the logs.
The emergency continued for another three hours.
The engineering team gradually restored production across the affected platforms, manually resolving resource conflicts and adjusting the temporary validation rules.
By the time the situation stabilized, the network was operating at eighty-nine percent of normal capacity.
It wasn’t perfect.
But the immediate crisis had passed.
Solis gathered the engineers for a short debriefing.
“The local validation protocol prevented a complete shutdown.
Good work.”
She looked toward Adrian and Orlov.
“I want the modification reviewed and incorporated into the emergency operating procedures.”
Orlov nodded.
“We’ll prepare the documentation.”
Solis continued.
“Security has agreed to provide a technical representative for the remaining investigation.
Until then, we’re keeping the temporary restrictions in place.”
Several engineers looked unhappy.
Adrian didn’t blame them.
The restrictions had nearly prevented them from responding to a serious production failure.
After the meeting, Solis approached him.
“How’s your qualification review?”
“Still pending.”
“I’ll speak to the Selection Directorate again.
The security incident shouldn’t count against you.”
“Thanks.”
She glanced toward the main display.
“And today’s work will be included in your performance assessment.”
Adrian nodded.
“All right.”
Solis hesitated.
“There’s something I want you to understand.
The orbital division is under enormous pressure.
Every day we lose production capacity, the fleet schedule becomes harder to maintain.”
“I know.”
“Then you understand why I need engineers who can solve problems without creating new ones.”
Adrian looked at her.
“Are you saying I created a problem?”
“No.
I’m saying the security situation is complicated, and I need you to work within the limits they’ve imposed.”
“I did.”
“You did today.
Keep doing it.”
Adrian nodded.
“I will.”
She returned to her workstation.
Adrian watched her leave.
He understood her position.
Solis was responsible for maintaining production.
She couldn’t afford to become involved in a dispute between engineering and security, especially when the manufacturing schedule was already behind.
But Adrian couldn’t help thinking that the restrictions themselves had contributed to the emergency.
He had identified the suspicious module.
Security had taken control of the investigation.
And now the engineering team was being forced to work around systems it wasn’t allowed to examine.
It seemed like a poor way to manage a critical project.
Adrian returned to his quarters shortly before midnight.
He was exhausted.
The artificial gravity no longer felt strange, but the constant background vibration of the station had begun to bother him.
He could feel it through the floor, a faint reminder of the enormous machinery operating throughout the structure.
He sat at his desk and opened his qualification record.
A new evaluation had appeared.
SPECIALIZED TECHNICAL QUALIFICATION
FIELD PERFORMANCE REVIEW — DAY 7
TECHNICAL PERFORMANCE: EXCEPTIONAL
PROBLEM-SOLVING: EXCEPTIONAL
COLLABORATIVE PERFORMANCE: STRONG
PROCEDURAL COMPLIANCE: SATISFACTORY
OVERALL STATUS: ON TRACK
Adrian read the report twice.
The procedural review had been resolved.
He opened the details.
PREVIOUS SECURITY CONCERN CLOSED
NO VIOLATION IDENTIFIED
He exhaled.
That was one less problem to worry about.
He sent Ren a short update describing the successful emergency stabilization, avoiding any mention of the restricted module.
Then he opened a message from Mira.
It had arrived several hours earlier.
Finished another assessment today.
We had to manage a simulated settlement with limited resources, but the rules kept changing.
I think we did well.
How’s the orbital assignment?
Adrian replied.
Busy.
We had a major network failure today, but we managed to stabilize it.
My evaluation’s going well so far.
He hesitated.
Then added:
The station’s impressive.
I’ll show you some pictures when I get back.
He sent the message and placed the terminal on the desk.
Outside the window, Earth drifted slowly beneath the station.
The planet’s night side was illuminated by enormous clusters of artificial light.
New Geneva was somewhere down there.
So was the residential complex where Adrian had left most of his belongings.
And beyond the protected cities were billions of people who would never have the opportunity to leave.
He watched the planet for a while.
Then he went to bed.
The following morning, Commander Rell received a confidential report from the station’s internal security division.
The report concerned the Continuity Optimization Module.
It contained several pages of technical analysis, including the altered manufacturing commands and the module’s execution history.
Rell read the summary.
The module had been active for years.
Its original function was legitimate.
But recent updates had introduced unauthorized behavior.
The investigation had identified several changes to the command-processing routines, all of which appeared designed to interfere with resource coordination.
The changes were subtle enough to resemble ordinary software faults.
They were also consistent enough to suggest deliberate modification.
The most recent update had been approved through a maintenance account belonging to a former systems administrator.
The administrator had left the station eighteen months earlier.
The account should have been disabled.
It wasn’t.
Rell frowned.
He checked the access history.
The account had been used several times during the previous year, always through internal network connections.
No external access attempts were recorded.
Whoever had modified the module had either possessed legitimate access to the station’s systems or found a way to use an account that should no longer have existed.
Rell contacted the security analysis team.
“Have you identified who used the maintenance account?”
“Not yet.
The access records are incomplete.”
“Why?”
“The module’s logging system was modified during the same update.
Some of the original records were overwritten.”
Rell considered that.
“Can you recover them?”
“We’re trying.
But it’ll take time.”
“Keep working.”
He ended the call.
Then he opened Adrian Vale’s personnel record.
The engineer had identified the interference after less than a day aboard the station.
That was impressive.
But it also raised a question.
Why had nobody else noticed?
The manufacturing network had been experiencing problems for months.
Dozens of engineers had investigated the failures.
Most had attributed them to the system’s increasing complexity.
Adrian had recognized the pattern because his arbitration modification forced him to examine the relationship between central instructions and local controller behavior.
He had approached the problem from a different direction.
Rell looked at the report again.
Then he opened a secure communication channel.
The man on the display was the same official Rell had contacted two days earlier.
He listened without interruption as Rell summarized the investigation.
When Rell finished, the man remained silent for several seconds.
“So the module was deliberately modified.”
“That’s our current assessment.”
“And you haven’t identified the person responsible.”
“No.”
“What about Vale?”
“His procedural review has been closed.
He performed well during yesterday’s production emergency.”
“How well?”
“He developed a temporary protocol that prevented the network from deteriorating further.
The engineering division credits him and another engineer with stabilizing the affected platforms.”
The man nodded.
“Good.”
Rell hesitated.
“Sir, I think we need to consider the possibility that the interference is part of a broader effort to disrupt the fleet’s construction.”
“That’s already being considered.”
Rell looked at him.
“Then you know more than I do.”
The man didn’t respond immediately.
“Commander, your responsibility is to maintain station security.
Continue investigating the unauthorized updates and identify the person who made them.”
“Understood.”
“Do not expand the investigation beyond your assigned authority.”
Rell frowned.
“With respect, sir, if the interference involves personnel outside this station—”
“Then the appropriate departments will handle it.”
The answer was firm.
Rell nodded.
“Very well.”
The man glanced at another display.
“One more matter.
The Strategic Personnel Office has requested that Adrian Vale’s technical evaluation be forwarded directly to them.”
“Why?”
“They’re reviewing several candidates with unusual performance records.”
Rell considered that.
“Is this related to the security incident?”
“Not directly.”
“Then why the interest?”
The man looked back at him.
“Because the Exodus Project needs people who can solve problems that our existing systems weren’t designed to handle.”
Rell remained silent.
The man continued.
“Vale has demonstrated that ability more than once.
We want to know whether he can do it consistently.”
“Understood.”
The connection ended.
Rell sat back.
He had received enough information to know that the situation was more complicated than a routine software compromise.
But not enough to understand what was actually happening.
He disliked that.
Still, there was little he could do.
He closed the communication channel and returned to the security report.
On the eighth day of his technical qualification, Adrian received an unexpected assignment.
It arrived during the morning engineering briefing.
SPECIALIZED TECHNICAL QUALIFICATION
SUPPLEMENTARY EVALUATION AUTHORIZED
ASSESSMENT TYPE: INDEPENDENT SYSTEMS REVIEW
DURATION: 48 HOURS
OBJECTIVE: IDENTIFY AND RESOLVE A CRITICAL INFRASTRUCTURE FAILURE
Adrian stared at the message.
He had already been working on critical infrastructure failures for more than a week.
Why did the Selection Directorate need a separate evaluation?
He opened the attached instructions.
The assessment would take place within a restricted simulation environment, using a model of an actual Exodus support system.
He would be given limited information about the system’s architecture and operational history.
His task was to identify the cause of a recurring failure and propose a solution.
The evaluation would be conducted independently of the Orbital Infrastructure Division.
Adrian frowned.
That was unusual.
His original qualification had been based on practical engineering work.
Now the Council was introducing an additional examination in the middle of the assessment.
He contacted Solis.
She answered a few minutes later.
“Adrian?”
“I received a supplementary evaluation notice.
Do you know anything about it?”
Solis looked confused.
“What kind of evaluation?”
“Independent systems review.
Forty-eight hours.
It says the Selection Directorate authorized it.”
She checked her terminal.
“I haven’t received anything.”
Adrian forwarded the notice.
Solis read it.
Then she frowned.
“This isn’t part of the assessment plan I approved.”
“Can they add new requirements without informing you?”
“Apparently.”
She examined the authorization.
“There’s a separate review office listed here.
Strategic Personnel.”
Adrian looked at the document.
He hadn’t noticed that.
“Do you know what they do?”
“Not specifically.
They’re involved in specialized recruitment, I think.”
“Should I be worried?”
Solis considered the question.
“I don’t think so.
Your technical performance has been excellent.
If they want another evaluation, it probably means they’re considering you for something beyond the standard qualification process.”
Adrian wasn’t sure whether that was reassuring.
“When does it start?”
“Tomorrow morning, according to the notice.”
He nodded.
“All right.”
Solis looked at him.
“Don’t let it interfere with the integration work today.
We still need to finish the emergency protocol review.”
“Understood.”
They ended the call.
Adrian returned to his workstation.
He opened the supplementary evaluation details again.
The system description was brief.
SYSTEM CATEGORY: AUTONOMOUS RESOURCE MANAGEMENT
OPERATIONAL ENVIRONMENT: CLOSED HABITAT
FAILURE TYPE: UNDISCLOSED
ASSESSMENT CONDITIONS: CONTROLLED
Adrian studied the words.
Closed habitat.
Autonomous resource management.
That could describe dozens of systems used throughout the Exodus Project.
Life support.
Food production.
Energy distribution.
Environmental regulation.
But the phrase closed habitat suggested something more specific.
A system designed to maintain a population without external assistance.
He thought about the fleet.
The enormous ships under construction outside the station.
The millions of passengers who would eventually live aboard them.
And the centuries-long journey toward Haven.
Perhaps the assessment involved one of the fleet’s internal management systems.
That would be interesting.
He closed the notice and returned to work.
Tomorrow, he would find out.
Far from Elysium-7, in a secure research facility attached to the Exodus Council’s central administrative network, Lucian Voss examined a list of candidates selected for supplementary evaluation.
There were twenty-four names.
Most belonged to engineers, systems architects, and computational researchers who had demonstrated exceptional performance during recent qualification stages.
Several had been recruited through technical assignments.
Others had been selected directly from the competitive examination rankings.
Adrian Vale’s name appeared near the middle.
Lucian opened his record.
The recent evaluations were impressive.
Exceptional technical performance.
Strong problem-solving.
Improving collaboration.
A security incident that had been resolved without disciplinary action.
And a successful response to a major manufacturing network failure.
Lucian examined the engineering reports.
He recognized the arbitration architecture.
It was a clever design, particularly the use of temporary local authority to maintain coordination during communication failures.
But what interested him most was the way Adrian had responded to the unexpected production emergency.
He hadn’t attempted to repair the entire network.
Instead, he had identified the part of the system he could still control and used it to prevent the failure from spreading.
That was a useful kind of judgment.
Lucian closed the report.
A message appeared on his terminal.
SUPPLEMENTARY EVALUATION GROUP CONFIRMED
ALL CANDIDATES APPROVED
ASSESSMENT ENVIRONMENT READY
Lucian opened the evaluation parameters.
The simulation was considerably more complicated than the ordinary Selection Games.
It modeled a closed habitat containing several thousand inhabitants, with autonomous systems responsible for maintaining essential resources.
The candidates would be given incomplete information.
They would need to investigate recurring failures, manage competing priorities, and make decisions under uncertain conditions.
The system would evaluate not only whether they solved the technical problem, but how they approached it.
Lucian examined the scoring criteria.
Technical accuracy.
Resource efficiency.
Risk management.
Adaptability.
And one additional category.
INSTITUTIONAL DEPENDENCE
He paused.
That category wasn’t part of the standard Selection Program.
He opened the definition.
The assessment would measure how candidates responded when established procedures, authority structures, or official information conflicted with their own observations.
Lucian considered that.
It was a useful measure for independent systems architects.
But it could also be interpreted in several ways.
A candidate who ignored authority might be dangerously reckless.
A candidate who obeyed every instruction might fail to recognize a serious institutional error.
The distinction depended heavily upon how the evaluation was designed.
He opened the test environment.
The scenario had been prepared by the Strategic Personnel Office.
Its central problem was not a simple equipment failure.
The habitat’s management system was functioning according to its official specifications.
The problem was that those specifications were producing increasingly harmful outcomes.
Lucian examined the underlying model.
Then he understood why the assessment had been created.
The candidates weren’t being asked to repair a broken system.
They were being asked to recognize that a system could operate exactly as designed and still be wrong.
He looked at Adrian Vale’s name again.
Then he closed the file.
Tomorrow would be interesting.