Chapter 17 of 35

AI-generated book by Adrian KnoxBook rights and permissions

Chapter 14: Throttle

Pell met Noor outside the redundancy room with a tablet tucked under one arm.

“Thank you for coming in,” he said.

She had been at her desk for eleven minutes. The invitation had arrived as she was opening her first case, with no subject beyond access review. She had brought her notebook, then left it in her bag when she saw Pell waiting.

The room overlooked an enclosed stairwell. On each landing a red strip marked the route down; someone had scuffed the paint beside the fourth-floor door. There was no table, only two chairs and a narrow shelf beneath the window.

Pell placed his tablet on the shelf. “I’m going to ask about several reads and an export. This is a review, not a finding.”

“How long?”

“Fourteen days are scheduled. It can finish sooner.”

“And until it finishes?”

“That depends on the access involved.”

Noor sat. Pell remained standing long enough to wake the tablet, then took the other chair. He was younger than she had expected, with a damp crease at one cuff. He turned the screen so she could see the first entry.

“Friday. Build archive export. The volume exceeded your recent baseline.”

“I needed the release history.”

“For what purpose?”

“A reconciliation question.”

“Which question?”

She could say Delia’s case. The trace was in her history, and she had added a note. She could also describe the ceiling, the category selected after the rank and the branch that had gone unused. Once she gave him those pieces, she could not choose where they went.

“There was a renderer identifier I wanted to check against the release records,” she said.

Pell looked down at the screen. “On Friday?”

“I identified the release history I needed on Friday. I checked the production trace yesterday.”

“So you exported before you had the identifier.”

“Yes. I was narrowing the possibilities.”

He entered something. “You selected records going back to 2043.”

“The component has been in use since then.”

“And the destination was removable media.”

“A card from my desk. The export contained build records.”

“Do you have the card with you?”

“No.”

It was in her flat, in the sleeve beneath a stack of utility notices. She kept her hands still on her knees.

Pell studied her for a moment. “Has anyone else accessed the files?”

She thought of Dov’s message asking her to bring the dates. She had sent him her summary of the tested branch, not the files.

“No one else has accessed the files,” she said.

He made another note. The wording had been exact. She wondered whether he heard the space around it.

“Yesterday you accessed a closed complaint.”

“It’s in my assigned case history. The trace is available for follow-up.”

“I can see that. Why follow it up now?”

“The earlier escalation didn’t explain the timestamp.”

“It was closed after triage.”

“For insufficient impact. That isn’t an explanation.”

Pell’s thumb stopped moving. Through the glass, a woman in a cleaning uniform came down the stairs carrying a folded caution sign. She paused at the third-floor landing and used her foot to open the door.

“Did you expect the build archive to explain the timestamp?” Pell asked.

“I hoped it might help me identify the renderer.”

“You said that.” He set the tablet on his knee. “What concern are you trying to resolve, Ms Abadi?”

The directness made her look at him. He did not appear angry. He appeared prepared to wait.

“The original complaint included an address defect,” she said. “I wanted to understand how that category reached the notice.”

“And did you?”

“I found the release and the category event. Not the source of the input.”

“Did you document that?”

“In the case notes.”

He read silently. Noor remembered how little she had written. Renderer identifier and category event recorded for follow-up.

“This doesn’t state a concern about the address input,” he said.

“No.”

“Why not?”

Because she had signed a document that defended the decision. Because her mother’s assessment depended on a system that could mark the household as unstable. Because a careful note would be visible to people who could close the question before she understood it.

“I hadn’t finished checking,” she said.

Pell tilted the tablet toward her again. “There was an earlier escalation on eleven timing inversions. You raised it, and it was closed. Have you found evidence that the closure was incorrect?”

“I’ve found evidence that it didn’t answer the question.”

“That’s not quite the same thing.”

“No.”

He returned to the form. Noor watched his reflection in the window: the slight movement of his hand, the red stripe on the stairwell passing through his shoulder.

“Were you asked to run these checks by your manager?”

“No.”

“Did you consult him?”

“Not before the export.”

“Have you discussed the records outside your team?”

She could tell him she had spoken to Dov about the tested branch. She could explain that the build files contained no applicant data and that she had taken care over what she sent. Pell had asked about records, though, not files.

“I’ve discussed the general issue,” she said.

“With whom?”

“Someone outside Vantage.”

“Name?”

“I’d rather not involve him.”

“I’ll record that you declined.”

She nodded.

He completed another field and set the tablet aside. “The review covers the export, the closed-case follow-up and the earlier escalation. Your account has been placed under temporary restrictions.”

“What restrictions?”

“No deployment authority, effective now. Broad build-log access is suspended. Your ordinary reconciliation queue remains available, with case access limited to current assignments.”

Noor felt for her terminal token in her pocket. It was still there.

“Can I retrieve the case notes I made yesterday?”

“Through the review team. Send a request with the case reference.”

“And the build records?”

“They’ll be assessed as part of the review.”

“You’ve already decided I can’t use them.”

“We’ve restricted access while we establish the purpose of the export.”

She looked through the glass again. The cleaner had left the caution sign on a landing, its yellow legs spread around a dark patch of water.

“Who reported me?”

“I can’t discuss review sources.”

There had been the export warning, the case access, her own escalation. Bem had seen the warning. She remembered telling him he would not always know the difference before he reported something. He had listened to her.

Pell picked up the tablet. “You’ll receive the restrictions in writing. Your manager has been notified of the operational effect.”

“Can I still speak to my team?”

“Yes. Don’t ask anyone to retrieve restricted material for you.”

“I can work within the restrictions.”

“I need to say it.”

He stood. Noor followed him into the corridor, where people moved between desks with cups and charging cables. The ordinary noise struck her after the quiet room: a laugh from the deploy row, a printer feeding paper, someone arguing mildly about a meeting time.

At her desk, she opened the build archive. The page loaded, but the search box was grey. Her deployment panel showed a small lock beside her name.

She tried her reconciliation queue. Six current cases appeared. Delia’s closed complaint did not.

Renny came over before she had opened the first case.

“Pell called,” he said. “You can work from the queue. I’ll redistribute anything that needs a deployment.”

“I can still investigate a complaint assigned to me?”

“Within the restrictions, yes.”

“And if it leads to a build?”

“Then tell me.”

Noor looked at him. “I did tell you about the inversions.”

“You escalated them. I made sure they went through.”

“They came back closed.”

“I know.” He glanced at the lock on her screen. “Don’t make me guess what you’re doing now.”

She wanted to ask what he had guessed when the escalation came back, and what he had chosen not to ask. Bem was at his desk across the aisle, looking down at a form. His ears had gone red.

“I’m checking complaints,” she said.

Renny’s mouth tightened. “All right. Check the ones in front of you.”

He left. Noor opened the first assignment. A notice had printed the wrong appeal deadline; the corrected date sat in a field she could still read. She compared it with the governing schedule, entered the amendment and sent it for reissue.

When she looked up, Bem was standing beside her desk.

“I’m sorry,” he said, too quietly for anyone else to hear. “I didn’t know it would—”

“You did what the form asked.”

“I could have spoken to you again.”

She saw him waiting for her to say it would have made no difference. She did not know that.

“The system logged the export,” she said. “Pell had more than one reason to ask.”

Bem gripped the back of the empty chair beside her. “Are you all right?”

“I can work.” She turned the corrected notice toward him. “Would you check that date? I may have missed something.”

He read it carefully, then pointed to the schedule reference. “You’ve got the old revision in the footnote.”

Noor corrected it. “Thank you.”

Bem went back to his desk. The notice was ready to send, and this time she read every line before pressing the button.


Renny left his sandwich unopened beside the keyboard. The bread had begun to darken where the filling touched it.

He pulled up the team’s access schedule and moved Noor off the next deployment rota. The change left a gap on Thursday. He filled it with his own name, then opened the retention folder for closed escalations.

Noor’s report was there: eleven inversions, the affected service references, her request for a review of the serving sequence. Attached to it was the triage response, with its threshold language and a closure date. The folder required a manager to confirm the record was complete when an associated review began.

He opened the escalation. At the bottom was the note he had added before forwarding it: Please confirm whether prepared objects can acquire a serving timestamp before an application event.

No answer to that question appeared in the closure.

Renny had seen other discrepancies over the years: a reason that changed after a reissue, a receipt whose confident language did not match the uncertainty in the case record. Individually, each had gone somewhere—the printer team, data quality, reconciliation. He had learned which route kept a case moving. He had not gathered them together.

His daughter’s school had sent him a payment reminder that morning. It sat beneath the sandwich packet. He moved both aside and checked the escalation’s attachments against the index. All eleven were present.

The retention form offered a box for manager comments. He typed, Closure did not address the timestamp question.

He stared at it. The sentence was true, but the confirmation did not ask him to reassess the decision. It asked whether the record was complete.

He deleted the comment and attached the closure response to the escalation, preserving the date and the unchanged text. Then he confirmed the record and placed it in the required retention folder.

A message from scheduling appeared: could he cover a second deployment next week? He opened his calendar and found a space. Before replying, he checked that the escalation and closure were both still visible in the folder. Then he accepted the shift.