Chapter 13: Production
On Sunday the Rennick office was quiet enough for Noor to hear the air moving through the vents. A cleaner had left the chairs at uneven angles. She straightened hers and found a coffee stain on the desk where Bem had set down the spare cup.
She opened Delia’s complaint from her assigned case history. The reconciliation was closed, but the production trace remained available for follow-up. A banner reminded her that access would be recorded against the case.
Noor selected the trace and waited.
The first screen showed the request arriving at 06:15 on 21 August. She expanded the associated object and found the earlier serving time, 06:14:19. Both were still there. The trace did not explain the inversion; a line marked the object as retrieved from a prepared batch, but the retrieval event had no readable account of how it had acquired its timestamp.
She opened the batch reference. July. Cohort 44. Position 1,006 against a funded ceiling of 110.
Below it was a later event: explanation category selected. The event carried a renderer identifier.
Noor took out her notebook and compared it with the release identifier she had copied from the build history. The strings matched.
She checked again, character by character. Then she opened the release record through the archive and compared the date of promotion. It covered Delia’s application. The trace showed that this release had rendered her notice.
The selected category concerned address continuity.
Noor expanded the category details. The trace named an input field and a confidence value presented to the renderer. It did not show how the value had been calculated, whether the tested minimum was active, or what other factors the Bell had used to place Delia in the cohort. The category-selection event followed the availability of the quarterly rank.
She leaned back. Someone had left a bowl of wrapped sweets at the end of the row. The red wrappers shifted in the draft from the vent.
Delia’s address history was continuous. Noor had checked it for the complaint and had signed a reconciliation that conceded the fact while preserving the decision. Now she could connect the false address statement on the original notice to the renderer release that had consumed her component.
The trace exposed neither the ranking calculation nor the production confidence setting.
Her notebook had room for both facts. She wrote them on separate lines.
A chair scraped behind her. Bem stood at the next desk, unwinding his scarf.
“You’re in early,” he said.
“It’s nearly ten.”
“On a Sunday.” He looked toward the dark windows, then pulled his terminal awake. “I left my access request half done. Renny said I could finish it today and take the time back.”
Noor closed the release record but left Delia’s trace open. Bem had seen her screen before; shutting everything at once would draw more attention than the case itself. He was not looking at it anyway. He was trying to free the end of his scarf from a zip.
“Did you get the renderer access?” she asked.
“Pending. I attached the wrong induction certificate.” He held up the scarf. “I’m doing well with fastenings this week.”
Noor smiled. She copied the trace’s event references and renderer identifier into her notebook. The case name was already in the assignment system; she left it off the page.
Bem sat down. His terminal chimed three times in quick succession.
“Oh, come on,” he said to it.
“Another form?”
“The form wants my manager’s confirmation that I’ve read the instructions. The instructions say I need access before I can see the instructions.”
“There’s a public copy on the induction page.”
He looked across at her. “The one dated last year?”
“It’s still the one they link.”
“That seems optimistic.”
“It’s Vantage.”
He found the copy and began reading. Noor returned to the category event. She wanted the precise wording of the input field, but when she opened the detail panel, a restriction notice appeared. The trace exposed the category and event order; the underlying model inputs required separate authority.
She did not request it. A denial would add nothing useful, and an approval would not necessarily expose the weight assigned to the field.
Instead she opened Delia’s original notice from the complaint file. The displayed sentence was familiar enough to recite. She read it anyway, then placed it beside the category record.
The notice presented the address interruption as the reason for refusal. Delia’s verified address record showed no such interruption. The trace showed the selected category and the deployed renderer, but not the source of the faulty address assertion.
Noor copied the notice reference. Her pen paused above the paper.
“What are you working on?” Bem asked.
“An old complaint.”
“Has it reopened?”
“No.”
He turned slightly in his chair. “I thought closed cases came back through the rota.”
“This one’s still in my case history.”
“But has anyone assigned it back to you?”
Noor capped her pen. Bem’s expression was curious, not hostile. She had shown him how to find an appeal address during his second week, when he was afraid to ask Renny the same question twice. He was waiting for the kind of answer she would have given him then.
“I’m checking the trace against the build,” she said.
“For the address defect?”
She looked at him. “How do you know about that?”
“It was on the anomaly list Renny discussed at induction. Not the person’s name. The time inversion and the address complaint came up together.”
Of course. The escalation had contained all eleven inversions, and the team had been told what to do if similar cases appeared.
“I wanted to see which renderer handled it,” she said.
“Did you find a fault?”
“I found the version.”
Bem waited. Noor shifted the notebook under her hand.
“That doesn’t tell you much by itself,” he said.
“No.”
“Are you sending it to Renny?”
“I haven’t finished.”
He faced his screen again. After a moment he said, “Sorry. I’m not trying to inspect your work.”
“It’s a fair question.”
But she had already given him the answer she thought would end the conversation. She opened the case notes and added a short entry: Reviewed production trace; renderer identifier and category event recorded for follow-up. It was true, and too small for what she had found.
At the end of the row, a printer woke and fed out a single blank sheet. Bem collected it, checked both sides and put it in the recycling tray.
Noor closed the trace. She would take the event references and dates to Dov, then work out what could be corroborated outside Vantage. Delia’s name would stay with Cass unless he chose otherwise.
As she packed her bag, Bem said, “The instructions mention unusual access.”
Noor’s hand stopped on the zip.
“They mean mine,” he added quickly. “For the renderer request. It says to report anything I don’t understand, even if it turns out to be normal.”
“That’s what the form is for.”
“Right.” He touched the edge of the recycled sheet. “I keep thinking I ought to know the difference before I report it.”
“You won’t always.”
She left him at his desk. In the lift, she opened her notebook to check that she had copied the renderer identifier correctly. Her handwriting had tightened halfway through the line, but every character was legible.
Bem finished the induction page twice. The first time, he read the words without taking much in. The second, he stopped at the reporting section.
Record what you observed. Do not infer intent.
He had seen Noor’s export progress bar on Friday, though not its contents. The warning had appeared briefly when he passed her desk. Today she had returned to a closed complaint and checked a production trace against a build. She had said the case was still within her history. He had no reason to think that was untrue.
He also remembered the anomaly list: eleven timing inversions, escalated and closed. He had been told closure meant the threshold for further action had not been met. He had assumed somebody had found an explanation.
The coffee on his desk had developed a skin. He carried it to the tap, rinsed the cup and came back. His access request was still open on one side of the screen. On the other, he opened the observation form.
The first box asked for a category. He chose access pattern: uncertain. The next asked for the system and approximate time.
He typed:
Large build archive export observed Friday morning. Today Noor Abadi said she was comparing a closed complaint’s production trace with a renderer build. She said the complaint remains in her case history. I did not see the exported files or the trace contents.
He read it back. “Large” was his impression from the progress window; the system would have the actual size. He changed it to export warning observed. He added that he had asked Noor whether she had found a fault and that she had said she had found the version.
The form offered a field for suspected impact. He left it blank.
He could ask her again tomorrow. She might explain, and he could avoid putting her name into a queue watched by people neither of them knew. But the induction page said prompt reporting allowed the review team to compare an observation with ordinary access records. Waiting for an explanation was also a choice about what to leave unreported.
Bem pressed SUBMIT.
A receipt appeared with a reference number and a line telling him not to investigate further. He saved the number in his induction notes. The form did not tell him whether anyone else had reported the export, or whether the system had already marked it for review.
He returned to the renderer request. This time, when the form asked for proof that he had read the instructions, he attached the certificate with the correct date. The request moved to pending.
Across the room, Noor’s chair was still straight beneath her desk. Bem looked away and began the next induction exercise. It asked him to classify three sample notices by defect. The first had a timestamp before its application, and the answer choices offered no place to write I don’t know why.