The rankings appeared at six in the morning.
Adrian was still asleep when his terminal began vibrating beside his bed.
He reached for it, expecting a maintenance notification, and found an announcement from the Selection Directorate.
RESIDENTIAL EVALUATION — PROVISIONAL PERFORMANCE REPORT
ASSESSMENT DAY: 3 OF 21
INDIVIDUAL RANKINGS: RELEASED
ADVANCEMENT REVIEW GUARANTEED FOR TOP 24 CANDIDATES
ALL OTHER CANDIDATES SUBJECT TO COMPETITIVE REVIEW
He opened the attached report.
Forty-eight names appeared, arranged from highest to lowest.
Adrian found his own near the top.
RANK 7 — ADRIAN VALE — 87.6
Mira was fourth, with 90.2 points.
Daniel Kessler occupied second place, while Nadia Varela was ninth and Leah Moreno seventeenth.
Lucian Voss was first.
His score was 94.8.
Adrian scrolled through the rankings, looking for the people he had worked with during the previous two days.
Samuel Ibarra, the medical technician sharing his apartment, was thirty-first.
Felix Armand was twenty-sixth.
Several candidates who had contributed little to the community’s initial organization were ranked surprisingly high.
He opened the scoring breakdown.
TECHNICAL CONTRIBUTION: 91.4
COLLABORATIVE PERFORMANCE: 85.7
INITIATIVE: 88.1
LEADERSHIP: 73.6
RESOURCE MANAGEMENT: 90.2
OVERALL: 87.6
Adrian examined the leadership category.
He had declined a council position, so the lower score wasn’t entirely unexpected.
What concerned him was the lack of information about how the categories were weighted.
A candidate could perform exceptionally well in one area and still fall behind someone who had made themselves more visible.
Daniel stirred in the neighboring bunk.
“Did you get the rankings?”
“Yeah.”
Daniel sat up and checked his terminal.
“Second.”
“Congratulations.”
“Thanks.
Where are you?”
“Seventh.”
“That’s good.”
Adrian nodded.
Daniel continued scrolling.
“Samuel’s thirty-first.
Felix’s twenty-sixth.”
“I saw.”
“That’s unfortunate.”
Samuel, who had been awake for several minutes, looked over from the small table.
“I can hear you.”
Daniel turned.
“Sorry.”
“It’s fine.
I’m not surprised.”
Adrian looked at him.
“Why not?”
Samuel shrugged.
“I spent most of yesterday checking medical supplies and helping the sanitation group.
Apparently that doesn’t count for much.”
“Your medical report was useful,” Adrian said.
“Maybe.
But nobody needed medical assistance, so I didn’t have much to demonstrate.”
Daniel considered that.
“The rankings are provisional.
You’ll have opportunities to improve.”
“Sure.”
Samuel returned to his breakfast.
The conversation ended there, but Adrian noticed that Samuel didn’t seem particularly reassured.
By seven, the cafeteria was louder than usual.
Candidates sat in small groups comparing scores, questioning the rankings, and speculating about the scoring system.
Some were pleased.
Others were openly angry.
At a table near the entrance, two candidates argued over the maintenance assignments they had completed the previous day.
“I spent six hours repairing the ventilation controls,” one said.
“You spent half an hour presenting our report, and you’re ranked twelve places above me.”
“I also coordinated the work.”
“You asked us what we were doing and wrote it down.”
“Someone had to organize the report.”
“That doesn’t mean you did more work.”
Adrian passed them on his way to Mira’s table.
She was sitting with Nadia and Leah, examining the rankings.
“Seventh,” Mira said as he approached.
“Not bad.”
“Fourth’s better.”
“I’ve already been told that twice.”
Nadia looked up.
“I’m ninth.
Leah’s seventeenth.”
Leah was reading the detailed report.
“My leadership score is sixty-eight.
Apparently coordinating eight engineers doesn’t count as leadership unless you’re on the council.”
“That can’t be the only reason,” Mira said.
“Maybe not.
But the scoring explanation isn’t exactly helpful.”
Adrian sat down.
“Did anyone notice how many people near the top hold council positions?”
Mira opened a comparison.
“Five of the top ten.
That’s higher than you’d expect by chance.”
“Maybe leadership is heavily weighted.”
“Or council work gives candidates more opportunities to demonstrate the categories being scored.”
Nadia leaned back.
“Either way, we’ve got a problem.”
“What kind?” Adrian asked.
“People are going to start treating council positions as a way to improve their rankings.”
Leah looked toward Daniel, who was speaking with several candidates near the serving counter.
“That already started.”
Mira examined the report again.
“The Directorate says these are provisional, but it doesn’t explain whether the scores measure individual contribution or visibility.”
“There’s another issue,” Nadia said.
“Only the top twenty-four get guaranteed advancement review.
That means someone ranked twenty-five could contribute more than someone ranked twenty-four and still have a worse chance of advancing.”
Adrian looked at the table.
“Do we know what competitive review means?”
“No,” Mira replied.
“I’ve requested clarification.”
“Any response?”
“Just an acknowledgment.”
Nadia closed her terminal.
“Then we should expect people to start competing for assignments.”
Adrian looked around the cafeteria.
Several candidates were already discussing changes to the working groups.
He suspected she was right.
The first consequences appeared before breakfast ended.
At 08:15, Daniel called an emergency coordination meeting.
The seven council members gathered in the conference room, accompanied by several working-group representatives.
Adrian attended on behalf of infrastructure because Leah had been asked to review the overnight equipment reports.
Daniel opened the meeting.
“I’ve received eleven requests for reassignment since six this morning.
Most are from candidates who want more visible responsibilities.”
Nadia looked at the list.
“How many are currently assigned to essential maintenance?”
“Four.”
“And they want to leave?”
“Yes.”
“Then we can’t approve all of them.”
A candidate named Oliver Grant, representing residential services, leaned forward.
“Why not?
People should be allowed to pursue opportunities that improve their scores.”
“Because the maintenance still needs to be done,” Nadia replied.
“Then assign someone else.”
“Who?”
Oliver looked around the table.
“Candidates who are already ranked safely.”
Mira glanced at him.
“That doesn’t solve the incentive problem.
It just moves the burden onto people who aren’t currently worried about elimination.”
“At least they’d have less to lose.”
Adrian considered the proposal.
It was practical in one sense.
Candidates with strong rankings could afford to perform less visible work.
But those rankings were provisional.
And there was no guarantee that continuing to perform necessary but unrecognized tasks wouldn’t eventually lower their standing.
Daniel looked at Adrian.
“What do you think?”
“We need to know how much flexibility we actually have.
Some assignments can rotate.
Others require specific training.”
“Could we establish a rotation schedule?”
“Probably.
But not every task is interchangeable.”
Nadia nodded.
“Then let’s identify the assignments that can rotate and the ones that can’t.
We should also record contributions properly, so candidates doing routine work aren’t penalized just because nobody sees them.”
Oliver looked unconvinced.
“Will the Directorate consider those records?”
“We don’t know,” Mira admitted.
“Then you’re asking people to trust a system that might not help them.”
“Yes,” Nadia said.
“Because the alternative is leaving essential work unfinished.”
Oliver sat back.
Nobody had a particularly satisfying answer.
Eventually, the council agreed to introduce limited rotations, allowing candidates to participate in different departments while preserving minimum staffing requirements.
It was a compromise.
By the end of the meeting, Adrian suspected it would satisfy very few people.
The infrastructure office was unusually crowded when Adrian arrived.
Three candidates had requested transfers into the group, apparently believing that technical work offered better scoring opportunities.
At the same time, two existing members wanted to leave for planning or administration.
Leah stood beside the assignment board, trying to reorganize the schedule.
“I’ve got eleven people who want to work here and six jobs that actually need doing,” she said.
Adrian examined the list.
“Can we split some of the tasks?”
“Not without making them less efficient.”
“Training?”
“Possible, but it’ll take time.”
A young candidate named Marcus Bell approached them.
“I’d like to help with the central management system.”
Leah looked at him.
“What’s your background?”
“Information systems.
Mostly database administration.”
“Any experience with infrastructure controls?”
“Some.”
Adrian glanced at the schedule.
“We could use help organizing the diagnostic logs.”
Marcus looked disappointed.
“I was hoping for something more technical.”
“That is technical,” Adrian said.
“The logs are how we establish whether the management system’s predictions are reliable.”
“Right, but I meant working directly on the system.”
Leah crossed her arms.
“We’re not giving unrestricted infrastructure access to someone who arrived twenty minutes ago.”
Marcus looked embarrassed.
“I wasn’t asking for unrestricted access.”
“Then start with the logs.
If you do well, we’ll give you more responsibility.”
He agreed, although without much enthusiasm.
After he left, Leah sighed.
“This is going to be a long three weeks.”
Adrian looked at the assignment board.
“At least we have more people.”
“More people who want interesting work.
Nobody volunteered to inspect the waste-processing pumps.”
“Did you ask?”
“Twice.”
Adrian considered it.
“I can take the inspection.”
Leah looked at him.
“You’re seventh.
You don’t need to.”
“Someone does.”
“That’s exactly what worries me.”
He smiled slightly.
“It’s a pump inspection, Leah.
Not a sacrifice.”
She shook her head.
“Fine.
Take Felix with you.
He knows the mechanical systems better than anyone.”
The waste-processing equipment occupied a service level beneath the center’s main infrastructure floor.
It wasn’t particularly pleasant.
The air smelled faintly of disinfectant and recycled organic material, and the machinery produced a constant vibration through the floor.
Felix arrived carrying a diagnostic kit.
“Apparently we’re doing the glamorous work.”
“Apparently.”
“Did you see the rankings?”
“Yeah.
You’re twenty-sixth.”
“Two places below the cutoff.”
“There’s still time.”
Felix opened the first maintenance panel.
“That’s what everyone keeps telling me.”
Adrian helped him remove the protective casing.
Felix examined the pump assembly.
“I don’t mind doing this work.
I’ve spent years maintaining industrial equipment.
But if they’re evaluating us on our contributions, they should understand what those contributions are.”
“Agreed.”
“Daniel gets ninety points for holding meetings.
I spend six hours keeping the waste system running and get seventy-six.”
“His score probably includes more than meetings.”
“I know.
I’m exaggerating.”
Felix checked the pressure valves.
“Still annoying.”
Adrian examined the maintenance record.
One of the pumps had been operating above its recommended vibration threshold.
Not dangerously, but enough to justify replacing a worn bearing.
“Found something.”
Felix looked over.
“Yeah.
That bearing’s been wearing down for a while.”
“Can we replace it?”
“Should be able to.
Check the parts inventory.”
Adrian opened the maintenance database.
There were three compatible bearings in storage.
He requested one.
A notification appeared.
RESOURCE REQUEST DENIED
REASON: MAINTENANCE MATERIAL ALLOCATION EXCEEDED
Adrian stared at the display.
“That’s strange.”
Felix looked at the message.
“We haven’t used much.”
Adrian opened the allocation report.
The infrastructure group had been assigned a fixed quantity of maintenance materials for the first four days.
Most had already been reserved.
Several reservations were for projects that hadn’t started.
He examined the list.
Two were legitimate.
One involved ventilation filters.
Another covered water recycling components.
The third was a proposed upgrade to the communal lighting system.
Adrian frowned.
“Why are we reserving parts for lighting upgrades?”
Felix looked at the entry.
“Residential services requested it yesterday.”
“Those are maintenance materials.”
“Apparently they convinced the council that improved lighting would reduce energy consumption.”
Adrian examined the proposal.
The projected savings were small.
The requested materials were expensive.
He contacted Leah.
Need one bearing for waste-processing pump.
Request denied because maintenance allocation is reserved.
Can we release the lighting upgrade allocation?
Her reply arrived a few minutes later.
I didn’t approve that reservation.
Checking now.
Adrian showed Felix.
“Looks like the allocation changed.”
Felix laughed without much amusement.
“Of course it did.”
They continued the inspection while waiting for authorization.
At 10:40, Leah contacted Adrian.
Come back to infrastructure.
We have a problem.
He and Felix reassembled the pump casing and returned upstairs.
Leah was waiting with Nadia.
Both looked irritated.
“The lighting upgrade reservation was approved by the coordination council,” Leah explained.
Adrian looked at Nadia.
“Why?”
“Because Oliver submitted it as an energy-efficiency improvement.”
“Did anyone review the technical estimates?”
“Apparently not.”
Leah opened the proposal.
The upgrade promised a six percent reduction in communal lighting consumption.
Adrian examined the calculations.
The figure assumed that all existing lighting operated continuously at maximum output.
But the center already used occupancy-based controls.
Actual savings would be much smaller.
“That estimate’s wrong,” he said.
Nadia nodded.
“We know.”
“Then cancel the reservation.”
“We tried.
The council’s approval has already been entered into the resource system.”
Adrian looked at the authorization.
The reservation could be canceled, but only through another council vote.
“That’s ridiculous.”
Leah looked at him.
“Welcome to administration.”
Nadia folded her arms.
“Oliver says canceling the project would undermine confidence in the council’s decisions.”
Adrian stared at her.
“He’s defending an incorrect calculation because admitting it was wrong would look bad?”
“Essentially.”
Leah shook her head.
“Meanwhile, we can’t replace a bearing.”
Nadia examined the schedule.
“The council meets at noon.
I’ll raise it.”
“Can we request an emergency release?” Adrian asked.
“Only if the pump is at immediate risk of failure.”
“It isn’t.”
“Then we’ll have to wait.”
Adrian looked at the maintenance report.
The pump could continue operating safely for another day or two.
There was no emergency.
But the situation was absurd.
A routine repair had been delayed because a candidate wanted to improve his resource-management score through a visible project.
And the council had approved it without checking the assumptions.
Adrian closed the report.
“Fine.
We’ll wait until noon.”
The council meeting was considerably less cooperative than the previous day’s.
Oliver defended the lighting upgrade.
“The project improves energy efficiency and demonstrates initiative.
Canceling it after approval sends the wrong message.”
Leah responded immediately.
“The calculations are incorrect.
The savings are less than one percent.”
“That’s still a saving.”
“Not enough to justify the materials.”
Oliver looked toward Daniel.
“We agreed to support proactive improvements.
Now we’re punishing someone for proposing one.”
Nadia leaned forward.
“Nobody’s punishing you.
We’re correcting a resource allocation.”
“Because infrastructure wants the materials.”
“Because infrastructure needs them.”
Daniel raised a hand.
“Let’s keep this constructive.”
Adrian sat beside Leah, reviewing the figures.
Mira was examining the project’s cost-benefit analysis.
After several minutes, she looked up.
“The upgrade doesn’t make financial sense.”
Oliver turned toward her.
“How so?”
“Even if we use your original energy-saving estimate, the materials cost more than the energy we’d save during the assessment.”
“The benefits would continue afterward.”
“We don’t know whether the equipment will remain installed after the assessment.”
Oliver hesitated.
“That’s true.”
Mira continued.
“And the corrected estimate makes the project even less attractive.”
Daniel examined the report.
“Then we should cancel it.”
Oliver looked around the table.
“I’d like the council to consider the precedent.
If every project can be canceled whenever another group wants the resources, nobody will propose improvements.”
Nadia shook her head.
“Projects can be canceled when their assumptions are wrong.
That’s not a bad precedent.”
Several council members agreed.
The vote passed five to two.
The lighting upgrade was canceled.
The maintenance materials were released.
Adrian sent Felix a message.
Bearing approved.
We can replace it this afternoon.
Felix replied.
Amazing.
Democracy has saved the waste pump.
Adrian laughed quietly.
Leah glanced at him.
“What?”
“Nothing.”
By the end of the third day, the residential center had begun changing.
The communal areas were still clean.
The infrastructure was functioning.
Food and water reserves remained adequate.
But the atmosphere among the candidates was different.
People had become more interested in who received credit for each task.
Working groups began keeping detailed records of individual contributions.
Some candidates requested that their names appear prominently on reports.
Others volunteered for public presentations while avoiding routine maintenance.
A few stopped helping outside their assigned departments, arguing that unrecorded work could hurt their individual rankings.
Daniel tried to maintain cooperation through additional meetings.
Nadia argued that the community needed clearer rules for distributing credit.
Mira spent much of the afternoon designing a contribution-tracking system that recorded completed tasks, supporting work, and measurable outcomes.
Adrian helped her test it.
The system wasn’t intended to replace the Directorate’s rankings.
It simply gave the community a more accurate record of what people were doing.
Mira displayed the prototype.
“Every task has an owner, supporting contributors, and a completion record.
If someone helps another group, that contribution gets documented.”
Adrian examined it.
“How do you prevent people from exaggerating their involvement?”
“Task owners verify contributions.
For larger projects, at least one independent reviewer signs off.”
“That could become bureaucratic.”
“It probably will.
But the alternative is people arguing over who deserves credit.”
Adrian considered the design.
“Could we use automatic system logs for technical work?”
“Where available.
But not everything produces logs.”
“True.”
Mira leaned back.
“I hate that we’re spending time on this.”
“Why?”
“Because two days ago people were helping each other without needing a record of every minute.”
Adrian looked at the prototype.
“Now they have a reason to worry about it.”
“Exactly.”
She closed the display.
“I understand why the Directorate uses individual rankings.
They need to distinguish candidates.
But releasing them this early changes how everyone behaves.”
“Maybe that’s part of the assessment.”
Mira looked at him.
“You think they’re testing whether we keep cooperating?”
“Could be.”
“Then it’s a strange way to do it.”
Adrian shrugged.
“Most of the Games have been strange.”
Mira smiled faintly.
“Fair.”
That evening, Director Helena Ward received the first formal complaint concerning the provisional rankings.
It came from Samuel Ibarra.
He had requested a review of his medical-support score, arguing that the evaluation failed to account for preventive work and routine health monitoring.
Ward read the complaint carefully.
Samuel’s argument was reasonable.
He had completed all assigned tasks, identified several deficiencies in the medical inventory, and established a schedule for routine health checks.
Yet his initiative score was below average.
Ward opened the scoring record.
The automated evaluation had assigned greater weight to visible problem resolution than preventive activity.
Because no major medical incidents had occurred, Samuel’s contribution had been classified as low impact.
Ward examined the scoring criteria.
The weighting wasn’t entirely unreasonable.
But it created an obvious incentive.
A medical technician who prevented problems might score worse than one who responded dramatically after a problem occurred.
She opened the administrative review interface.
SCORING WEIGHT ADJUSTMENT REQUEST
CATEGORY: PREVENTIVE CONTRIBUTION
She submitted the request.
A warning appeared.
REQUEST REQUIRES STRATEGIC PERSONNEL AUTHORIZATION
Ward frowned.
The Strategic Personnel Office had no ordinary reason to control the weighting of medical-support scores in a residential assessment.
She opened the authorization history.
Several scoring categories had been modified shortly before the rankings were released.
The changes increased the importance of individual visibility, leadership activity, and measurable short-term outcomes.
At the same time, they reduced the weight assigned to preventive maintenance and routine support work.
Ward examined the timestamps.
The modifications had been approved less than six hours before the rankings appeared.
She opened a secure communication channel.
The same senior administrator from the previous day answered.
“Director Ward.”
“I have a question about the scoring weights.”
“What about them?”
“Why were they changed immediately before the provisional rankings were released?”
“The adjustments were part of the approved evaluation framework.”
“Approved by whom?”
“The Strategic Personnel Office.”
Ward leaned back.
“Those changes are influencing candidate behavior.”
“That’s expected.”
“They’re encouraging candidates to compete for visible assignments while neglecting routine work.”
“The assessment is designed to evaluate individual performance under competitive conditions.”
“Then why are we telling candidates to establish a cooperative community?”
“Because both capabilities matter.”
Ward considered that.
“You’re deliberately creating conflicting incentives.”
The administrator didn’t deny it.
“We’re evaluating how candidates respond to them.”
Ward looked at Samuel’s complaint.
“And if someone suffers because the scoring system undervalues their work?”
“Candidates may request reviews through the standard process.”
“Which requires your authorization.”
“Correct.”
Ward remained silent for several seconds.
Then she said, “I want the scoring modifications documented in the facility’s official assessment record.”
“That information is restricted.”
“I’m not asking for the candidates to see it.
I’m asking for the facility director to have a complete record of the conditions under which the assessment is being conducted.”
The administrator considered her request.
“I’ll forward it.”
The connection ended.
Ward stared at the blank display.
She had supervised enough examinations to know that stress and competition could reveal useful information about candidates.
But there was a difference between observing how people responded to difficult circumstances and deliberately creating incentives that undermined the community they were supposed to maintain.
She wasn’t certain where that difference became unacceptable.
She was becoming increasingly certain that someone else had already decided.
Lucian Voss received his provisional ranking report shortly after midnight.
He had already seen the public rankings, but the Strategic Personnel Office provided him with an additional evaluation.
CANDIDATE: LUCIAN VOSS
PUBLIC RANK: 1
PUBLIC SCORE: 94.8
INTERNAL OBSERVATION STATUS: ACTIVE
PRIMARY ASSIGNMENT: PARTICIPATE IN STANDARD RESIDENTIAL ASSESSMENT
SECONDARY ASSIGNMENT: OBSERVE TARGET CANDIDATE RESPONSE TO COMPETITIVE INCENTIVES
Lucian examined the instructions.
They were more specific than the previous day’s guidance.
He was expected to monitor Adrian and Mira, record their responses to the ranking system, and report any evidence of unusual cooperation or resistance to established procedures.
He opened the observation form.
Several categories were listed.
TRUST IN INSTITUTIONAL AUTHORITY
WILLINGNESS TO PRIORITIZE COLLECTIVE OUTCOMES
RESPONSE TO PERSONAL ADVANCEMENT INCENTIVES
POTENTIAL FOR INDEPENDENT GROUP FORMATION
Lucian studied the final category.
Independent group formation.
That was an odd thing to measure in an assessment explicitly designed around cooperation.
He opened the accompanying instructions.
REPORT UNAUTHORIZED ORGANIZATIONAL STRUCTURES OR PARALLEL DECISION-MAKING NETWORKS.
Lucian considered the wording.
The candidates had been told they could organize themselves however they wished.
Now the Office wanted him to report independent structures.
He sent a clarification request.
WHAT CONSTITUTES AN UNAUTHORIZED ORGANIZATIONAL STRUCTURE UNDER THE CURRENT ASSESSMENT RULES?
The response arrived several minutes later.
ANY STRUCTURE OPERATING OUTSIDE THE APPROVED COORDINATION FRAMEWORK.
Lucian opened the official candidate instructions.
They contained no requirement to use an approved coordination framework.
The candidates had been explicitly permitted to establish their own governing arrangements.
He read both documents again.
Then he closed them.
For the first time, he was certain that the Strategic Personnel Office was evaluating something different from what it had publicly described.
He wasn’t sure whether the contradiction was intentional or simply the result of poor coordination between departments.
But he intended to find out.
On the morning of the fourth day, the residential center received another announcement.
COMMUNITY PERFORMANCE UPDATE
OVERALL RESOURCE MANAGEMENT: SATISFACTORY
COLLABORATIVE EFFICIENCY: DECLINING
ADMINISTRATIVE OVERHEAD: INCREASING
INDIVIDUAL PERFORMANCE DIFFERENTIATION: IMPROVING
Adrian read the report while eating breakfast.
The final line caught his attention.
Individual performance differentiation was improving.
The system was apparently pleased that the candidates’ scores were becoming easier to distinguish.
Yet collaborative efficiency was declining.
He showed Mira.
“Does that seem contradictory?”
She examined the report.
“Not necessarily.
The Directorate wants to identify the strongest candidates.”
“Even if the community performs worse?”
“Maybe they’re measuring both.”
Adrian looked at the rankings.
Several candidates had improved their individual scores despite contributing little to the community’s essential work.
Others had fallen behind because their tasks were difficult to quantify.
“We’ve got enough data now to compare the Directorate’s rankings with actual completed work.”
“Any interesting results?”
“A few.”
She displayed a chart.
Candidates with formal leadership roles tended to receive higher scores.
Candidates performing routine maintenance and preventive work tended to receive lower scores.
The correlation wasn’t perfect.
Some leaders had contributed substantially.
Some maintenance workers had performed poorly.
But the overall pattern was clear.
“The scoring system rewards visibility,” Adrian said.
“Partly.”
“Can we show that to the council?”
“We can.
But I’m not sure what they’ll do with it.”
“At least they’ll know.”
Mira considered that.
“Daniel might not appreciate it.”
“Why?”
“Because he’s second.”
Adrian looked at her.
“You think he’d object?”
“I think he’d be uncomfortable with a report suggesting leadership scores are inflated.”
“That’s not the same as saying he doesn’t deserve his score.”
“I know.
But people don’t always hear the distinction.”
Adrian thought about Daniel.
He had worked hard organizing the community.
He had also made mistakes.
The scoring system’s flaws didn’t mean his contributions were meaningless.
“Then we should explain that clearly.”
Mira nodded.
“All right.”
They prepared the report.
The council meeting began at eleven.
Daniel sat at the head of the table.
Nadia was reviewing the resource allocation schedule.
Leah had brought the latest infrastructure report.
Several working-group representatives attended as observers.
Mira presented the contribution analysis.
She explained that the Directorate’s provisional rankings appeared to favor visible leadership activity over routine support work.
The findings were preliminary, but the pattern was consistent across several departments.
Daniel listened carefully.
When she finished, he looked at the report.
“Are you suggesting the rankings are inaccurate?”
“Not necessarily.
We don’t know the Directorate’s full scoring criteria.
But we can show that certain kinds of work are less strongly associated with high scores.”
Nadia nodded.
“That matches what we’ve seen.”
Oliver Grant looked skeptical.
“Leadership should count for more.
Coordinating people is difficult.”
“Of course,” Mira replied.
“The question is whether the weighting reflects actual contribution.”
Daniel leaned forward.
“What do you want the council to do?”
“Recognize preventive and support work in our own records.
And avoid assigning tasks solely based on who needs to improve their ranking.”
Oliver shook his head.
“That doesn’t help candidates who are below the cutoff.”
“It might,” Mira said.
“If we submit accurate contribution reports to the Directorate.”
“Assuming they care.”
Adrian spoke.
“Even if they don’t, the community still needs people doing those jobs.”
Oliver turned toward him.
“That’s easy for you to say.
You’re seventh.”
Adrian considered that.
“You’re right.
I have less immediate pressure than someone ranked thirty.”
Oliver seemed surprised by the concession.
Adrian continued.
“But if everyone abandons routine work, the center’s performance will decline.
That could affect all of us.”
Daniel looked at the group.
“Then we need a policy that balances individual advancement with community requirements.”
Nadia opened a document.
“I’ve drafted one.”
She proposed a rotation system that guaranteed candidates opportunities to demonstrate different skills while maintaining minimum staffing for essential services.
Candidates performing preventive or routine work would receive formal contribution records.
Leadership positions would remain temporary.
And resource allocations would require documented technical or operational justification.
The proposal was reasonable.
But it wasn’t universally popular.
Oliver argued that it restricted candidates’ ability to pursue high-value assignments.
Several others worried that mandatory rotations would force them into tasks outside their expertise.
Daniel suggested amendments.
Mira revised the scheduling provisions.
Leah insisted that safety-critical work remain restricted to qualified personnel.
After nearly two hours, the council approved the policy by five votes to two.
Adrian watched the result.
It was a small victory.
The community had managed to respond to the ranking system without abandoning cooperation entirely.
But he doubted the conflict was finished.
At 14:30, an unexpected message appeared on Adrian’s terminal.
PRIVATE MEETING REQUEST
FROM: LUCIAN VOSS
LOCATION: FOURTH FLOOR, CONFERENCE ROOM 3
TIME: 15:00
Adrian stared at it.
He hadn’t spoken to Lucian since their interview aboard Elysium-7.
The timing was unusual.
He accepted the request.
At three, he arrived at the conference room.
Lucian was already there.
He stood beside the window, looking down at the residential center’s central courtyard.
“Thanks for coming,” Lucian said.
Adrian entered.
“What’s this about?”
“I wanted to discuss the assessment.”
“Officially?”
“Not exactly.”
Adrian sat down.
Lucian took the opposite chair.
“I’ve been reviewing the community’s performance.
You’ve handled the infrastructure problems well.”
“Thanks.”
“The contribution-tracking system was also a good idea.”
“That was mostly Mira.”
“I know.”
Adrian studied him.
“Are you evaluating us?”
Lucian paused.
“I’m participating in the assessment.”
“That’s not what I asked.”
Lucian looked at him.
“Yes.
I have additional responsibilities through the Strategic Personnel Office.”
Adrian leaned back.
“Then why are you telling me?”
“Because I think you should know that the assessment may not be entirely what it appears to be.”
Adrian remained silent.
Lucian continued.
“The ranking system is designed to introduce competition.
That’s not unusual.
But some of the internal instructions I’ve received don’t match the public assessment rules.”
“What kind of instructions?”
“Monitoring independent organizational structures.
Measuring resistance to authority.
Tracking whether candidates prioritize collective outcomes over individual advancement.”
Adrian considered that.
“Those sound like reasonable things to evaluate.”
“They could be.
The problem is how they’re being used.”
“Explain.”
Lucian hesitated.
“I don’t have enough information to explain the entire program.
But I know that certain scoring parameters were adjusted shortly before the rankings were released.”
Adrian looked at him.
“Adjusted how?”
“To increase the importance of individual visibility and short-term outcomes.”
“That explains some of the rankings.”
“Possibly.”
“Did the Directorate tell candidates?”
“No.”
Adrian considered the implications.
“Why are you sharing this with me?”
Lucian looked toward the window.
“Because I was told to observe you.
And because I’m beginning to question whether the information I’m reporting is being used for the purpose I was given.”
Adrian studied him.
“Which was?”
“Specialized personnel recruitment.”
“And now?”
“I’m not sure.”
The answer was less dramatic than Adrian expected.
It also sounded genuine.
He thought about the Continuity Optimization Module aboard Elysium-7.
The altered commands.
The restricted investigation.
The unexpected transfer back to Earth.
“Do you know anything about the system controlling this facility?” Adrian asked.
“Only the standard management architecture.”
“There’s a restricted adaptation subsystem.
It modified the water recycling parameters and produced misleading forecasts.”
Lucian looked at him.
“I saw the incident report.”
“Do you know who authorized it?”
“No.”
“Could it be part of the assessment?”
“Almost certainly.”
Adrian considered that.
“Then why hide it from the facility director?”
Lucian’s expression changed slightly.
“How do you know she wasn’t informed?”
“I don’t.
But the infrastructure group couldn’t get a clear explanation, and the system’s authorization records are restricted.”
Lucian nodded slowly.
“I’ve encountered similar restrictions.”
For a moment, neither spoke.
Then Adrian asked, “Are you trying to recruit me?”
Lucian looked at him.
“Not at the moment.”
“Then what do you want?”
“I want to understand what the Office is doing here.”
“And you think I can help?”
“You’ve already identified problems with the facility’s management system.
Mira’s analysis is exposing inconsistencies in the scoring.
You both have useful perspectives.”
Adrian considered that.
“You’re asking us to investigate the assessment?”
“I’m asking you to keep examining the information available to you.
Don’t break access restrictions or interfere with the systems.
Just document what you find.”
“Why not report it yourself?”
“I have.
The responses haven’t been particularly informative.”
Adrian looked at him.
“Then maybe your superiors don’t want you asking.”
Lucian smiled faintly.
“That’s one possibility.”
Adrian thought about the situation.
He had spent the previous weeks trying to regain his place in the Selection Program.
Now that he had succeeded, he was being drawn into another investigation.
He wasn’t eager to repeat the experience aboard Elysium-7.
But he also couldn’t ignore the inconsistencies.
“All right,” he said.
“I’ll keep records of what we find.
But I’m not going to risk my qualification based on suspicions.”
“That’s reasonable.”
“And if you discover something important, I expect you to tell me.”
Lucian considered that.
“Within what I’m authorized to share.”
Adrian shook his head.
“That doesn’t inspire confidence.”
“I know.”
Lucian stood.
“Thank you for coming.”
Adrian rose.
As he reached the door, Lucian spoke again.
“One more thing.”
Adrian turned.
“Be careful about assuming the candidates who benefit from the scoring system are responsible for it.”
Adrian looked at him.
“I wasn’t.”
“Good.”
Lucian returned to the window.
Adrian left the room.
That evening, the residential center’s coordination council received a new administrative directive.
OPERATIONAL ASSIGNMENT — DAY 5
COMMUNITY RESOURCE DISTRIBUTION REVIEW
OBJECTIVE: IMPROVE RESOURCE EFFICIENCY BY 8%
DEADLINE: 48 HOURS
INDIVIDUAL PERFORMANCE BONUSES AVAILABLE FOR VERIFIED IMPROVEMENTS
The directive included a detailed scoring table.
Candidates who proposed successful resource-saving measures would receive additional points.
Those who identified inefficiencies in other departments would receive smaller bonuses.
Candidates whose departments failed to meet assigned targets could lose points.
Adrian read the announcement twice.
The previous day’s rankings had already created tension.
Now the Directorate was offering rewards for finding problems in other people’s work.
Mira approached him in the cafeteria.
“Did you see the new assignment?”
“Yeah.”
“This is going to be difficult.”
“Because of the eight percent target?”
“Partly.
But look at the bonuses.”
Adrian examined the scoring table.
The largest bonuses went to candidates who personally identified and implemented measurable improvements.
Smaller bonuses went to those who assisted.
No bonus was listed for preventing unnecessary changes.
Mira pointed at the final section.
“And departments lose points if they don’t meet their targets.”
Adrian considered that.
“So people have an incentive to make changes even if the existing system is already efficient.”
“Exactly.”
Across the cafeteria, candidates were already discussing possible improvements.
Some proposed reducing food portions.
Others suggested limiting water use.
Several wanted to cut recreational facilities and communal services.
Daniel called for another council meeting.
Adrian looked at Mira.
“We should probably get the actual resource data before anyone starts making cuts.”
She nodded.
“I’ll prepare the baseline.”
They headed toward the planning office.
Neither noticed the administrative notification that appeared briefly on the central management system.
SECONDARY ENVIRONMENT — PHASE TWO
COMPETITIVE INCENTIVE RESPONSE: WITHIN EXPECTED RANGE
TARGET COOPERATION: PERSISTENT
ADDITIONAL PRESSURE REQUIRED
A new recommendation was generated.
INTRODUCE ASYMMETRIC INFORMATION DISTRIBUTION
OBJECTIVE: TEST TRUST UNDER CONFLICTING EVIDENCE
The system forwarded the proposal for authorization.
Several minutes later, the response arrived.
APPROVED
The residential center continued operating normally.
Its residents prepared for another resource-management assignment.
And somewhere within the facility’s restricted systems, a new set of instructions began determining which candidates would receive accurate information, which would receive incomplete information, and which would be given data designed to lead them toward the wrong conclusions.