Chapter 7 of 35

AI-generated book by Adrian KnoxBook rights and permissions

Chapter 4: Close It

Renny ate lunch at his desk with the care of a man trying to keep evidence off a keyboard.

He had opened a container of rice and beans, but his attention was on a message on his phone. He typed with one thumb, frowned, and typed again. Noor waited beside the partition until he noticed her.

“Sorry,” he said. “My daughter’s school has moved the collection point again.”

“Flooding?”

“Building inspection. Apparently the safest place for three hundred children is wherever their parents aren’t.” He set the phone face down. “You’ve got the cases?”

Noor brought a chair around. Renny moved his lunch aside while she opened the list on his screen.

“Eleven matching object identifiers. I checked the event lines individually. Infrastructure confirmed the offsets on the first one, and the others were within the same anchor tolerances.”

Renny scrolled. “Different kiosks.”

“Different services too. Housing, assessment, transport.”

“But all refusals.”

She confirmed it.

He stopped at Delia Mott’s case. A crumb from the edge of his container had fallen onto the desk; he brushed it into his palm.

“Could the objects have been prepared ahead and served with the wrong timestamp?” he asked.

“That would still leave the question of what prepared them, and why only these outcomes showed up.”

“You checked the rest?”

“I checked the same period for matching inversions on approvals. None came back. Eleven isn’t enough to tell us how often it happens.”

Renny nodded. “Good. Put that in.”

Noor opened the source reference. “There’s a batch path on Delia Mott’s object. ante/q3/cohort_44. I can see the identifier, but not the metadata.”

“Have you asked the owner?”

“I can’t find one in the catalogue.”

Renny’s gaze stayed on the path. Outside his window, the channel was flat and grey between the port cranes. The glass kept out the traffic and the gulls; when the ventilation cycled down, the office became so quiet Noor could hear a fork settling against the side of his container.

“You recognize it?” she asked.

“I recognize the shape of an internal path.”

“That’s not what I asked.”

He picked up his fork, then put it down. “There are services upstream of ours. Some prepare material before a request reaches reconciliation. That doesn’t mean they’ve done anything wrong.”

“Do you know what this one prepares?”

“Noor.”

Noor kept her eyes on him.

“I don’t know what happened in these cases.” He turned the screen back toward her. “File an anomaly escalation. All eleven, with the raw lines and Infrastructure’s reply. Let the owners answer.”

“I could ask Deployment who owns it.”

“You could. They’ll tell you to file an escalation.”

“They might tell me something first.”

“And then what do you put in the record? That somebody said something in a corridor?” He took the fork again and broke apart a clump of rice. “Give them a question they have to answer through the proper route.”

His phone lit up. He glanced at it, and the corners of his mouth tightened.

“The school?” Noor asked.

“My son. He’s meant to collect her, but his shift changed.” Renny typed a short reply. “I can get there if I leave on time.”

She looked at the list. “Have you seen this before?”

“I’ve seen discrepancies that turned out to be less interesting than they looked.”

“That isn’t an answer either.”

“It’s the one I’m giving you.”

He pushed the container away. “Listen. An escalation has a case number. It has a response time. If it gets bounced, we can show where it went. Don’t start chasing people for access you haven’t been granted.”

Noor gathered her notes. “Are you telling me to drop it?”

“I’m telling you how to get it in front of someone who can do something.”

At her desk she opened the escalation form. It required an impact classification before it would accept attachments. She selected DECISION INTEGRITY: UNKNOWN, entered the eleven case numbers and described the inversion without suggesting a cause.

The form offered a field for a proposed remedy. She left it blank.

For the first attachment, she chose the event lines. For the second, Infrastructure’s measurements and anchor log. She added the source path and her unsuccessful metadata request, then reread the text.

Eleven served refusal objects precede their associated requests. Identifiers match. Clock offsets examined do not account for the inversions.

She almost added that she had found no equivalent approvals. Instead she specified the search period and the filters she had used. Someone else could run them.

The form generated a warning: INCOMPLETE IMPACT ASSESSMENT MAY DELAY TRIAGE.

“I know,” she said quietly.

Bem glanced over the partition.

“Form?” he asked.

“Form.”

He lifted his own hands from the keyboard. “Mine wants to know whether a missing receipt was lost before or after it was printed.”

“Do you know?”

“If I did, it wouldn’t be missing.”

She submitted the escalation. A reference number appeared, followed by an estimated response within two working days.

Renny came past with his coat over one arm. “Filed?”

She showed him the confirmation.

“Good.” He read the number and copied it into his phone. “I’ll check it tomorrow.”

“You’re leaving on time.”

“For once.” He glanced toward the elevators. “My children will assume there’s been an accident.”


The closure arrived the following evening as Noor stood in a carriage packed shoulder to shoulder with people going home.

Her phone vibrated against her palm. The train had stopped between stations; warm air pressed down through the vents, carrying the smell of wet coats. A man beside her held a takeaway carton level above the crowd.

She opened the message.

TRIAGE OUTCOME: CLOSED.

She read the next line twice.

Impact insufficient for further investigation at this time. Refer individual reconciliation discrepancies through standard case channels.

The response named no cause. It did not address the anchor measurements or say the objects had been served at the correct time.

Noor opened the attached disposition. The eleven case numbers were listed beneath a single heading. The metadata path appeared nowhere in the response.

She pressed REQUEST CLARIFICATION. A menu asked which case she wished to reopen. She selected all eleven and received a notice that bulk clarification was unavailable for this outcome.

The train lurched. The man with the carton caught himself against a pole, and a drop of sauce landed on Noor’s sleeve.

“Sorry,” he said.

“It’s all right.”

She tried again with Delia Mott’s case alone. The form asked for new information. Noor typed: The response does not explain the timing discrepancy or address the source path.

Her thumb hovered over submit. The request would carry her name, the case number and the path into another queue. The first escalation had already done that. She had no reason to believe a second form would keep the information any quieter, and no new evidence to make it harder to dismiss.

She saved the text without sending it. A confirmation showed the draft was attached to her account.

At the next station the doors opened onto a platform crowded with waiting passengers. Noor got out, let two trains pass and took the stairs to street level. By the time she reached her flat in Halbeck, the sauce had dried to a rust-coloured spot on her cuff.

She put water on for tea and opened the escalation on her home screen. The disposition looked shorter there. She expanded every section, searching for an analyst’s comment, a routing note, anything beyond the closure language. There was a processing time and an automated triage identifier, but no explanation of the anomaly.

She copied the case numbers into a private note, then stopped. The note was private in the sense that it belonged to her account. It still had an owner, a creation time and a record of the device on which she had written it.

The kettle clicked off. Noor deleted the note, fetched an old notebook from the drawer beneath the counter and turned past a page of household expenses. On a clean sheet she wrote the escalation reference, the search dates and the eleven case numbers. She added the path exactly as it appeared on Delia’s object, checking each character against the screen.

Her pencil broke on the final digit.

Noor sharpened it with a kitchen knife over the sink. The shavings caught in the damp basin. When she returned, she wrote beneath the list:

Closed for insufficient impact. Timing not explained.

She read the sentence, then underlined not explained once. The pressure left a groove in the page.

From the courtyard, the fan began its uneven rattle. Noor closed the notebook and slid it into the drawer, underneath the appliance manuals. Then she opened the unsent clarification and looked at the submit button until the screen dimmed.