scribe

Chapter 6 - The Price Beside Her Name

Isolde did not touch the keyboard.

“Export everything,” she told Bell.

“I already tried.”

“And?”

“The system blocks external media.”

“Print it.”

Bell stared at her.

“All thirty-seven?”

“All thirty-seven. Adjustment history, access history, metadata, every tab.”

The printer began spitting pages into the tray.

Isolde watched her own name remain on the screen.

ISOLDE VIRELAINE — $68,000.

“Tell me exactly where you found this.”

Bell opened a hidden local directory used by the scoring software.

“When the network drops, Northstar’s program caches unfinished transactions. Most of it deletes after synchronization, but this machine had an old recovery image from last winter.”

“So this was never meant to be visible?”

“No, ma’am.”

“What does HIGH ATTRITION VALUE mean?”

“I thought maybe contract cost.”

“Per person?”

Bell shook her head.

“It doesn’t make sense.”

The printer stopped.

Then every monitor went black.

Bell jerked backward.

“What happened?” Isolde asked.

A restart symbol appeared.

Bell hit the keyboard.

“I didn’t do that.”

The system rebooted. When the desktop returned, the Northstar scoring application was gone.

So was the cache directory.

Bell’s face drained.

“Remote wipe.”

“Can they do that?”

“They’re not supposed to.”

Isolde gathered the printed pages.

“Can they erase the printer history?”

“Probably.”

“Then we leave.”

They walked directly to Captain Shah’s legal office. Corvin arrived two minutes later. Mercer locked the door. The four of them spread the pages across a conference table.

Corvin stared at the dollar figures.

“This isn’t a bounty list.”

“How do you know?” Isolde asked.

“Because Northstar’s contract has performance incentives. Predictive validation milestones.”

Shah looked at him.

“Explain.”

“The software predicts which candidates are likely to fail, withdraw, or require remediation. If its predictions hit certain accuracy thresholds, Northstar gets additional payment at each validation stage.”

Isolde looked down at her name.

“So sixty-eight thousand dollars is what?”

“Maybe the modeled value of your outcome toward a contract milestone.”

Mercer swore softly.

Shah’s face tightened.

“The contract summary didn’t mention individual monetary weighting.”

“Technical annex,” Corvin said. “Restricted to the evaluation board.”

“You signed it.”

“Yes.”

“And you didn’t think attaching dollar value to candidate outcomes was a problem?”

“It wasn’t supposed to influence outcomes. The predictions were sealed before candidates arrived. Independent evaluators were supposed to score them normally.”

Isolde tapped the manual-adjustment list.

“But if Thane knew the predictions…”

Corvin finished the thought.

“He could make the model look more accurate.”

“And trigger payments to Northstar.”

Nobody spoke.

Shah separated the printed pages into piles.

“We need to preserve this properly.”

“Can we send it to oversight now?” Isolde asked.

“We can report suspected procurement misconduct. But we need to be precise. These pages prove there were hidden dollar values and score changes. They do not yet prove Arkwright changed outcomes to enrich a family member.”

“What about the land lease?”

“Strong conflict indicator. Still not proof of intent.”

Mercer pointed to the access column.

“Most adjustments use his administrator ID.”

Shah nodded.

“That’s evidence. But credentials can be shared or misused. We need the audit server.”

“Building Nine,” Isolde said.

Corvin’s phone rang.

He answered, listened, and looked at Isolde.

“Northstar’s field engineer just arrived at the front gate.”

Evan Rusk was thirty-eight, thin, tired-looking, and offended by nearly everything at once. He carried two laptops and an equipment case marked NORTHSTAR READINESS SOLUTIONS.

“I received an automated tamper alert,” he said in the communications room. “Someone accessed a recovery directory.”

Bell stood beside Isolde.

“I did.”

Rusk looked at her as if she had confessed to breaking a laboratory instrument.

“That directory contains proprietary data.”

“It contained our personnel names,” Isolde said.

“And contract-validation metrics.”

“Why was my name there three months before I arrived?”

Rusk stopped.

He looked at Corvin.

“That’s not possible.”

Isolde placed the printed line in front of him.

Rusk read it twice.

“Where did you get this?”

“You just said it was proprietary data.”

“I mean your record. Candidate rosters aren’t supposed to enter the prediction environment until thirty days before cycle start.”

“Mine was there ninety-three days before.”

Rusk sat down slowly.

“That would require a pre-load list.”

“Who can provide one?”

“Program manager. Site administrator. Contracting officer’s representative.”

“Names.”

Rusk hesitated.

“Northstar program manager is Lydia Kess. Site administrator is Colonel Arkwright.”

“And the contracting representative?”

Rusk looked at Corvin.

“Major Drake was acting COR during the first six months.”

Isolde turned.

Corvin did not flinch.

“I told you I was on the board.”

“You didn’t tell me you controlled contract data.”

“I didn’t preload you.”

Rusk raised both hands.

“Wait. Pre-load lists leave server receipts.”

“Where?” Isolde asked.

“Central Northstar archive.”

“Can you access it?”

“Not without authorization.”

“Can Lydia Kess?”

“Yes.”

“Call her.”

Rusk gave a short laugh.

“You don’t order my program manager.”

“No. But you can tell her we have printed evidence of personnel data being used outside the stated window and that your software remotely wiped a government workstation after we found it.”

His face changed.

“The wipe is automatic security policy.”

“Then she’ll want to explain that too.”

Rusk stepped outside to call.

Ten minutes later he returned.

“She’ll join a secure video conference at eighteen hundred.”

“Good.”

Rusk packed his laptop, then paused.

“There’s something else.”

Isolde waited.

“The dollar amount beside your name is unusually high.”

“Why?”

“Because the model assigns value based partly on confidence and strategic importance.”

“Strategic importance of what?”

“Of validating a prediction.”

“What did it predict about me?”

Rusk looked genuinely uncomfortable.

“That you would challenge command authority, trigger a disciplinary event, and fail the cycle.”

The room went silent.

Isolde thought of the morning square.

Thane provoking Ames.

Her stepping forward.

The Command Challenge.

Someone had predicted not just failure, but conflict.

“How?” she asked.

Rusk shook his head.

“I don’t know. The model ingests prior evaluations, assignments, education, disciplinary history, leadership comments—”

“I have no disciplinary history.”

“Then there must have been another data source.”

Bell looked down at the printout.

At the far edge of Isolde’s row was a field they had ignored.

SOURCE PROFILE: VIRELAINE LEGACY.

Isolde read it once.

Then again.

May you like

She knew only one person who might understand what that meant.

Her father.

Related Stories

Other posts