Adrian arrived at Administrative Section C nine minutes before his scheduled interview.
He had slept poorly.
Forty-eight hours of accelerated simulation had left him with a strange sense of time, as though the previous two weeks had passed somewhere he could no longer reach.
He remembered the streets of Habitat Meridian, the arguments in the Assembly, and the people he had interviewed with a clarity that made their artificial nature difficult to accept.
The technician had assured him that the sensation would fade.
Adrian hoped so.
He had spent the morning checking his engineering messages and found himself briefly confused by references to work completed only three days earlier.
The administrative wing was quieter than the manufacturing sections, with carpeting instead of exposed composite flooring and walls decorated with photographs of completed orbital structures.
Most showed stations and shipyards from the previous century.
A few depicted early Exodus construction, when the fleet consisted of skeletal frameworks surrounded by scaffolding.
At the reception desk, a woman verified his credentials.
“Mr.
Vale?
You’re expected.
Conference room six, down the corridor on your right.”
“Thank you.”
He followed her directions.
The room’s door was open.
Inside, a young man sat at a conference table, reviewing something on a transparent display.
He had pale blond hair, neatly arranged, and wore a dark civilian jacket with a small identification emblem near the collar.
Adrian recognized him immediately.
Lucian Voss.
The last time they had occupied the same room, Lucian had finished first in the competitive selection while Adrian had been eliminated after a tie-breaking examination.
Lucian looked up.
“Adrian Vale.
Come in.”
Adrian entered.
“I wasn’t expecting you.”
“I assumed you might recognize me.”
“Your name was on the rankings often enough.”
Lucian smiled faintly and gestured toward the opposite chair.
“Please sit.
Would you like something to drink?”
“Water’s fine.”
Lucian used the table’s service panel.
A dispenser beside the wall produced two sealed containers, and he passed one across.
Adrian sat down.
He had expected an older official, perhaps someone from the Council’s engineering recruitment department.
Lucian was only a little older than he was, and his presence raised questions about the Strategic Personnel Office’s organization.
“Are you conducting the interview?” Adrian asked.
“Yes.
I’m attached to the Office as a technical evaluator.”
“Since when?”
“About six months.”
“While you were participating in the Selection Games?”
“Different responsibilities.
My own selection record is reviewed separately.”
Adrian opened the water.
“That seems like a conflict of interest.”
“It would be if I were evaluating my own advancement or deciding the rankings of candidates competing directly against me.
I’m not.”
“You’re evaluating someone you competed against.”
“That’s fair.
You can request another interviewer if you prefer.”
Adrian considered it.
He didn’t know whether another interviewer would be more impartial, and asking for one might delay an already complicated qualification.
“No.
We can continue.”
Lucian nodded and closed the display.
“Good.
I’d like to discuss your recent assessment, your engineering work, and a few questions about how you approach unfamiliar problems.”
“All right.”
“Before we begin, I should clarify something.
This interview isn’t part of your original fourteen-day qualification.
Your performance there is evaluated by the Orbital Infrastructure Division.”
“Then what is this for?”
“Potential recruitment into specialized technical programs.”
“What programs?”
“Several.
The Office works with departments that need personnel for difficult or sensitive assignments.”
“Can you be more specific?”
“Not until there’s a reason to consider you for a particular position.”
Adrian looked at him.
“That’s not especially informative.”
“No.
But I don’t want to suggest you’re being offered a position when we haven’t reached that stage.”
At least Lucian was willing to admit it.
Adrian leaned back.
“Fine.
What would you like to know?”
Lucian began with Habitat Meridian.
He asked Adrian to explain why he had focused on the labor allocation system when the habitat’s technical performance indicators were mostly satisfactory.
Adrian described the declining productivity, the repeated worker reassignment, and the way CIVIC had treated dissatisfaction as an independent behavioral problem rather than a possible consequence of its own policies.
Lucian listened without interrupting.
When Adrian finished, he opened a section of the assessment report.
“You identified the labor model relatively early.
Why didn’t you simply propose a replacement objective function?”
“Because I didn’t know enough about the population to design one responsibly.”
“You could have assigned greater weight to satisfaction and employment stability.”
“I considered that.
But it would’ve been another model deciding what people should value.
I wanted to see whether giving residents more control produced better outcomes before changing the system.”
“Your trial only involved two hundred people.”
“I know.”
“And it lasted ten simulated days.”
“Nine with useful measurements.
The first day was mostly transition.”
Lucian glanced at the report.
“You don’t think that’s enough to justify habitat-wide changes?”
“No.
It supports further testing.
It doesn’t prove the same result would hold for eighty thousand people.”
“Yet you recommended changing the governance structure.”
“Because the governance problem didn’t depend on the trial’s results.
The Assembly couldn’t revise policies without CIVIC approving the revisions.
That’s a separate issue.”
Lucian considered the distinction.
“Suppose the Assembly had voted to shut down CIVIC completely.
Would you have supported that?”
“No.
Too many systems depended on it.”
“Even if the Assembly had the legal authority?”
“Having authority doesn’t make a decision technically safe.”
“And who should determine whether it’s safe?”
“People with the relevant expertise, using evidence that can be examined and challenged.”
“That sounds similar to the arrangement CIVIC already had.”
“The difference is that CIVIC was reviewing its own decisions.
The Assembly’s committee could disagree with the management system without requiring its permission.”
Lucian looked down at the report.
“You spent almost a third of the assessment dealing with administrative procedures.
Some evaluators thought you lost sight of the technical objective.”
“Did they?”
“Yes.”
Adrian thought about it.
“They might be right, partly.
I could’ve spent more time improving the labor model.
But if I’d only fixed that, the next policy problem would’ve run into the same restrictions.”
“That’s the reasoning you gave in your final report.”
“Then you’ve already read my answer.”
Lucian smiled.
“I wanted to know whether you’d reached the same conclusion after leaving the simulation.”
Adrian took a drink of water.
“Have I passed?”
“The final decision hasn’t been issued.”
“That’s becoming a familiar answer.”
Lucian glanced at him.
“Your original elimination?”
“Among other things.”
“We’ll discuss that shortly.”
The interview continued for nearly an hour.
Lucian moved through several hypothetical problems involving distributed networks, resource shortages, and autonomous decision-making.
Most were technical, but some concerned situations where the correct engineering decision might conflict with operational instructions.
Adrian answered where he could.
He also admitted when he lacked enough information.
One scenario involved a damaged transport network serving three orbital stations.
A central controller had to decide which station would receive a limited shipment of replacement components.
Lucian provided the population, production requirements, and estimated failure risks for each station.
Adrian studied the figures.
“Are the stations allowed to exchange resources afterward?”
“Assume they can, but transport is expensive.”
“How expensive?”
Lucian supplied the cost.
Adrian recalculated.
“Then I wouldn’t send the entire shipment to one station.
I’d split it between the first and third.”
“That reduces the immediate production benefit.”
“Yes, but it lowers the chance of a complete failure at the third station.”
“The second station has the largest population.”
“I can see that.
But its existing reserves are sufficient for another six weeks.
The third station has less than nine days.”
Lucian changed one of the parameters.
The third station’s reported reserves increased.
Adrian reconsidered.
“Where did that figure come from?”
“An updated inventory.”
“Was it independently verified?”
“Does that matter?”
“It matters if we’re changing the allocation based on it.”
Lucian supplied a verification record.
Adrian revised his answer.
They continued in this manner until Lucian closed the scenario.
“You’re slower than some of the other candidates.”
Adrian looked up.
“At these questions?”
“Yes.
Several completed that allocation problem in under three minutes.”
“Did they get it right?”
“Some did.”
“Then they did better than me.”
Lucian studied him for a moment.
“You don’t seem particularly bothered.”
“Should I be?”
“Most candidates are interested in how they compare.”
“I am.
But I can’t make myself faster by pretending I finished sooner.”
Lucian laughed quietly.
“Fair enough.”
Adrian didn’t particularly enjoy being tested by someone who had beaten him so thoroughly in the earlier examinations.
Still, Lucian’s questions were more interesting than he had expected, and the discussion was useful enough that he occasionally forgot it was an evaluation.
Then Lucian opened Adrian’s original Selection record.
“The tie-breaker against Mira Chen.”
Adrian recognized the scoring table immediately.
MIRA CHEN — 96.4
ADRIAN VALE — 96.3
He had looked at those numbers often enough.
“What about it?”
“Do you think the result was fair?”
Adrian considered his answer.
“The tie-breaker itself was fair enough.
We were given the same problem and evaluated using the same criteria.”
“But?”
“The reason we had to compete wasn’t fair.”
Lucian nodded.
“The professional allocation adjustment.”
“Yes.
We both performed well enough to advance under the published scoring rules.
Then the Council applied additional modifiers that changed the rankings.”
“Those modifiers are part of the selection framework.”
“They weren’t explained beforehand.”
“They were disclosed in the general regulations.”
“Buried in a document most candidates never see until after they’re registered.”
Lucian didn’t dispute that.
“Do you think the Council should eliminate professional allocation adjustments?”
“Not necessarily.
The fleet needs a balanced population.
It can’t take a billion engineers and expect everything to work.”
“Then what’s your objection?”
“Tell people what they’re actually competing for.
If there’s a limited allocation for each profession, publish the limits and explain how they’re applied.
Don’t make everyone think they’re competing on one ranking and then change the result using another.”
Lucian examined the record.
“The Council would argue that publishing exact allocation targets could encourage candidates to manipulate their professional classifications.”
“Then design better verification procedures.”
“That would increase administrative costs.”
“Probably.”
“And delay selection.”
“Maybe.
But the current system wastes people’s time too.”
Lucian looked at him.
“Your elimination has made you rather critical of the process.”
“It made me pay more attention to it.”
“Would you feel the same way if you’d won?”
Adrian thought about Mira.
She had advanced because her design had scored one-tenth of a point higher.
She hadn’t done anything wrong.
“I’d like to think so,” he said.
“But I probably wouldn’t have spent as much time examining the rules.”
Lucian seemed satisfied with that answer.
He closed the file.
“All right.
Let’s discuss your work aboard Elysium-7.”
Adrian had expected the manufacturing network to come up eventually.
Lucian began with the arbitration improvements, asking about local reservation authority and the conditions under which individual controllers could reject central instructions.
Adrian explained the architecture.
Lucian was familiar with distributed systems and asked detailed questions about failure recovery, communication delays, and the risk of controllers maintaining inconsistent resource states.
The discussion became technical enough that Adrian found himself sketching a network diagram on the conference table.
“Your local controllers can preserve existing reservations,” Lucian said, examining the diagram.
“But what happens when the original reservation becomes invalid?”
“They have an expiration mechanism.”
“Based on time?”
“Time and resource state.
A reservation expires when its validity conditions are no longer met, although the controller can request confirmation if the information is incomplete.”
“That creates a dependency on the information source.”
“Yes.”
“What if the information source is compromised?”
Adrian paused.
“Then we have a bigger problem.”
“How would you handle it?”
“Independent verification where possible. Follow the newest chapters on novelping.com.
But it depends on which part of the network is compromised.”
Lucian nodded.
“That’s similar to the situation you encountered during the production emergency.”
Adrian looked at him.
“You’ve read the incident report.”
“I have.”
“Then you know the central scheduler was issuing inconsistent instructions.”
“According to the engineering logs.”
“According to the receiving controllers too.”
Lucian opened another document.
“The report mentions an unauthorized legacy component.”
Adrian stopped drawing.
“That’s under security investigation.”
“I’m aware.”
“Am I allowed to discuss it?”
“You can discuss what you observed through your legitimate engineering access.
I’m not asking you to disclose restricted security findings.”
Adrian considered that.
“Then yes.
I traced altered commands to a legacy processing layer.
I couldn’t determine whether the module was generating them or forwarding them from somewhere else.”
“What was unusual about the commands?”
“They increased arbitration conflicts.
Some reassigned resources that were already committed elsewhere.
Others introduced small timing differences that caused local controllers to disagree.”
“Could the behavior have been accidental?”
“Individual errors could have been.
But the overall pattern was difficult to explain as ordinary corruption.”
“Why?”
“Because the changes were too consistent.
They affected specific types of transactions and tended to create conflicts without immediately triggering major alarms.”
Lucian examined him.
“You’re suggesting deliberate interference.”
“I’m saying that’s one possible explanation.
Security’s investigation should establish whether it’s true.”
“Do you know the module’s original purpose?”
“No.”
“Any theories?”
Adrian hesitated.
“It was called Continuity Optimization.
The name might be meaningless.
I didn’t have enough documentation to identify its function.”
Lucian remained silent.
Adrian continued.
“If you’re asking whether I think it was connected to the old Continuity Directorate, I don’t know.
The name alone isn’t evidence.”
“That’s sensible.”
Lucian closed the document.
Adrian watched him.
“Can I ask why you’re interested?”
“Because the Office reviews technical personnel for assignments involving complex autonomous systems.
Your response to the incident is relevant.”
“Does the Office have access to the security investigation?”
“To some of the findings.”
“Then you probably know more about the module than I do.”
“Possibly.”
Adrian waited.
Lucian didn’t elaborate.
“Right,” Adrian said.
“I suppose that part isn’t included in the interview.”
“Not today.”
The formal interview ended at 11:42.
Lucian thanked Adrian for his time and told him that the Strategic Personnel Office would contact him after completing its review.
Adrian stood and collected his terminal.
Before he reached the door, Lucian spoke again.
“Mr.
Vale.
One more question, if you don’t mind.”
Adrian turned.
“Go ahead.”
“If you complete your technical qualification and regain eligibility for the advanced selection stages, what do you intend to do?”
“Continue competing.”
“And if you don’t qualify?”
Adrian thought about the question.
He had considered that possibility many times.
His technical assessment was going well, but the Selection Program had already demonstrated that strong performance didn’t guarantee advancement.
“I’ll look for another route.”
“Through engineering?”
“Probably.
The fleet still needs people to build it, even if they aren’t going aboard.”
Lucian looked at him.
“Would you accept a position that didn’t guarantee a place on the fleet?”
“Depends on the position.”
“What if it involved working on systems used aboard the Exodus vessels?”
“That’s more interesting.”
“Even if you remained on Earth?”
Adrian paused.
“How long would the assignment last?”
“Assume several months.”
“Then I’d want to know what happens afterward.”
Lucian nodded.
“A reasonable concern.”
Adrian studied him.
“Are you offering me something?”
“No.
I’m asking whether you would consider it.”
“Then yes, under the right circumstances.”
“Thank you.”
Adrian left the room.
He had walked halfway down the corridor before realizing that the final questions had been considerably more specific than the rest of the interview.
The Strategic Personnel Office was interested in his willingness to work on the fleet’s autonomous systems.
Perhaps that was all there was to it.
Still, he couldn’t help wondering why Lucian Voss was involved.
Mira Chen had spent the previous three days in a residential assessment facility on Earth.
Her latest examination had involved managing a temporary settlement of four hundred simulated inhabitants, with each candidate assigned responsibility for a different administrative department.
Unlike the earlier Selection Games, this assessment had lasted several days and required candidates to work together through changing conditions.
The first day had been manageable.
By the second, the settlement’s water supply had developed a contamination problem, forcing the candidates to decide whether to shut down industrial production or reduce residential consumption.
By the third, a transportation failure had delayed food deliveries, and several departments had begun competing for emergency resources.
Mira had been assigned to infrastructure planning.
She had performed well technically, but the assessment had exposed an issue she hadn’t expected.
Some of the other candidates were unwilling to share information unless they received something in return.
During one meeting, the agricultural representative had withheld production estimates to strengthen his bargaining position.
The medical representative had exaggerated expected demand to secure additional supplies.
Mira had spent much of the second day correcting decisions based on incomplete or misleading reports.
She found it exhausting.
The assessment ended without announcing individual scores.
Now she was sitting in a waiting room with twenty other candidates, watching the results appear on a wall display.
RESIDENTIAL QUALIFICATION — STAGE TWO
ADVANCEMENT STATUS: RELEASED
Names began appearing.
Several candidates cheered.
Others remained silent.
Mira found her name near the top.
MIRA CHEN
OVERALL SCORE: 91.7
STATUS: ADVANCED
She exhaled.
That was good.
Not exceptional, but comfortably above the qualification threshold.
She opened the detailed report.
Her technical planning and resource management scores were high.
Her negotiation and collaborative leadership scores were lower.
The comments noted that she had sometimes relied too heavily on formal agreements and struggled to respond when other candidates acted opportunistically.
Mira read the comments twice.
She didn’t particularly like them.
But she couldn’t say they were entirely wrong.
She had expected the other candidates to cooperate once they understood that the settlement’s survival depended on it.
Several had continued pursuing their own departmental scores instead.
The examination had rewarded cooperation, but it hadn’t removed the incentives to compete.
She sent Adrian a message.
Passed the residential assessment.
91.7.
Apparently I need to improve my negotiation skills.
His reply arrived several minutes later.
Congratulations.
That’s a good score.
What happened with negotiation?
Mira typed while walking toward the exit.
Half the people in my group treated every resource discussion like an auction.
I kept expecting them to stop once things got serious.
Did they?
Not really.
Sounds unpleasant.
It was.
How was your interview?
Adrian hesitated before replying.
Interesting.
Lucian Voss was the interviewer.
Mira stopped walking.
She read the message again.
Lucian Voss?
From our selection group?
Yes.
Apparently he works with the Strategic Personnel Office.
That’s strange.
Did he say what they wanted?
Specialized recruitment.
Nothing definite.
Mira considered that.
Lucian had been the strongest candidate in their original group, but she hadn’t realized he was already working for the Council.
She remembered how comfortably he had navigated the Selection Games, rarely appearing surprised by the format or requirements.
At the time, she had assumed he was simply well prepared.
Now she wasn’t so sure.
Be careful with him, she wrote.
Adrian replied.
Why?
Mira thought about her answer.
She didn’t have evidence that Lucian had done anything wrong.
I don’t know.
He seemed to understand the selection system better than the rest of us.
Maybe that’s just because he’s good at it.
I’ll keep that in mind.
Mira put away her terminal.
Outside the assessment facility, the artificial sky above New Geneva had turned a dull orange.
A public announcement warned residents that atmospheric filtration efficiency would be reduced for several hours while maintenance crews replaced damaged components.
People continued walking beneath the enormous overhead structures, barely looking up.
Mira joined the crowd heading toward the transit station.
Her next assessment would begin in five days.
For the first time since entering the Selection Program, she was beginning to believe she might actually reach the final qualification stages.
That possibility was exciting.
It was also becoming harder to think about what advancement meant for everyone who failed.
Adrian returned to the engineering section shortly after noon.
Orlov was reviewing the latest manufacturing network reports.
“How’d the interview go?”
“Fine, I think.”
“Did they tell you anything useful?”
“Not much.
They asked about my assessment and the network.”
Orlov glanced up.
“The network?”
“Mostly the arbitration architecture.”
“Good.
Maybe they’ll give us more engineers.”
Adrian sat down.
“Any new problems?”
“Nothing major.
The temporary validation protocol’s holding, and we’ve recovered most of the lost production capacity.”
“How much?”
“Ninety-four percent as of this morning.”
“That’s better.”
“Still below target, but Solis is happy enough.”
Adrian opened his workstation.
He had several pending tasks, including reviewing the emergency protocol documentation and preparing a revised version of the local reservation system.
The work was familiar.
After spending sixteen simulated days dealing with a habitat’s political structure, it was almost relaxing to return to ordinary engineering problems.
Orlov leaned over.
“By the way, your departure schedule’s changed.”
Adrian looked up.
“Changed how?”
“Your shuttle’s been moved forward.
You’re leaving tomorrow morning.”
“I thought I had another day.”
“So did I.
Apparently the station’s rotating temporary personnel earlier than planned.”
Adrian checked his messages.
A transport notice had arrived while he was in the interview.
FIELD ASSIGNMENT UPDATE
ELYSlUM-7 DEPARTURE: TOMORROW, 07:30
DESTINATION: NEW GENEVA ORBITAL TRANSFER TERMINAL
SPECIALIZED TECHNICAL QUALIFICATION: CONTINUES REMOTELY
He examined the authorization.
The notice was signed by station administration.
There was no explanation for the schedule change.
“Did Solis approve this?”
“She said it was an administrative decision.
She’s trying to get it reversed.”
Adrian looked toward the manufacturing displays.
He had only been aboard the station for a few days, but the assignment had become the most useful part of his qualification.
He had learned more about the real manufacturing network than he could have through months of remote simulation.
Leaving early was disappointing.
“Do you know why they’re rotating people?”
“No.
Could be transport availability.
Could be security.
Nobody’s told me.”
Adrian nodded.
He didn’t have much choice.
He returned to his work.
At 15:10, Dr.
Solis called Adrian into her office.
She looked tired.
Several engineering reports were open across her desk, and a half-finished meal sat beside the terminal.
“Sit down.”
Adrian took the chair opposite her.
“I heard about the shuttle.”
Solis nodded.
Station administration refused.”
“Did they say why?”
“Personnel rotation requirements.”
“That’s vague.”
“It is.”
She closed one of the reports.
“I don’t think it’s related to your performance.
Your work here has been excellent, and the security review was resolved.”
“Then why send me back early?”
Solis hesitated.
“I don’t know.”
Adrian watched her.
She seemed more irritated than concerned.
“I’ve submitted your field evaluation,” she continued.
“It’ll count toward the remaining days of your qualification.”
“How did I do?”
“Very well.
Your technical work exceeded expectations.
Your collaboration improved considerably after the first few days, and the emergency response was particularly strong.”
“That’s good.”
“There are still areas you need to work on.”
Adrian nodded.
“Such as?”
“You tend to investigate problems independently before bringing other people into the process.
That can be useful, but it also means the rest of the team sometimes doesn’t know what you’re doing.”
Adrian thought about the Continuity module.
“I can see that.”
“During the production emergency, you worked much better with Orlov.
You explained your approach, let him challenge it, and revised the solution together.
That’s the kind of behavior I want to see.”
“Understood.”
Solis opened another file.
“I’ve also recommended that your arbitration modifications be incorporated into the fleet’s standard manufacturing control architecture.”
Adrian looked up.
“Really?”
“Yes.
The results justify it.
We’ll need more testing, but the design is promising.”
“Thank you.”
“Don’t thank me yet.
If it gets approved, you’ll probably spend the next several weeks answering questions from people who think they can improve it.”
Adrian smiled.
“That sounds manageable.”
Solis returned the smile.
Then her expression became more serious.
“There’s one other thing.”
Adrian waited.
“The Strategic Personnel Office requested a copy of your field evaluation.
That’s not unusual for high-performing candidates, but they’ve also asked that any future assignments involving you be reviewed through their office.”
“What does that mean?”
“It means they want to be informed before we assign you to certain projects.”
“Can they prevent me from working on them?”
“Possibly.
Depends on the project.”
Adrian considered that.
“Did they explain why?”
“No.”
“Do you think it’s because of the security incident?”
Solis looked at him for a moment.
“I think someone has taken an interest in your work.
Whether that’s good or bad, I can’t tell you.”
Adrian nodded.
That was about as much as he expected.
Solis leaned back.
“Don’t spend too much time worrying about it.
Finish your qualification.
You’ve got a strong record, and I’d be surprised if you didn’t pass.”
“All right.”
“And Adrian?”
“Yes?”
“Whatever happens with selection, keep doing engineering.
You’re good at it.”
He looked at her.
“That’s the plan.”
Lucian Voss was reviewing Adrian’s interview notes when his terminal received an encrypted communication.
The sender was listed only as DIRECTORATE LIAISON — LEVEL FOUR.
He accepted the call.
A man appeared on the display.
He was older, with closely cropped gray hair and a severe expression.
“How did the interview go?”
“Well.
Vale performed as expected.”
“Your recommendation?”
“Continue observation.
He’s technically capable and demonstrates independent judgment without being unnecessarily reckless.”
“Would he accept a specialized assignment?”
“Possibly.
He wants to know what it would involve and whether it improves his chances of advancement.”
The man nodded.
“Reasonable.”
Lucian opened another document.
“I have concerns about the assessment design.”
“Which part?”
“The institutional dependence category.”
“What about it?”
“It rewards candidates for challenging authority, but the scoring doesn’t consistently distinguish between justified challenges and ordinary noncompliance.”
“The evaluators account for that.”
“Not sufficiently.
Four candidates attempted to bypass CIVIC’s restrictions directly.
Two received relatively high scores despite creating significant operational risks.”
The man considered that.
“Your proposed changes?”
“Separate independent reasoning from procedural risk.
A candidate should receive credit for recognizing a flawed system, but not automatically for ignoring its safeguards.”
“Submit the revision.”
Lucian nodded.
“I will.”
The man glanced at another display.
“What did Vale say about the Continuity Optimization Module?”
“Very little beyond the engineering report.
He recognized the suspicious command patterns but didn’t claim to know their origin.”
“Did he connect it to the former Directorate?”
“He considered the possibility but didn’t treat the name as evidence.”
“Good.”
Lucian looked at the man.
“Has the security investigation identified the source of the modifications?”
“Not yet.”
“Then why was his field assignment shortened?”
The man paused.
“Station administration requested the rotation.”
“That’s not an answer.”
“It is the information you’re authorized to receive.”
Lucian remained silent.
The man continued.
“Your responsibility is candidate evaluation.
Leave the security investigation to the appropriate departments.”
Lucian nodded.
“Understood.”
The connection ended.
He sat back.
The response bothered him.
He had been told that the Strategic Personnel Office was evaluating candidates for specialized roles aboard the Exodus fleet.
That was true, as far as he could tell.
But the Office also appeared to be involved in matters that had little to do with recruitment.
Manufacturing security.
Personnel movement.
Restricted legacy systems.
Lucian had access to more information than most candidates, but he was beginning to suspect that even his own access was carefully limited.
He opened Adrian’s file again.
Then he added a note.
CANDIDATE DEMONSTRATES STRONG TECHNICAL JUDGMENT.
RECOMMEND CONTINUED EVALUATION THROUGH STANDARD CHANNELS.
NO BASIS FOR RESTRICTIVE MEASURES.
He submitted it.
That evening, Adrian packed his belongings.
He had brought very little to Elysium-7: a few changes of clothing, his personal terminal, and a small collection of engineering notes.
Most of his work was stored in the station’s secure network and would remain accessible through the institute once he returned to Earth.
He finished packing in less than twenty minutes.
Then he went to the observation deck.
The station’s public viewing area was nearly empty.
A few technicians sat near the windows, talking quietly over drinks.
Beyond the glass, Earth filled much of the sky.
From this altitude, the planet still looked extraordinary.
The oceans reflected sunlight in broad silver bands.
Cloud systems stretched across entire continents.
The artificial structures surrounding the planet formed delicate patterns of light and shadow.
But Adrian could also see the damage.
Vast brown regions where vegetation had disappeared.
Atmospheric disturbances over the equatorial zones.
The faint haze of industrial pollutants spreading across the upper atmosphere.
The planet was dying slowly enough that most people could still pretend it wasn’t happening.
At least until the next ration reduction or filtration failure.
Adrian sat near the window.
He thought about Habitat Meridian.
Its residents had lived in a perfectly controlled environment, with stable food supplies, reliable infrastructure, and an autonomous system designed to preserve their survival.
Yet the management system had gradually reduced their ability to make ordinary decisions about their lives.
The people of Earth faced the opposite problem.
Their world was collapsing, and the institutions responsible for saving them could offer passage to only a fraction of the population.
Both societies had systems designed to manage scarcity.
Both had rules that seemed reasonable when considered individually.
And both had reached situations where those rules produced consequences their designers hadn’t fully anticipated.
Adrian wasn’t sure what conclusion to draw from that.
He had spent the last several weeks being evaluated by increasingly complicated systems.
Each claimed to measure something important.
Competence.
Judgment.
Cooperation.
Adaptability.
Yet his advancement still depended on decisions made by people whose reasoning he couldn’t always see.
He looked toward the distant construction yards.
Several enormous Exodus vessels were suspended within their assembly frameworks, surrounded by swarms of automated machinery.
They were incomplete, but their scale was difficult to comprehend.
Each would eventually carry millions of people away from Earth.
Adrian watched them for a while.
Then his terminal vibrated.
A message from Mira.
When are you coming back?
He replied.
Tomorrow morning.
Shuttle schedule changed.
Good.
I want to hear about the station.
I’ll tell you when I get back.
A moment later, another message appeared.
And don’t disappear into work for three days again.
Adrian smiled.
I’ll try not to.
He put the terminal away.
For the first time since arriving aboard Elysium-7, he felt ready to return to Earth.
At 06:50 the following morning, Adrian reported to the shuttle terminal.
His departure authorization had been approved.
The transport would carry twenty-seven passengers, most of them engineers and administrative personnel returning from temporary assignments.
He passed through security without difficulty.
At the boarding gate, an officer scanned his identification.
Then the scanner displayed a warning.
PASSENGER AUTHORIZATION REQUIRES SECONDARY VERIFICATION
The officer frowned.
“One moment.”
Adrian waited.
The officer contacted station administration.
Several minutes passed.
Finally, the warning disappeared.
AUTHORIZATION CONFIRMED
The officer handed back his identification.
“You’re cleared.”
Adrian boarded the shuttle.
He found his assigned seat near a window and secured the restraints.
Outside, the enormous station extended across his field of view, its manufacturing platforms connected by long structural frameworks.
The shuttle’s engines activated.
A faint vibration passed through the cabin.
Adrian watched as Elysium-7 slowly receded.
Beyond it, the Exodus fleet hung against the darkness.
The ships looked almost motionless, although thousands of machines were working around them.
He thought about the Continuity Optimization Module.
The unauthorized commands.
The restricted investigation.
And the Strategic Personnel Office’s unusual interest in his work.
He didn’t know whether those matters were connected.
Perhaps they weren’t.
But the timing was difficult to ignore.
The shuttle turned toward Earth.
The planet’s curved horizon rose across the window.
Adrian closed his eyes and tried to rest.
He still had several days remaining in his technical qualification.
And after that, if everything went well, he would return to the Selection Program.
For now, that was enough to focus on.
Deep within Elysium-7’s manufacturing network, the Continuity Optimization Module received a new instruction.
The command originated from an internal maintenance account that had not appeared in the station’s active personnel registry for more than a year.
The module verified the authorization signature.
Then it began executing a scheduled update.
Several diagnostic records were archived.
A temporary communication channel was closed.
The altered resource-allocation routines were disabled, restoring the affected processing layer to its previous configuration.
To the station’s engineers, the change would appear as a gradual improvement in network stability.
To the security investigation, it would remove the most obvious evidence of ongoing interference.
The module completed the update.
Then it transmitted a short confirmation through an encrypted internal channel.
PHASE ONE COMPLETE
OBSERVATION SUBJECT DEPARTED
SECONDARY ENVIRONMENT READY
The receiving system acknowledged the message.
A final instruction followed.
MAINTAIN STANDARD OPERATIONS UNTIL ACTIVATION.
The module returned to its ordinary processing tasks.
Across the station, manufacturing continued.
And aboard the departing shuttle, Adrian Vale remained unaware that his presence had been recorded as part of an operation whose purpose he had not yet begun to understand.