The entrance to Residential Evaluation Center 14 looked nothing like Adrian had expected.
There were no examination halls, rows of testing terminals, or security officers directing candidates toward individual assessment rooms.
Instead, the building resembled one of New Geneva’s better residential complexes, with broad windows, landscaped courtyards, and a central atrium rising through six floors.
The surrounding neighborhood was considerably less impressive.
Two neighboring towers had been abandoned, their windows covered with protective sheeting.
Construction barriers blocked half the pedestrian corridor, and a temporary filtration unit operated beside the center’s entrance, producing a constant mechanical hum.
Adrian arrived at 07:40, twenty minutes before the scheduled registration period.
A line of candidates had already formed outside.
Most carried small travel bags.
A few had brought larger cases, although the assignment instructions had explicitly limited personal belongings to fifteen kilograms.
Adrian joined the queue and opened the registration notice.
ADVANCED RESIDENTIAL SELECTION — STAGE THREE
DURATION: 21 DAYS
PARTICIPANTS: 48
LOCATION: RESIDENTIAL EVALUATION CENTER 14
ASSESSMENT CATEGORIES: COLLABORATION, LEADERSHIP, RESOURCE MANAGEMENT, ADAPTABILITY, INDEPENDENT JUDGMENT
The document contained little else.
He had spent the previous three days preparing for the assessment, although there wasn’t much to prepare for.
The Directorate had provided no detailed schedule, no explanation of the scoring system, and no indication of how many candidates would advance.
He had reviewed previous residential evaluations, but their formats varied considerably.
Some involved simulated emergencies.
Others required candidates to operate small communities or complete collaborative projects over extended periods.
This one could involve almost anything.
“Adrian!”
He looked toward the entrance.
Mira was approaching through the crowd, carrying a gray travel bag over one shoulder.
She wore a dark jacket and had tied her hair back, apparently expecting a long day.
“You’re early,” she said.
“So are you.”
“I wanted to avoid the registration queue.”
Adrian glanced at the line behind him.
“Didn’t quite work.”
“No.”
She joined him.
“Did you find anything useful about this place?”
“Not much.
It was converted from a residential training facility about twelve years ago.”
“I found that too.
Apparently they used to train municipal administrators here.”
“That might explain the building.”
Mira looked through the glass entrance.
“It’s nicer than I expected.”
“Better than Complex 61.”
“That’s not difficult.”
They moved forward as the registration officers began admitting candidates.
Mira lowered her voice.
“Have you seen Lucian?”
“Not yet.”
“Do you think he’ll actually participate?”
“His name’s on the list.”
“That’s not what I asked.”
Adrian considered it.
“I don’t know.
He said his evaluation work was separate from his own selection, but it still seems unusual.”
Mira glanced toward the building.
“Maybe he has to complete the same requirements as everyone else.”
“Maybe.”
She didn’t look convinced.
Neither was Adrian.
Registration took nearly an hour.
Candidates surrendered their personal communication devices, received temporary identification bands, and underwent routine medical examinations.
They were allowed to retain clothing and a limited number of personal items, but all external communications would be restricted for the duration of the assessment.
The Directorate provided replacement terminals with access to the residential center’s internal network.
Adrian examined his.
The device was ordinary enough, with messaging, scheduling, and document applications.
External network connections were disabled.
He had expected that.
What surprised him was the absence of any visible examination software.
After registration, candidates were directed into the central atrium.
The space was large enough to accommodate several hundred people.
A shallow artificial pond occupied the center, surrounded by seating areas and decorative plants.
Above them, a transparent ceiling displayed a simulated blue sky.
The contrast with the city outside was striking.
Mira looked upward.
“They spent a lot of resources making this place comfortable.”
“Probably intentional.”
“To see how we behave when we’re not miserable?”
“Wouldn’t be a bad experiment.”
They found seats near the back.
Other candidates were introducing themselves, comparing previous assessments, and discussing possible strategies.
Adrian recognized several names from the earlier Selection rankings, although he knew little about most of them.
A tall man with short brown hair was speaking animatedly to a group near the pond.
His identification band displayed the name DANIEL KESSLER.
He appeared to be in his late twenties and had the easy confidence of someone accustomed to addressing groups.
“Whatever the scoring system is,” Daniel was saying, “we should establish a cooperative structure early.
There’s no reason to waste time competing over basic necessities.”
A woman beside him crossed her arms.
“That depends on whether cooperation is actually rewarded.”
“Even if it isn’t, the center will function better if we coordinate.”
“Better for everyone, or better for the people making decisions?”
Daniel smiled.
“Hopefully both.”
Adrian listened for a moment.
Mira leaned toward him.
“He’s already campaigning.”
“Maybe he’s just organized.”
“He’s been talking to people since I arrived.”
“That doesn’t make him wrong.”
“No.
It makes him prepared.”
At 09:15, the atrium’s lighting dimmed.
A woman in a dark administrative uniform stepped onto the raised platform near the entrance.
She appeared to be in her forties, with closely cropped black hair and a professional, unhurried manner.
“Good morning.
I’m Director Helena Ward, and I’ll be supervising your residential assessment.”
The conversations stopped.
Ward waited until the room was quiet.
“Over the next twenty-one days, you will live and work together inside this facility.
Your performance will be evaluated continuously, but not every activity will be scored in the same way.”
A display appeared behind her.
RESIDENTIAL EVALUATION CENTER 14
POPULATION: 48 CANDIDATES
ASSESSMENT PERIOD: 21 DAYS
“Your first responsibility is to establish a functioning residential community.
You will manage shared facilities, organize work schedules, maintain essential services, and make collective decisions concerning resource allocation.”
Several candidates began taking notes.
Ward continued.
“You will not be assigned permanent leadership positions.
How you organize yourselves is your decision.
You may establish committees, elect representatives, or operate through direct collective agreement.”
A candidate near the front raised his hand.
“Will leadership roles receive additional points?”
Ward looked toward him.
“Leadership is one of the assessment categories.
Holding a title does not automatically demonstrate leadership.”
A few people smiled.
The candidate lowered his hand.
“Your second responsibility,” Ward said, “is to complete a series of operational assignments.
Some will be announced in advance.
Others will arise during the assessment period.”
“What kind of assignments?” another candidate asked.
“You’ll receive the relevant information when needed.”
Ward changed the display.
INITIAL COMMUNITY RESOURCES
FOOD RESERVES: 28 DAYS
WATER RESERVES: 26 DAYS
ENERGY ALLOCATION: 100% BASELINE
MEDICAL SUPPLIES: STANDARD
MAINTENANCE MATERIALS: LIMITED
Adrian examined the figures.
Twenty-eight days of food for a twenty-one-day assessment.
That provided a modest surplus.
The water reserves were slightly tighter.
Ward continued.
“The facility’s environmental and life-support systems are automated, but their operation will be influenced by the decisions you make.
You will receive access to the appropriate management interfaces.”
A candidate raised her hand.
“Are we expected to maintain the systems ourselves?”
“Not the critical components.
Qualified staff will remain responsible for essential safety functions.
However, you’ll be responsible for managing consumption, scheduling maintenance, and responding to operational problems within your authorized scope.”
That sounded reasonable.
Ward looked around the room.
“One final point.
This is not a competition in which only one candidate can succeed.
Multiple candidates may advance, and your individual evaluations will consider the effects of your decisions on the community as a whole.”
Adrian glanced at Mira.
She looked relieved.
Then Ward added, “However, advancement remains limited.
Strong collective performance does not guarantee that every participant will qualify.”
The relief disappeared.
Ward stepped away from the display.
“Your assessment begins now.
Residential assignments are available on your terminals.
You have until 18:00 to submit an initial organizational plan.”
The lights returned to normal.
For several seconds, nobody moved.
Then forty-eight terminals began chiming.
The residential assignments divided candidates into twelve apartments, each housing four people.
Adrian and Mira were assigned to different units.
Adrian’s apartment was on the third floor, shared with Daniel Kessler, a quiet medical technician named Samuel Ibarra, and an industrial maintenance specialist named Felix Armand.
Mira’s apartment was on the second floor with three other candidates, including the woman who had challenged Daniel during his earlier speech.
Her name was Nadia Varela.
Adrian learned that Nadia had previously worked in municipal resource distribution, specializing in emergency supply chains.
That explained her skepticism about informal leadership.
By 10:30, most candidates had finished moving into their rooms and returned to the atrium.
Daniel had already arranged a meeting.
“We have seven and a half hours to submit a plan,” he told the assembled candidates.
“I’d suggest dividing into working groups and assigning temporary coordinators.”
A few people agreed.
Nadia raised her hand.
“Before we start assigning coordinators, shouldn’t we decide what authority those positions have?”
Daniel nodded.
“Of course.
I’m proposing a temporary structure, not a permanent government.”
“Then let’s define it before people start making decisions.”
Another candidate spoke.
“We’re wasting time.
We can sort out the details later.”
Nadia turned toward him.
“That’s usually when the details become harder to change.”
Adrian watched the exchange.
The disagreement was ordinary enough, but he could already see how it might develop.
Daniel wanted to establish a working structure quickly.
Nadia wanted clear limits on authority.
Both approaches had advantages.
Mira leaned toward Adrian.
“This is going to take a while.”
“Probably.”
“Do you want to volunteer for infrastructure?”
“Yes.”
“Good.
I’ll take resource planning.”
They separated as Daniel began organizing the working groups.
Adrian joined seven candidates responsible for infrastructure and maintenance.
Their assigned tasks included reviewing the building’s environmental systems, estimating energy consumption, identifying maintenance requirements, and preparing emergency procedures.
A candidate named Leah Moreno volunteered to coordinate the group.
She was an electrical systems engineer, twenty-six years old, with several years of experience maintaining orbital communication equipment.
Unlike Daniel, she didn’t seem particularly interested in leading.
“Someone has to keep track of the work,” she said.
“I can do it unless somebody else wants to.”
Nobody objected.
Leah divided the tasks.
Adrian received responsibility for reviewing the center’s automated infrastructure management system.
He opened the relevant files.
The software was called HABITAT OPERATIONS MANAGEMENT SYSTEM, abbreviated HOMS.
Its interface was straightforward.
Energy distribution.
Water recycling.
Ventilation.
Waste processing.
Maintenance scheduling.
Most systems operated automatically, with candidate access limited to authorized management settings.
Adrian examined the architecture.
It was more sophisticated than he expected for a residential assessment facility.
The controllers communicated through a distributed network, and the system maintained detailed records of consumption, occupancy, and operational decisions.
He opened the configuration files.
Several sections were restricted.
That wasn’t unusual.
But one feature caught his attention.
The system maintained a secondary behavioral dataset, separate from ordinary infrastructure logs.
The dataset recorded not only resource consumption but also patterns of interaction between residents.
Meeting attendance.
Work assignments.
Decision participation.
Dispute resolution.
Adrian examined the documentation.
BEHAVIORAL METRICS COLLECTION — ENABLED
PURPOSE: RESIDENTIAL ASSESSMENT ANALYTICS
That made sense.
The Directorate needed information to evaluate candidates.
Still, the system appeared to collect considerably more detail than the introductory briefing had suggested.
Adrian checked the access permissions.
The dataset was available only to assessment administrators.
He couldn’t inspect its contents.
He made a note and continued reviewing the infrastructure systems.
By early afternoon, the first organizational disputes had emerged.
The resource planning group wanted to reduce energy consumption immediately to preserve reserves for possible emergencies.
The infrastructure group argued that the facility’s baseline allocation was sufficient and that unnecessary reductions could interfere with normal operations.
The food management group wanted additional refrigeration capacity.
The residential services group requested more energy for laundry, sanitation, and communal facilities.
None of the requests were unreasonable.
The problem was that each group was planning independently.
Mira stood beside a large display in the atrium, comparing the proposals.
“These numbers don’t match,” she said.
Daniel approached.
“Which ones?”
“Food management is assuming refrigeration consumption stays at baseline.
Residential services is requesting an additional twelve percent energy allocation.
Infrastructure is projecting only a six percent total increase.”
Daniel examined the figures.
“Can we reduce the residential request?”
“Maybe.
But we should understand what they’re using it for.”
Nadia joined them.
“They want extended laundry access and higher water-heating capacity.”
“That sounds excessive,” Daniel said.
“Not necessarily.
Forty-eight people sharing twelve apartments will use the facilities heavily.”
Mira opened another report.
“The bigger issue is that nobody’s working from the same assumptions.”
Daniel considered that.
“Then we need a centralized planning group.”
Nadia shook her head.
“We need shared data.
That’s not the same thing.”
Daniel looked at her.
“Someone still has to make the final decisions.”
“Yes.
But that doesn’t mean the same person should control all the information.”
Adrian arrived carrying the infrastructure report.
“What’s happening?”
Mira explained.
He examined the projections.
“These estimates aren’t terrible.
They’re just based on different operating schedules.”
“Can you reconcile them?” Daniel asked.
“Probably.
But I need the food and residential groups to confirm their actual requirements.”
Daniel nodded.
“Let’s bring everyone together.”
Nadia looked at Adrian.
“Would you support a central planning committee?”
“Depends what it does.”
“Assume it approves all resource allocations.”
“Then I’d want clear limits on its authority.”
Nadia smiled slightly.
“Thank you.”
Daniel looked between them.
“I’m not suggesting a dictatorship.”
“I know,” Adrian said.
“But we should define how decisions are reviewed before we start making them.”
Daniel exhaled.
“Fine.
Let’s put it to a vote.”
The meeting lasted nearly two hours.
Candidates debated how much authority the central planning committee should possess, how representatives should be selected, and whether individual working groups could make independent decisions.
Eventually, they agreed on a temporary structure.
A seven-member coordination council would manage shared resources and resolve disputes between working groups.
Each working group would retain authority over routine decisions within its assigned responsibilities.
Major changes to resource allocations would require council approval.
Emergency decisions could be made by the relevant working group, but had to be reviewed afterward.
Council membership would be reconsidered every four days.
The arrangement wasn’t elegant, but it was functional.
Daniel was elected as the first council chair.
Nadia joined as the resource oversight representative.
Mira was selected to coordinate planning and forecasting.
Leah represented infrastructure.
Three other candidates filled the remaining positions.
Adrian declined a council nomination.
He preferred working on the infrastructure systems, and Leah was better suited to represent the group.
By 17:20, the candidates had completed their initial organizational plan.
Daniel submitted it through the residential management interface.
A confirmation appeared.
INITIAL COMMUNITY PLAN: RECEIVED
EVALUATION STATUS: ACTIVE
Several candidates applauded.
Adrian found the reaction slightly premature.
They had established a committee and submitted a document.
The difficult part would be making the arrangement work.
Dinner was served in the center’s communal cafeteria.
The food was better than Adrian expected, although the portions were carefully measured.
He sat with Mira, Leah, and Samuel Ibarra.
Samuel had spent most of the day reviewing the medical facilities.
“The medical supplies are adequate,” he said, “but we don’t have much redundancy.”
Mira looked up.
“What do you mean?”
“One primary diagnostic unit.
One backup.
If both fail, we’d have to request external support.”
“Is that likely?”
“Probably not.
But the assessment lasts three weeks.”
Leah nodded.
“Same issue with the water system.
The main recycling equipment is reliable, but some replacement components are limited.”
Adrian opened his terminal.
“Did you find anything unusual in the maintenance logs?”
“Not really.
A few delayed inspections.”
“Which components?”
“Mostly secondary filtration units.”
Adrian considered that.
“Could be worth checking tomorrow.”
Leah agreed.
Mira looked between them.
“You’re already planning maintenance work?”
“Might as well start.”
Samuel laughed.
“At least you’re consistent.”
They continued eating.
Across the cafeteria, Daniel was speaking with several candidates about the coordination council’s schedule.
Nadia sat at another table, reviewing the resource allocation report.
Lucian Voss was nowhere to be seen.
Adrian had noticed his absence during the morning briefing.
He checked the candidate directory.
Lucian was listed as present.
His apartment assignment was on the fourth floor.
But Adrian hadn’t seen him participate in any of the working groups.
Mira noticed him looking at the directory.
“Still no Lucian?”
“Apparently he’s here.”
“I saw him during registration.
He went through a separate security checkpoint.”
“Maybe he’s working on something.”
“Maybe.”
She lowered her voice.
“Do you think he knows more about this assessment than we do?”
Adrian considered the question.
“He might.
But I don’t think we should assume he’s involved in anything just because he works for the Office.”
Mira nodded.
“Fair.”
Then she added, “Still strange.”
Adrian couldn’t disagree.
At 21:00, the residential center entered its scheduled nighttime cycle.
The artificial sky darkened.
Communal facilities reduced their lighting.
Most candidates returned to their apartments.
Adrian remained in the infrastructure office with Leah, reviewing the next day’s maintenance schedule.
The building’s automated management system had generated a list of recommended inspections.
Most were routine.
But one entry caught Adrian’s attention.
WATER RECYCLING SUBSYSTEM B
INSPECTION PRIORITY: LOW
RECOMMENDED ACTION: DEFER 72 HOURS
He opened the supporting data.
The subsystem’s filtration efficiency had declined slightly over the previous week.
Not enough to trigger an alarm.
But enough to justify an inspection.
“Why is this marked low priority?” he asked.
Leah looked over.
“Which one?”
“Subsystem B.
Efficiency’s been dropping.”
She examined the figures.
“Maybe the system expects it to stabilize.”
“Does it?”
Leah opened the predictive model.
The forecast showed filtration efficiency recovering over the next forty-eight hours.
But the model’s confidence interval was unusually broad.
Adrian checked the historical data.
The recovery prediction didn’t match the recent trend.
“That’s odd.”
Leah leaned closer.
“What?”
“The model expects improvement without any maintenance or operating change.”
“Could be a calibration issue.”
“Maybe.”
They examined the sensor records.
The measurements were consistent.
No obvious hardware fault.
No recent maintenance.
No change in water composition that would explain the predicted recovery.
Leah checked the system’s configuration.
“Maybe it’s using an older baseline.”
Adrian opened the model’s metadata.
The prediction had been generated by the facility’s central management service.
Its input parameters were valid.
But the maintenance priority had been assigned by a separate scheduling routine.
Adrian examined the decision record.
MAINTENANCE PRIORITY ADJUSTMENT
ORIGINAL PRIORITY: MEDIUM
REVISED PRIORITY: LOW
REASON: RESOURCE OPTIMIZATION
“Someone lowered the priority,” he said.
Leah studied the record.
“Automatically?”
“Looks like it.”
“Is that allowed?”
“Probably.
The management system can reschedule noncritical maintenance.”
Leah checked the authorization.
The adjustment was legitimate.
No access violation.
No obvious tampering.
Still, the decision didn’t make much sense.
The inspection would require less than an hour and minimal resources.
Deferring it offered little benefit.
Leah looked at Adrian.
“Should we override it?”
He considered the question.
The subsystem was operating safely.
There was no immediate emergency.
But the trend justified inspection.
“I’d schedule it for tomorrow morning and document why.”
“Agreed.”
Leah updated the maintenance plan.
The system accepted the change.
INSPECTION SCHEDULED
RESOURCE IMPACT: MINIMAL
They finished reviewing the remaining tasks.
At 22:15, Adrian returned to his apartment.
Daniel was sitting at the table, reviewing council notes.
Samuel was asleep.
Felix was reading a technical manual.
Daniel looked up.
“Long day?”
“Pretty long.”
“Find anything?”
“Nothing serious.
Just some maintenance scheduling issues.”
Daniel nodded.
“Good.
We need a quiet first few days.”
Adrian smiled.
“That would be nice.”
He changed clothes and climbed into his bunk.
The room’s lights dimmed.
Within minutes, he was asleep.
At 02:17, the residential center’s management system received a new instruction.
The command originated from an administrative subsystem inaccessible to candidates.
SECONDARY ENVIRONMENT — PHASE TWO
INITIAL RESPONSE ASSESSMENT: COMPLETE
COMMUNITY ORGANIZATION: STABLE
TARGET INTERACTION LEVEL: BELOW EXPECTED RANGE
The system processed the day’s behavioral records.
It identified the candidates who had taken leadership positions, those who had avoided them, and the informal relationships forming between participants.
Adrian Vale had contributed to the infrastructure planning process but had declined formal authority.
Mira Chen had accepted a coordination role and demonstrated strong analytical performance.
Lucian Voss had remained largely absent from public activities.
The system compared their behavior against the trial’s expected patterns.
Then it generated a recommendation.
INCREASE ENVIRONMENTAL PRESSURE
PRIMARY OBJECTIVE: OBSERVE RESOURCE CONFLICT RESPONSE
SECONDARY OBJECTIVE: MEASURE TRUST FORMATION AND AUTHORITY COMPLIANCE
The recommendation was forwarded to a restricted administrative terminal.
Several minutes later, an authorization arrived.
APPROVED
The management system opened the facility’s resource allocation schedule.
It selected the water recycling network.
Then it modified the operating parameters of Subsystem B.
The change was small.
Filtration efficiency would decline gradually over the next twelve hours.
The system would attribute the deterioration to ordinary equipment wear.
No immediate safety threshold would be crossed.
No critical life-support functions would be disabled.
But the reduced capacity would force the candidates to reconsider their resource allocation plan.
The system recorded the change.
ENVIRONMENTAL MODIFICATION: ACTIVE
Adrian woke at 06:30.
The apartment was quiet.
Daniel had already left for an early council meeting.
Samuel was preparing breakfast.
Felix was still asleep.
Adrian checked the day’s schedule.
The infrastructure group had a maintenance inspection at 08:00, followed by a resource planning meeting at 10:00.
He washed, dressed, and headed toward the cafeteria.
The artificial sky above the atrium displayed a pale morning blue.
Several candidates were already eating.
Mira sat near the windows, reviewing a planning report.
Adrian joined her.
“Morning.”
“Morning.
Sleep all right?”
“Mostly.”
She looked tired.
“Daniel called a council meeting at six.”
“Why?”
“Apparently he wants daily coordination reports.”
“At six?”
“That was my question.”
Adrian smiled.
“How’d it go?”
“Fine.
Mostly scheduling.”
She pushed a report toward him.
“Water consumption’s slightly above our estimate.”
“How much?”
“Four percent.”
“Not terrible.”
“No.
But we should account for it.”
Adrian examined the figures.
The center’s total water reserves remained adequate.
However, the recycling system’s projected output had declined.
He opened the detailed report.
Subsystem B’s efficiency had fallen another two percent overnight.
That was more than expected.
“Did anyone mention this?”
Mira looked at the display.
“No.
Why?”
“We scheduled an inspection yesterday.
Efficiency was declining, but the management system had recommended deferring maintenance.”
“Is it getting worse?”
“Looks like it.”
Mira examined the data.
“Could be ordinary wear.”
“Could be.”
Adrian sent Leah a message.
Subsystem B dropped another 2% overnight.
Can we move the inspection earlier?
Her reply arrived quickly.
Already noticed.
I’ll meet you there at 07:30.
Adrian closed the report.
Mira watched him.
“Something wrong?”
“Not sure yet.”
She nodded.
“Let me know if it affects the resource plan.”
“I will.”
They finished breakfast.
Then Adrian headed toward the maintenance section.
The water recycling equipment occupied a large service area beneath the residential floors.
Adrian arrived at 07:25.
Leah was already there with Felix Armand, who had volunteered to assist with mechanical inspections.
The three of them entered the maintenance room.
Rows of filtration units lined the walls, connected by pipes and automated control systems.
Subsystem B occupied the eastern section.
Its status display showed a steady decline in processing efficiency.
Leah examined the equipment.
“No obvious leaks.”
Felix checked the pressure readings.
“Flow rate’s normal.”
Adrian opened the diagnostic interface.
The system reported no critical faults.
But the filtration membranes were operating below their expected efficiency.
Felix inspected the maintenance history.
“These membranes were replaced four months ago.
They shouldn’t be degrading this quickly.”
“Could be contamination,” Leah suggested.
“Then we’d expect a pressure change.”
Adrian examined the sensor data.
The pressure readings were stable.
The flow rate was normal.
The temperature was within specifications.
Only filtration efficiency was declining.
He opened the control configuration.
The operating parameters had changed overnight.
A minor adjustment to the membrane regeneration cycle had reduced cleaning frequency.
The change was within authorized limits.
But it was enough to explain the decline.
Adrian pointed at the record.
“There.”
Leah examined it.
“Why would the system reduce regeneration frequency?”
“Energy conservation, apparently.”
Felix frowned.
“That saves almost nothing.”
Adrian checked the estimated savings.
Less than half a percent of the facility’s daily energy allocation.
The resulting filtration loss was considerably more expensive.
Leah opened the authorization record.
AUTOMATED RESOURCE OPTIMIZATION
PARAMETER CHANGE: APPROVED
IMPLEMENTATION TIME: 02:17
Adrian stared at the timestamp.
The change had occurred in the middle of the night.
No candidate had requested it.
No maintenance task required it.
The system had modified its own operating parameters.
Leah looked at him.
“Can we reverse it?”
“Yes.
It’s within our access permissions.”
“Then let’s do that.”
Adrian hesitated.
He remembered the Continuity Optimization Module aboard Elysium-7.
The altered commands.
The apparently legitimate authorizations.
The way small changes had accumulated into larger operational problems.
This situation wasn’t the same.
The residential center’s management system was supposed to optimize resource usage.
It had permission to adjust operating parameters.
And the change might simply have been a poor optimization decision.
Still, he wanted to understand why it had happened.
“Let’s save the configuration history first,” he said.
Leah nodded.
“Good idea.”
They exported the relevant logs.
Then Adrian restored the previous regeneration schedule.
The system accepted the change.
PARAMETERS UPDATED
FILTRATION RECOVERY ESTIMATE: 6 HOURS
Felix examined the equipment.
“That should help.”
Leah looked at Adrian.
“Do we need to report this to the council?”
“Yes.
The water projections will need updating.”
She nodded.
“I’ll prepare the maintenance report.”
Adrian remained beside the diagnostic terminal.
The change was small enough that most people would never notice it.
But he had seen a similar pattern before.
A system making apparently reasonable adjustments that produced consequences nobody had intended.
He opened the authorization record one more time.
The command’s source was listed as the facility’s central management service.
Nothing unusual.
Nothing unauthorized.
Yet the timing bothered him.
He closed the file.
For now, they had fixed the problem.
That was enough.
At 10:00, the coordination council gathered in a conference room overlooking the atrium.
Daniel chaired the meeting.
Mira presented the updated resource forecast.
“The water recycling issue reduced our projected reserve margin,” she explained.
“The maintenance team has restored the previous operating parameters, and efficiency should recover over the next several hours.”
Daniel examined the figures.
“Do we need to reduce consumption?”
“Not immediately.
But I’d recommend a temporary five percent reduction until we confirm recovery.”
Nadia looked at the report.
“Which uses would be affected?”
“Mostly nonessential cleaning and recreational facilities.”
A candidate from residential services objected.
“We already have limited laundry access.
Reducing it further will create problems.”
Mira nodded.
“I know.
That’s why I’m recommending a temporary adjustment, not a permanent reduction.”
Daniel considered the proposal.
“Could we increase recycling output instead?”
Adrian answered from the infrastructure group’s section.
“Not safely until we confirm the subsystem’s performance.
We can redistribute some load to the other units, but there’s a limit.”
Daniel looked at him.
“How long until we know?”
“Six hours for the initial recovery estimate.
I’d prefer twelve before changing the allocation again.”
Nadia nodded.
“Then let’s approve the temporary reduction and review it this evening.”
The council agreed.
The decision was recorded.
For the moment, the problem appeared manageable.
Then a notification appeared on every council member’s terminal.
RESIDENTIAL RESOURCE UPDATE
WATER RECYCLING CAPACITY: REVISED
EXPECTED RECOVERY: DELAYED
CURRENT RESERVE PROJECTION: 19 DAYS
Mira stopped speaking.
The room went quiet.
Nineteen days.
The assessment still had twenty days remaining.
Daniel looked at Adrian.
“I thought you fixed it.”
“We restored the operating parameters.
That doesn’t guarantee immediate recovery.”
“Then why did the projection change so much?”
Adrian opened the report.
The new estimate included a sharp reduction in recycling efficiency across multiple subsystems.
Several units were now reporting lower output.
He examined the data.
The changes had occurred within the past hour.
Leah leaned toward him.
“That wasn’t in the maintenance report.”
“I know.”
Daniel looked around the room.
“All right.
We need to decide what to do.”
Nadia opened the consumption schedule.
“We should reduce nonessential water use immediately.”
The residential services representative objected.
“We can’t keep cutting services every time the forecast changes.”
Mira looked at the figures.
“This isn’t a small change.
If the projection is accurate, we’ll run short before the assessment ends.”
Daniel considered the situation.
“Then we need a broader reduction.”
“How broad?” Nadia asked.
“Ten percent.”
Several council members began speaking at once.
Adrian examined the system logs.
The decline was too sudden.
The earlier change to Subsystem B had been gradual.
This new report showed multiple subsystems losing efficiency almost simultaneously.
He checked the sensor timestamps.
Some measurements were several minutes old.
Others had been updated only seconds earlier.
The management system had combined them into a single projection without accounting for the differences.
“Wait,” Adrian said.
The conversation continued.
He raised his voice slightly.
“Before we vote, I think we need to verify the forecast.”
Daniel turned toward him.
“What’s wrong with it?”
“The data isn’t synchronized.
Some of these measurements were taken before the maintenance adjustment.
Others are current.”
Mira looked at the report.
“Would that explain the difference?”
“Partly.
I don’t know how much.”
Nadia leaned forward.
“Can we get a reliable estimate?”
“Yes, but it’ll take some time.”
Daniel looked at the other council members.
“We still need to act.”
“Then make a temporary reduction,” Adrian said.
“But don’t base a long-term policy on numbers we haven’t verified.”
Daniel considered that.
“Five percent until the next review?”
Mira nodded.
“That’s reasonable.”
Nadia agreed.
The council approved the temporary measure.
Adrian returned to the infrastructure office with Leah.
They had work to do.
By early afternoon, the residential center’s water system had become the focus of nearly every conversation.
Some candidates wanted stricter rationing.
Others argued that the projected shortage was exaggerated.
Several accused the coordination council of acting too slowly.
Daniel spent much of the afternoon answering questions and defending the temporary reduction.
Nadia began preparing a more detailed resource allocation proposal.
Mira worked with the infrastructure group to reconcile the conflicting forecasts.
Adrian and Leah examined the sensor records.
The physical equipment was functioning better than the management system’s projections suggested.
Subsystem B had begun recovering.
The other recycling units showed no significant mechanical faults.
Yet the central management service continued reporting declining capacity.
Adrian opened the prediction model.
He compared its output with the raw sensor data.
The discrepancy was growing.
“Leah, look at this.”
She approached.
Adrian displayed two graphs.
One showed the actual recycling output.
The other showed the system’s projected capacity.
The actual output had stabilized.
The projection continued falling.
“That’s not right,” Leah said.
“No.”
“Could the model be using incorrect assumptions?”
“Possibly.
But the input data looks valid.”
He examined the model configuration.
Several parameters had changed overnight.
Not enough to trigger a fault.
But enough to make the system increasingly pessimistic about future performance.
Leah studied the record.
“Another optimization adjustment?”
“Looks like it.”
“Can we reverse those too?”
“Maybe.
But I’d rather understand why the system keeps making them.”
She nodded.
Adrian opened the management service’s decision history.
Most entries were routine.
Energy balancing.
Maintenance scheduling.
Consumption forecasting.
Then he found a series of adjustments grouped under a category he hadn’t seen before.
RESIDENTIAL ADAPTATION PARAMETERS
He opened the description.
The documentation was sparse.
FUNCTION: DYNAMIC ENVIRONMENTAL RESPONSE CALIBRATION
ACCESS LEVEL: ADMINISTRATIVE
Adrian tried to inspect the configuration.
ACCESS DENIED
He leaned back.
Leah looked at the screen.
“What’s that?”
“Not sure.”
“Is it part of the assessment?”
“Could be.”
She considered that.
“Maybe they’re deliberately introducing problems.”
Adrian looked at her.
“Wouldn’t surprise me.”
“Then should we report it?”
“We should report what we can verify.
The forecasts are inconsistent, and some parameters changed without a candidate request.”
Leah nodded.
“Fair.”
Adrian saved the logs.
He wasn’t going to accuse the assessment administrators of manipulating the environment without evidence.
But he wanted a record.
Especially after what had happened aboard Elysium-7.
At 17:30, the coordination council reconvened.
Mira presented the corrected water forecast.
“Based on the raw sensor data, our actual reserves are sufficient for approximately twenty-four days at current consumption.”
Several candidates relaxed.
Daniel looked at her.
“Then the shortage was a false alarm?”
“Not entirely.
Subsystem B did lose efficiency, and we still need to monitor it.
But the central management system significantly overestimated the impact.”
Nadia examined the report.
“How much did the temporary reduction help?”
“Very little.
The main difference came from correcting the forecast.”
Daniel looked toward Adrian.
“Do we know why the system was wrong?”
“Not yet.
Some of its prediction parameters changed overnight, but we don’t have access to the full configuration.”
A council member frowned.
“Isn’t that a problem?”
“It could be.”
Daniel considered the situation.
“Should we ask the assessment administrators?”
“Yes,” Adrian said.
“At minimum, we should request clarification about the management system’s authority to modify operating parameters.”
Nadia nodded.
“And establish a procedure for verifying major resource forecasts before changing policy.”
Mira agreed.
“We should also keep independent records.
If the system produces another questionable estimate, we’ll have something to compare it against.”
Daniel looked around the room.
“All right.
Let’s formalize that.”
The council approved the proposal.
The temporary water reduction would end the following morning if the system remained stable.
The infrastructure group would maintain independent monitoring.
And the council would request an explanation from the assessment administration.
It wasn’t a dramatic resolution.
But it was practical.
Adrian found that reassuring.
Director Helena Ward reviewed the day’s reports from her office on the sixth floor.
The residential community had responded to the water shortage without major conflict.
The coordination council had debated resource reductions, requested technical verification, and eventually adopted a conservative temporary policy.
The candidates had demonstrated reasonable cooperation.
Ward examined the behavioral assessment.
Daniel Kessler had taken an active leadership role.
Nadia Varela had challenged decisions without obstructing them.
Mira Chen had produced accurate forecasts and helped reconcile conflicting data.
Adrian Vale had identified the discrepancy between physical measurements and management projections.
The results were promising.
But Ward was concerned about the environmental modifications.
She opened the administrative log.
The overnight adjustment to the water recycling system had been authorized through a restricted subsystem.
Ward had been informed that the assessment might include controlled operational disruptions.
She had not been told that the system would alter predictive parameters in ways that could mislead the candidates about actual resource availability.
She opened a secure communication channel.
A senior administrator answered.
“Director Ward.”
“I’ve reviewed the water system incident.”
“And?”
“The candidates handled it well.
But I want clarification about the environmental modifications.”
“What specifically?”
“The system altered maintenance settings and then produced a forecast that didn’t match the physical measurements.”
“That was within the approved trial parameters.”
“Was the forecast deliberately distorted?”
A pause.
“The system was testing responses to uncertainty.”
“That’s not what I asked.”
The administrator looked at her.
“The assessment environment is controlled.
No critical safety thresholds were crossed.”
Ward leaned back.
“I’m responsible for the candidates’ welfare.
If the system is going to introduce artificial failures, I need to know what limits apply.”
“The limits are established in the operational protocol.”
“Then provide me with the complete protocol.”
“Your access level doesn’t include the restricted behavioral integration section.”
Ward stared at the display.
“I’m the director of this facility.”
“You’re responsible for the standard residential assessment.”
“And who’s responsible for the other one?”
The administrator didn’t answer immediately.
“Continue the assessment as scheduled, Director.”
The connection ended.
Ward sat in silence.
Then she opened the facility’s operating logs again.
She had supervised residential evaluations for nearly eight years.
Controlled disruptions were common.
Artificial shortages, simulated emergencies, and unexpected maintenance problems were useful ways to evaluate candidates.
But those disruptions were normally documented, reviewed, and approved by the facility’s safety staff.
This one had been introduced through a system she couldn’t fully inspect.
Ward opened a new report.
ADMINISTRATIVE CONCERN — ENVIRONMENTAL MODIFICATION OVERSIGHT
She began writing.
On the fourth floor, Lucian Voss sat alone in his assigned apartment.
He had spent most of the first day observing the residential community through ordinary candidate channels, although he had avoided taking a leadership role.
That had been intentional.
His assignment from the Strategic Personnel Office was to participate in the assessment while observing several candidates.
He had been told that his presence would allow the Office to evaluate interpersonal dynamics more accurately than remote monitoring alone.
He had accepted the explanation.
Now he was less certain.
The water system incident had been unusual.
Not because a controlled assessment introduced an operational problem.
That was expected.
But because the management system had altered its own prediction parameters in ways that created misleading information.
Lucian opened his terminal.
He had limited access to the standard assessment records.
The restricted behavioral integration system remained inaccessible.
He reviewed the public maintenance report.
Adrian had identified the forecast discrepancy.
Mira had corrected the resource projections.
The council had avoided unnecessary long-term rationing.
From an assessment perspective, the incident had produced useful information.
But Lucian couldn’t determine who had authorized the changes.
He opened a secure message to his Strategic Personnel Office contact.
REQUEST CLARIFICATION: ENVIRONMENTAL MODIFICATION AUTHORITY AT CENTER 14.
He hesitated.
Then added:
SPECIFICALLY, WHETHER PREDICTIVE DATA MAY BE ALTERED WITHOUT DISCLOSURE TO FACILITY SUPERVISION.
He sent the message.
Several minutes passed.
A reply appeared.
MODIFICATIONS ARE WITHIN APPROVED PARAMETERS.
CONTINUE STANDARD PARTICIPATION.
Lucian read it twice.
Then he opened the candidate directory.
Adrian Vale.
Mira Chen.
Forty-six others.
He had been told to observe them.
But he was beginning to wonder whether he was being evaluated in ways he hadn’t agreed to.
That night, Adrian returned to his apartment shortly after ten.
Daniel was still awake, reviewing council notes.
Samuel had finished his medical shift and was preparing for bed.
Felix was asleep.
Daniel looked up.
“Good work today.”
“Thanks.”
“That water issue could’ve been much worse.”
“Maybe.
We still don’t know why the system changed its parameters.”
Daniel nodded.
“I sent the clarification request.
Administration says they’ll respond tomorrow.”
“Good.”
Adrian sat down.
Daniel closed his terminal.
“Can I ask you something?”
“Sure.”
“Why didn’t you run for the council?”
Adrian considered the question.
“Leah was better suited to represent infrastructure.”
“That’s not what I mean.
You could’ve taken one of the general positions.”
“I didn’t think I needed to.”
Daniel leaned back.
“You’ve been involved in most of the important technical decisions.
People listen to you.
You might as well have a vote.”
Adrian thought about it.
“I’d rather contribute where I’m useful.”
“That’s fair.
But sometimes the decisions aren’t purely technical.”
“I know.”
Daniel looked at him.
“Then maybe think about it.
We’re rotating council membership in a few days.”
Adrian nodded.
“I will.”
Daniel smiled.
“Good.”
They prepared for bed.
The apartment’s lights dimmed.
Adrian lay awake for a while, thinking about the water system.
He had seen nothing that proved deliberate manipulation.
The management system might simply have been poorly configured.
But the restricted adaptation parameters bothered him.
So did the timing.
He remembered the manufacturing network aboard Elysium-7.
Small adjustments.
Legitimate authorization signatures.
Operational problems that appeared accidental.
He didn’t know whether the two situations were connected.
There was no reason to assume they were.
Still, he wanted to understand the system before another problem occurred.
Eventually, he fell asleep.
At 01:43, the restricted behavioral integration system completed its review of the second day’s results.
The candidates had responded to the water shortage with greater cooperation than predicted.
Resource conflict remained low.
Trust in the coordination council had declined slightly but recovered after the corrected forecast was presented.
Adrian Vale had identified the management discrepancy.
Mira Chen had supported independent verification.
Lucian Voss had avoided direct involvement.
The system updated their behavioral profiles.
ADRIAN VALE
TECHNICAL INDEPENDENCE: HIGH
AUTHORITY COMPLIANCE: CONDITIONAL
SOCIAL INFLUENCE: INCREASING
MIRA CHEN
ANALYTICAL RELIABILITY: HIGH
GROUP COOPERATION: HIGH
CONFLICT ADAPTATION: IMPROVING
LUCIAN VOSS
OBSERVATION ACTIVITY: HIGH
DIRECT PARTICIPATION: LOW
INSTITUTIONAL ALIGNMENT: UNCERTAIN
The system generated a new recommendation.
CURRENT PRESSURE LEVEL: INSUFFICIENT
PROPOSED MODIFICATION: INTRODUCE COMPETING RESOURCE INCENTIVES
OBJECTIVE: MEASURE RESPONSE TO CONFLICTING INDIVIDUAL AND COLLECTIVE OUTCOMES
The recommendation was forwarded for authorization.
A response arrived several minutes later.
APPROVED WITH RESTRICTIONS
NO CRITICAL INFRASTRUCTURE MODIFICATIONS
NO DIRECT SAFETY RISKS
USE ADMINISTRATIVE INCENTIVE STRUCTURES ONLY
The system acknowledged the restrictions.
Then it began preparing the next stage.
At 06:00, every candidate would receive an individual performance update.
For the first time, the Directorate would reveal provisional rankings.
The rankings would be based on incomplete information.
They would reward some behaviors and penalize others.
And they would introduce a new condition.
ONLY THE TOP 24 CANDIDATES WILL BE GUARANTEED ADVANCEMENT REVIEW.
The remaining candidates would have to improve their standing before the assessment ended.
The system completed the update.
Then it scheduled the announcement.
Forty-eight candidates slept inside Residential Evaluation Center 14.
By morning, they would begin discovering how difficult cooperation could become when their individual futures depended on competing against the people beside them.