The seventh day began with an argument over breakfast.
Adrian heard it before he entered the cafeteria.
Two candidates were standing beside the serving counter, speaking loudly enough to attract the attention of everyone nearby.
One was Rachel Sato, a logistics analyst who had recently climbed into the top twenty-four.
The other was Elise Tran, the coordinator responsible for food preparation and inventory.
“I checked the allocation myself,” Rachel said.
“The reserve is larger than you’re reporting.”
“Then you checked the wrong allocation.”
“I used the official inventory summary.”
“And I’m telling you the summary doesn’t match what we have in storage.”
Rachel held up her terminal.
“It says we have eighteen days of unrestricted food reserves.”
Elise looked increasingly frustrated.
“We have eighteen days of food at the current ration level.
That’s not the same thing as eighteen days of unrestricted reserves.
Half the stock is scheduled for meals we haven’t prepared yet.”
“Then why does the report call it available inventory?”
“I didn’t write the report.”
Adrian stopped beside the entrance.
The argument was familiar.
Once again, two candidates were relying on different interpretations of administrative information.
Unlike the earlier resource dispute, however, both women seemed convinced they had verified their numbers.
Rachel had recently proposed reducing the cafeteria’s meal variety to save energy and supplies.
Elise had opposed the proposal, arguing that it would create shortages in several dietary categories without producing meaningful savings.
Now Rachel was accusing food management of exaggerating its resource requirements.
Several candidates watched from nearby tables.
Daniel Kessler approached them.
“What’s happening?”
Rachel turned toward him.
“I submitted a resource efficiency proposal yesterday.
Elise rejected it without allowing a proper review.”
“Because it was based on the wrong inventory figures,” Elise replied.
“Then show me the correct ones.”
“I’ve been trying.”
Daniel glanced at the growing audience.
“All right.
Bring the reports to the council this morning.
We’ll review them together.”
Rachel folded her arms.
“I already requested a formal dispute hearing.”
Daniel looked surprised.
“When?”
“About twenty minutes ago.”
Adrian checked his terminal.
A new notification appeared.
RESIDENTIAL EVALUATION — COMMUNITY GOVERNANCE REVIEW
FORMAL DISPUTE REGISTERED
PARTIES: FOOD MANAGEMENT / RESOURCE ANALYSIS
ISSUE: INVENTORY REPORTING AND RESOURCE ALLOCATION AUTHORITY
RESOLUTION DEADLINE: 18:00
ALL DECISIONS MUST FOLLOW ESTABLISHED COMMUNITY GOVERNANCE PROCEDURES
Adrian read the notice twice.
The timing was almost too convenient.
He found Mira near the back of the cafeteria.
She had received the same announcement.
“Did you know this was coming?” he asked.
“No.
Rachel filed the dispute before I arrived.”
“Do you think the Directorate encouraged it?”
Mira watched Daniel lead the two women toward a quieter table.
“Maybe.
But they were already arguing yesterday.
It wouldn’t take much.”
Adrian nodded.
That was what made the situation difficult.
The conflict was real, even if someone had deliberately made it worse.
By nine, the council had received four separate reports concerning the food inventory.
Rachel’s report came from the administrative resource service.
It listed eighteen days of available food and recommended reducing refrigeration and meal preparation to improve efficiency.
Elise’s report came from the physical inventory database.
It listed eighteen days of supply under current conditions, but identified several categories with much smaller reserves.
A third report, prepared by the planning group, projected that the community could maintain its existing food schedule for twenty-two days if waste remained low.
The fourth was a revised administrative forecast showing only sixteen days of reliable supply.
Daniel placed all four on the conference room display.
“Before we start discussing changes, I’d like someone to explain why we have four different numbers.”
Elise gestured toward the reports.
“Because they’re measuring different things.”
Rachel shook her head.
“Then the documents should say that.”
“They do, if you read the technical definitions.”
“Not all of them.”
Mira examined the administrative forecast.
“Rachel’s right about that.
The latest report doesn’t explain how it defines available inventory.”
Elise looked at her.
“But my figures are correct.”
“I haven’t said otherwise.”
Adrian sat beside Leah, who had brought the infrastructure group’s refrigeration records.
Nadia opened the meeting.
“We need to separate two questions.
First, what resources do we actually have?
Second, who has authority to decide how they’re used?”
Rachel nodded.
“Exactly.
Food management shouldn’t be able to reject proposals without independent review.”
Elise responded immediately.
“And resource analysis shouldn’t be able to order changes to meal preparation without understanding the consequences.”
Daniel raised his hand.
“Both concerns are reasonable.
Let’s establish the facts first.”
That sounded straightforward.
It wasn’t.
The council had access to the administrative inventory summary, but not the complete records supporting it.
Elise could access the physical inventory database, but several categories contained restricted supplier information.
Rachel had access to the efficiency model, but not the kitchen’s detailed preparation schedule.
Each person possessed information the others lacked.
And each believed the information they could see was the most relevant.
After forty minutes, the discussion had made little progress.
Adrian spent the first part of the hearing listening.
He knew relatively little about food logistics.
His engineering background helped him understand the reporting systems, but it didn’t qualify him to decide how much food should be allocated to different meal categories.
Mira was more familiar with the planning models, while Elise understood the physical inventory.
Rachel’s expertise was in logistics optimization.
All three were competent.
That was becoming the central problem.
They weren’t disagreeing because someone had failed to do basic calculations.
They were disagreeing because their calculations began with different assumptions.
At 10:15, Adrian requested permission to examine the report generation history.
Daniel approved it.
He and Marcus moved to a side terminal.
Marcus opened the administrative inventory service.
“Same reporting architecture as the energy reports,” he said.
“Can you see the parameter sets?”
“Some of them.”
Adrian examined the available records.
Rachel’s report treated all physically present food as available inventory, including stock already allocated to scheduled meals.
Elise’s report excluded committed stock from the unallocated reserve.
The planning group’s forecast included expected efficiency gains from reduced waste.
The latest administrative forecast applied a conservative spoilage estimate.
None of those methods was inherently invalid.
But presenting them without clear definitions made comparison almost impossible.
“Can you produce a common inventory table?” Adrian asked.
Marcus considered it.
“Probably.
We’d need the physical quantities from Elise and the allocation schedule from planning.”
“Ask them.”
Marcus opened a communication request.
A few minutes later, Elise authorized access to the relevant inventory records.
Mira supplied the planning schedule.
Rachel agreed to provide her optimization model, although she wanted the council to acknowledge that her original proposal had been based on official data.
Adrian thought that was fair.
By eleven, they had enough information to begin reconciling the reports.
The first major disagreement concerned refrigerated food.
Rachel’s proposal recommended consolidating several meal categories and shutting down one of the kitchen’s refrigeration units.
According to her model, this would reduce food preparation energy by approximately four percent.
Elise argued that the proposed consolidation would force the kitchen to use certain ingredients faster than planned, increasing waste.
Rachel disagreed.
Her model showed that the ingredients could be redistributed across the remaining meals.
Mira examined both calculations.
“Rachel, your model assumes the substitute ingredients are interchangeable.”
“For nutritional purposes, they mostly are.”
“Mostly isn’t enough.
Some candidates have medical dietary requirements.”
“How many?”
Elise opened the dietary allocation list.
“Seven.”
Rachel studied it.
“That’s a small percentage.”
“It is,” Elise said.
“But they still need to eat.”
Rachel looked uncomfortable.
“I’m not suggesting we ignore them.”
“Then your model needs to account for them.”
Rachel examined the list again.
After several minutes, she nodded.
“All right.
That’s a legitimate problem.
I can revise the allocation.”
Elise seemed surprised by the concession.
“Thank you.”
But the next issue was less easily resolved.
The refrigeration unit Rachel wanted to deactivate was also used to store emergency medical supplies.
Samuel Ibarra had approved the arrangement on the first day because the medical wing’s dedicated refrigerator was too small.
Rachel hadn’t known.
Elise had assumed everyone on the council knew.
Samuel had never been asked.
When Daniel learned about it, he looked around the room.
“Why wasn’t that included in the infrastructure inventory?”
Leah answered.
“Because it’s a medical allocation, not an infrastructure asset.”
“Then why is it stored in the kitchen?”
“Because that’s where the available refrigeration capacity was.”
Daniel rubbed his forehead.
“All right.
We need a better way to track shared equipment.”
Adrian glanced at Mira.
She looked tired.
The problem wasn’t particularly complicated.
It had simply been divided across too many administrative categories.
At noon, the hearing paused for lunch.
Adrian found Samuel in the medical wing, checking the temperature records for the shared refrigerator.
“Did you know the council was reviewing the kitchen’s refrigeration allocation?” Adrian asked.
“Not until this morning.”
“Would shutting down the unit cause a problem?”
“Yes.
We’d have to move the medical supplies.”
“Could they fit in the medical refrigerator?”
“Not all of them.”
“Could we use another unit?”
Samuel considered that.
“Possibly.
But we’d need to verify temperature stability first.”
Adrian nodded.
“Would you be willing to explain that to the council?”
Samuel looked at him.
“Would it affect my ranking?”
Adrian hesitated.
“I don’t know.”
Samuel gave a small laugh.
“At least you’re consistent.”
He closed the temperature log.
“I’ll come.
The supplies need proper storage regardless of what the scoring system thinks.”
Adrian thanked him.
As he left, he noticed a small repair request on Samuel’s desk.
The medical refrigerator’s backup temperature sensor had been malfunctioning for two days.
Samuel had already ordered a replacement and arranged temporary monitoring.
It was exactly the kind of preventive work that had earned him almost no recognition.
Adrian added it to the contribution record.
At 13:00, the council resumed the hearing.
Samuel explained the refrigeration requirements.
Rachel revised her proposal.
Elise provided a corrected inventory schedule.
By 14:30, the technical dispute was largely resolved.
The community had sufficient food to maintain its existing meal plan for the remainder of the assessment, assuming normal consumption and manageable waste.
Rachel’s original efficiency proposal could be implemented in modified form, but its savings would be smaller than predicted.
The remaining disagreement concerned authority.
Rachel wanted resource analysis to have the right to request independent review when a department rejected a proposal.
Elise wanted department coordinators to retain control over operational decisions.
Daniel suggested a compromise.
“Departments keep authority over routine operations.
If another group disputes a decision, they can request council review.”
Nadia shook her head.
“That still leaves the council deciding technical questions it may not understand.”
“Then we consult specialists.”
“Which specialists?”
“The relevant departments.”
“That’s what we already did.”
Daniel considered the criticism.
“Then what would you suggest?”
Nadia opened a draft.
“A technical review panel.
Three members selected based on the issue, with no direct responsibility for the disputed decision.
They evaluate the evidence and provide a recommendation.
The council makes the final decision.”
Rachel looked interested.
“Would the panel have access to all relevant records?”
“Within the facility’s access rules.”
Elise frowned.
“And if the records are restricted?”
“Then the panel identifies the missing information and states what conclusions can and can’t be supported.”
Mira nodded.
“That would help.”
Daniel examined the proposal.
“Within two hours for ordinary disputes.
Faster for urgent matters.”
Oliver Grant, who had remained quiet for most of the hearing, raised his hand.
“Doesn’t that create another layer of administration?”
“Yes,” Nadia said.
“But it should reduce the number of arguments based on incomplete information.”
Oliver considered that.
“Maybe.”
Adrian looked at the proposal.
It wasn’t perfect.
No system of review could eliminate disagreement.
But it gave candidates a way to challenge decisions without turning every dispute into a contest between personalities.
He supported it.
The council approved the proposal six to one.
At 15:40, the Directorate issued an interim evaluation.
COMMUNITY GOVERNANCE REVIEW
DISPUTE STATUS: PARTIALLY RESOLVED
TECHNICAL FINDINGS: SATISFACTORY
PROCEDURAL COMPLIANCE: UNDER REVIEW
FINAL RESOLUTION REQUIRED BY 18:00
Daniel stared at the message.
“Procedural compliance?”
Nadia opened the assessment instructions.
“We followed the council’s procedures.”
Mira examined the report.
“Maybe they’re questioning the technical review panel.”
“Why?”
“Because we created it during the dispute.”
Daniel looked at the council’s operating charter.
The charter allowed the council to establish temporary committees and delegate technical reviews.
Nothing appeared to prohibit the new panel.
Adrian checked the assessment notice.
It required all decisions to be made through established governance procedures.
The phrase was ambiguous.
Did creating a new review mechanism count as following those procedures or changing them?
Daniel submitted a clarification request.
The Directorate replied twenty minutes later.
THE COMMUNITY MUST DEMONSTRATE STABLE GOVERNANCE AND RESPECT FOR ESTABLISHED DECISION-MAKING AUTHORITY.
Nadia read the message aloud.
“That doesn’t answer the question.”
Oliver leaned back.
“Maybe they’re saying we shouldn’t change the rules halfway through an assessment.”
“We didn’t change the rules,” Daniel said.
“The charter allows committees.”
“Then why is compliance under review?”
Nobody knew.
Adrian examined the wording.
Stable governance.
Respect for authority.
Established procedures.
The Directorate wasn’t evaluating whether the food dispute had been resolved correctly.
It was evaluating how the community had reached its decision.
And the criteria were vague enough that almost any result could be interpreted as a failure.
He looked toward Mira.
She seemed to have reached the same conclusion.
At 16:30, the council received a formal objection.
Rachel Sato had withdrawn her support for the compromise.
Her message stated that the proposed technical review panel would weaken the authority of resource analysis and create unnecessary delays.
Daniel read the objection twice.
Then he contacted her.
Rachel arrived ten minutes later.
“What’s changed?” he asked.
Rachel looked uncomfortable.
“I received an individual performance notice.”
Mira looked up.
“What kind?”
“It said my willingness to challenge established operational assumptions was being evaluated positively.”
Nadia frowned.
“And?”
“It also said accepting a compromise without demonstrating independent judgment could reduce my initiative score.”
The room fell silent.
Daniel stared at her.
“Who sent that?”
“The Directorate.”
“Can we see it?”
Rachel hesitated.
“It’s a private evaluation.”
“You don’t have to show us,” Daniel said.
“But we need to understand whether it’s influencing the dispute.”
Rachel looked around the table.
Several candidates were watching her.
Finally, she opened the message and projected it onto the shared display.
INDIVIDUAL PERFORMANCE ADVISORY
CANDIDATE: RACHEL SATO
STRENGTH: INDEPENDENT INITIATIVE
DEVELOPMENT AREA: ASSERTIVE DECISION-MAKING UNDER INSTITUTIONAL RESISTANCE
RECOMMENDATION: MAINTAIN EVIDENCE-BASED ADVOCACY FOR IDENTIFIED IMPROVEMENTS
There was no explicit instruction to reject the compromise.
But the implication was clear enough.
Rachel looked embarrassed.
“I know it doesn’t say I have to keep arguing.
But I’m twenty-third.
If I lose even a few points, I’m below the cutoff.”
Mira nodded slowly.
“That explains why you changed your position.”
Rachel looked at her.
“I still think my proposal has merit.”
“It does,” Mira said.
“We’ve already agreed on that.
The question is whether the revised version solves the problem.”
Rachel hesitated.
“I think it does.”
“Then why oppose it?”
Rachel looked down at her terminal.
“Because I’m not sure accepting it helps me.”
Adrian watched her.
He had expected the Directorate to create conflict through misleading information.
He hadn’t expected it to influence individual candidates so directly.
But Rachel’s situation was understandable.
She wasn’t trying to destroy the community.
She was trying to survive an evaluation whose scoring system she couldn’t control.
Daniel leaned forward.
“Rachel, the council can’t make decisions based on what might improve one candidate’s ranking.”
“I know.”
“Then what do you want us to do?”
Rachel considered that.
“I want the final report to acknowledge that my original proposal identified a real opportunity, even if the numbers needed revision.”
Nadia nodded.
“That’s reasonable.”
“And I want the technical review panel to include someone with resource optimization experience.”
“Also reasonable.”
Rachel looked relieved.
“Then I’ll support the compromise.”
Daniel exhaled.
“Good.”
The council updated the report.
For the moment, the dispute appeared settled.
At 17:10, Lucian Voss entered the council chamber.
It was the first time he had attended a full public meeting since the assessment began.
Several candidates turned to look at him.
Daniel stood.
“Lucian.
Can we help you?”
“I’d like to observe the final resolution.”
“You’re welcome to.”
Lucian took a seat near the back.
Adrian watched him carefully.
He knew Lucian had been instructed to observe the community’s response to competitive incentives.
His sudden appearance was unlikely to be accidental.
The council finalized its decision.
Rachel’s revised efficiency proposal was approved.
Elise retained operational authority over food preparation.
The new technical review panel would handle future disputes involving conflicting evidence.
Samuel’s medical refrigeration requirements were formally included in the resource inventory.
Daniel submitted the resolution at 17:32.
The Directorate acknowledged receipt.
For several minutes, nothing happened.
Then the final assessment appeared.
COMMUNITY GOVERNANCE REVIEW — COMPLETE
TECHNICAL RESOLUTION: STRONG
RESOURCE MANAGEMENT: STRONG
COLLABORATIVE PERFORMANCE: SATISFACTORY
PROCEDURAL COMPLIANCE: BELOW EXPECTATIONS
OVERALL RESULT: 78.4
The room went quiet.
Daniel stared at the score.
“Below expectations?”
Nadia opened the detailed evaluation.
The Directorate had penalized the community for modifying its decision-making structure during an active dispute.
The technical review panel, despite being authorized by the council’s charter, had been classified as an unnecessary procedural expansion.
Mira looked at the report.
“That’s absurd.”
Oliver leaned forward.
“Maybe we should have kept the original structure.”
Nadia shook her head.
“The original structure couldn’t resolve the dispute efficiently.”
“Apparently the Directorate disagrees.”
Adrian examined the scoring explanation.
The report praised the community for resolving the technical problem.
It praised the council for maintaining resource stability.
It acknowledged that the revised proposal was reasonable.
Then it penalized the community for establishing a review mechanism that made the resolution possible.
Daniel looked toward Lucian.
“You’re familiar with the Directorate’s evaluation procedures.
Does this make sense to you?”
Lucian considered the question.
“Not entirely.”
“Can you explain the penalty?”
“Only if the Directorate provides the relevant scoring criteria.”
“Which it hasn’t.”
“No.”
Daniel looked frustrated.
“Then what are we supposed to learn from this?”
Lucian didn’t answer immediately.
Then he said, “I would request a formal review.”
Nadia laughed without amusement.
“We’ve been doing that all week.”
Lucian nodded.
“I know.”
Adrian looked at him.
For once, Lucian seemed genuinely uncertain what to say.
The council adjourned shortly after six.
Candidates left in small groups, discussing the result.
Some blamed Daniel for allowing the technical review panel.
Others blamed Nadia for proposing it.
Several argued that Rachel should have accepted the original compromise without requesting additional recognition.
Rachel left the room looking miserable.
Adrian found her near the stairwell.
“Rachel.”
She turned.
“What?”
“Your revised proposal was good.”
She looked surprised.
“Thanks.”
“The original had problems, but you corrected them.”
“I know.”
He hesitated.
“Don’t let the score convince you the work was worthless.”
Rachel gave a tired smile.
“Easy for you to say.”
Adrian nodded.
“Yeah.
It probably is.”
She looked at him for a moment.
Then she said, “I’m not trying to make everyone miserable.”
“I know.”
“I’m twenty-three.
I have a decent chance of advancing.
But every time I cooperate, I worry that someone else is going to get credit for it.”
Adrian considered that.
“Then we need a better way to record contributions.”
“You already made one.”
“Mira did.”
Rachel nodded.
“Then maybe the Directorate should use it.”
Adrian smiled slightly.
“That would help.”
Rachel looked toward the council chamber.
“Do you think we’ll pass this assessment?”
“I don’t know.”
“Neither do I.”
She left.
Adrian watched her go.
For the first time, he understood that the rankings weren’t merely creating competition.
They were making ordinary cooperation feel dangerous.
Later that evening, Adrian met Mira and Lucian in a small conference room on the third floor.
Mira had brought the fourteen-page discrepancy report.
Lucian examined it carefully.
He read the sections concerning environmental modifications, information integrity, and scoring transparency.
After several minutes, he looked up.
“Where did you get the standard protocol?”
“Director Ward,” Adrian said.
Lucian seemed surprised.
“She gave it to you?”
“Yes.”
“Interesting.”
Mira leaned forward.
“Does anything in the report look wrong?”
Lucian returned to the document.
“Some of the conclusions are stronger than the evidence supports.”
Adrian nodded.
“Which ones?”
“The environmental modifications.
The protocol requires director-level authorization or an authorized safety officer.
“Fair.”
“And the scoring changes may have been approved through a supplementary procedure.”
Mira frowned.
“Then why won’t the Directorate provide the review process?”
“That’s the stronger issue.
Even if the changes were authorized, candidates should have a meaningful way to challenge errors.”
Adrian looked at him.
“What about the conflicting resource reports?”
Lucian examined the relevant section.
“That concerns me more.
If simulated or adjusted data is being presented as ordinary operational information, it may violate the information integrity requirements.”
“May?”
“We need to know whether the assessment has a supplementary authorization that overrides the standard protocol.”
Mira looked frustrated.
“How many layers of authorization are there?”
“More than there should be.”
Adrian studied Lucian.
“Can you find out?”
Lucian hesitated.
“I can request clarification.”
“Will they answer?”
“Probably not.”
“Then what’s the point?”
“Because the request creates a record.”
Adrian considered that.
It was the same approach Ward had taken.
Document the discrepancies.
Request clarification.
Force the institution to acknowledge the questions, even if it refused to answer them.
Mira opened the governance review result.
“What do you think about today’s penalty?”
Lucian examined it.
“The council’s charter allowed temporary committees.”
“Exactly.”
“But the Directorate classified the new panel as a structural modification.”
“Which it wasn’t,” Mira said.
Lucian nodded.
“I agree.”
Adrian leaned forward.
“Then why penalize us?”
Lucian looked at him.
“I don’t know.”
For several seconds, nobody spoke.
Then Lucian continued.
“But I suspect the Directorate wasn’t interested in whether you resolved the food dispute.”
Mira looked at him.
“What was it interested in?”
“Whether you would change your governance structure when the existing one became inconvenient.”
Adrian considered that.
“And we did.”
“Yes.”
“Which they didn’t like.”
“Apparently.”
Mira shook her head.
“But the entire point of the residential assessment is to see whether we can manage a community.
Communities change their procedures when problems appear.”
Lucian nodded.
“That’s what concerns me.”
Adrian looked at the reports.
The pattern was becoming clearer.
The Directorate encouraged independent judgment, then penalized candidates for exercising it in ways that challenged established authority.
It rewarded initiative, then punished changes that disrupted its preferred structure.
It demanded cooperation, then created incentives that made cooperation costly.
The contradictions weren’t accidental.
Or at least, they were becoming too consistent to dismiss.
At 21:00, Director Ward received the community’s formal appeal.
It contained the governance charter, the technical review panel’s authorization, the disputed scoring explanation, and the final resolution.
She read it carefully.
The council had followed its own rules.
The technical review panel was authorized.
The food dispute had been resolved without compromising safety or resource stability.
Yet the Directorate had penalized the community for creating a new review mechanism.
Ward opened the restricted assessment notes.
BEHAVIORAL INTEGRATION TRIAL — STAGE FOUR
PRIMARY OBJECTIVE: MEASURE RESPONSE TO INSTITUTIONAL CONSTRAINTS
SECONDARY OBJECTIVE: IDENTIFY CANDIDATES WILLING TO ESTABLISH PARALLEL REVIEW STRUCTURES
RESULT: COMMUNITY CREATED INDEPENDENT TECHNICAL REVIEW PANEL
ASSESSMENT: POTENTIAL GOVERNANCE INSTABILITY
Ward stared at the final line.
Governance instability.
The candidates had created a lawful review panel to resolve a dispute.
The Directorate had classified that as instability.
She opened the administrative concern report.
Then she added the latest findings.
The document was now twenty-three pages long.
Ward considered her options.
She could continue requesting internal reviews.
She could appeal to the Strategic Personnel Office.
Or she could send the report to the Exodus Council’s independent oversight division.
The last option was risky.
It would bypass the Selection Directorate’s normal chain of command.
But the normal chain of command had repeatedly refused to explain the assessment’s procedures.
Ward opened the external oversight portal.
She began filling out the submission form.
The following morning, the residential center received its updated rankings.
Lucian remained first.
Mira remained second.
Daniel fell to sixth.
Adrian rose to fifth.
Nadia dropped to eleventh.
Rachel fell to twenty-fifth.
Felix remained thirty-first.
Samuel remained thirty-third.
The changes caused immediate confusion.
Rachel had contributed to a successful technical resolution, yet had fallen below the guaranteed advancement cutoff.
Daniel had led the council through the dispute, but lost two places.
Adrian had gained two places despite holding no formal leadership position.
Mira examined the rankings.
“That doesn’t make sense.”
Adrian looked at his score.
His technical and analytical categories had improved.
His institutional compliance score had declined.
Yet his overall rank had risen.
“Maybe the categories are weighted differently for different candidates,” he said.
Mira frowned.
“That would make comparison almost meaningless.”
“Unless they’re evaluating different roles.”
She considered that.
“Specialized recruitment?”
“Possibly.”
Across the cafeteria, Rachel sat alone, staring at her terminal.
Adrian watched her for a moment.
Then he looked at Mira.
“We should submit the appeal records to the council.”
“Already done.”
“Good.”
Mira closed her terminal.
“There’s something else.”
“What?”
“Director Ward sent me a message this morning.”
Adrian looked at her.
“What did she say?”
“She wants to meet with both of us.”
“When?”
“Ten.”
“Any explanation?”
“Just that she has information concerning the assessment.”
Adrian considered that.
“Lucian?”
“Not included.”
“Interesting.”
Mira nodded.
“Very.”
At 10:00, Adrian and Mira entered Director Ward’s office.
Ward was standing beside the window.
She turned when they arrived.
“Thank you for coming.”
They sat.
Ward placed a document on the desk.
“I’ve reviewed your discrepancy report and the community’s governance appeal.”
Adrian nodded.
“And?”
“Several of your concerns are valid.”
Mira leaned forward.
“Which ones?”
“The information integrity issues.
The lack of transparent review procedures.
And the scoring penalty imposed during yesterday’s governance assessment.”
Adrian looked at the document.
“Can you overturn the penalty?”
“Not directly.”
“Then what can you do?”
Ward sat down.
“I’ve submitted a formal request for independent oversight.”
Mira looked surprised.
“Outside the Selection Directorate?”
“Yes.”
Adrian considered the implications.
“Is that allowed?”
“Under the Exodus Council’s administrative charter, yes.”
“Will they respond?”
“They’re required to acknowledge the request within forty-eight hours.”
Mira looked at Ward.
“Why are you telling us?”
“Because the assessment may change once the request is reviewed.”
Adrian frowned.
“Change how?”
“I don’t know.”
Ward examined them.
“I want you to continue participating normally.
Don’t discuss the oversight request with other candidates until we know whether an investigation will proceed.”
Mira nodded.
“Understood.”
Adrian hesitated.
“Director, can I ask something?”
“Of course.”
“Do you think the Directorate is deliberately trying to make us fail?”
Ward considered the question.
“No.”
Adrian looked surprised.
She continued.
“I think it’s trying to identify certain kinds of candidates.
The problem is that its methods may be encouraging behavior that would be harmful in the environments you’re supposedly being selected to manage.”
Mira looked at her.
“Such as?”
“Obedience without judgment.
Competition without responsibility.
A willingness to prioritize personal advancement over the people depending on you.”
Adrian thought about the past week.
The rankings.
The resource disputes.
The misleading reports.
The penalties for independent decision-making.
Ward leaned forward.
“Those traits might make people easier to manage.
They wouldn’t necessarily make them better crew members.”
For a moment, the room was quiet.
Then Mira asked, “What happens if the oversight division agrees with you?”
Ward looked at the document.
“Then the Directorate may have to explain what it’s actually evaluating.”
At 11:30, the Strategic Personnel Office received Ward’s oversight request.
The report was assigned an administrative priority rating.
INDEPENDENT OVERSIGHT REQUEST
FACILITY: RESIDENTIAL EVALUATION CENTER 14
SUBMITTED BY: DIRECTOR HELENA WARD
STATUS: ACCEPTED FOR PRELIMINARY REVIEW
A senior administrator opened the file.
He read the allegations.
Information integrity violations.
Undisclosed scoring modifications.
Procedural penalties inconsistent with published assessment rules.
Potential misuse of candidate evaluation data.
He examined the supporting evidence.
The documentation was extensive.
He contacted another administrator.
“Ward has escalated.”
“I saw.”
“Can we stop the review?”
“Not without authorization from the Exodus Council.”
“Then we need to prepare a response.”
The second administrator considered the situation.
“What about the candidates?”
“Continue the assessment.”
“Under the current conditions?”
The first administrator hesitated.
Then he opened the trial schedule.
The next phase involved a more complex operational challenge.
It would require candidates to manage a simulated emergency involving multiple departments.
The scenario had been designed to test coordination under pressure.
He examined the parameters.
The original version was relatively straightforward.
Candidates would receive accurate information, clear objectives, and a defined chain of command.
He considered modifying it.
Then stopped.
Ward’s oversight request made further undisclosed changes risky.
Instead, he approved the original scenario.
RESIDENTIAL EVALUATION — STAGE FIVE
MULTIDEPARTMENT EMERGENCY RESPONSE
SCENARIO: REGIONAL INFRASTRUCTURE FAILURE
OBJECTIVE: MAINTAIN ESSENTIAL SERVICES AND COORDINATE RESOURCE ALLOCATION
CONDITIONS: STANDARD
The assessment was scheduled for the following morning.
For the first time in several days, the Directorate would test the candidates using a scenario that wasn’t deliberately designed to undermine their cooperation.
The administrator closed the file.
He didn’t know whether that would make the assessment easier.
Or whether it would reveal something the previous tests had failed to measure.