Chapter 5: The Dependency
The meeting room’s window had been warm when Noor leaned against it. By the time Deployment reached its fourth slide, the glass was hot through her shirt.
She moved to a chair. Around the table, people watched a list of releases advance down the wall. Someone had muted the presenter’s microphone while he took a call; his mouth moved in a small window above the slide, and no one made an effort to tell him.
Renny sat two seats away, working through messages. Bem had brought a notebook and was writing down every release number.
Noor touched the edge of her own tablet. The escalation remained closed. She had checked it that morning, although there was no reason for the disposition to have changed.
The presenter came back on the audio. “Sorry. That was the school.”
Renny looked up.
“I’ll keep this short,” the man said, and opened a shared deployment list.
It was the same list engineers used to check which components were due for maintenance. Noor usually searched it for reconciliation changes and ignored the rest. The entries moved too quickly to read in full, but she saw recon.explain and, indented beneath it, a consumer she did not recognize.
ante.justify
“Could you go back?” she asked.
The presenter stopped scrolling. “Which one?”
“The explanation component.”
He returned to the entry. Noor read it again. ante.justify appeared under DEPENDENT SERVICES, alongside three familiar applications.
Renny’s chair shifted.
“Is there a version change?” Noor asked.
“Routine rebuild. Same interface.” The presenter enlarged the entry. “Why?”
“I didn’t know Ante was using it.”
“Half the services use it.”
“Not half,” said a woman at the far end of the table. “Don’t give them ideas.”
A few people laughed. Noor kept her eyes on the wall.
The entry showed a dependency and a release identifier. It did not show what Ante sent into the component, what came out, or where that output went. Still, the name shared the prefix of the source path on Delia Mott’s object. Noor wanted the presenter to open the service details. She also wanted to avoid making that request in a room that included Renny.
“Is there an owner listed?” she asked.
The presenter tapped the name. A panel opened with a team identifier and an address for automated build notifications.
“That’s a mailbox,” Noor said.
“It’s the one they’ve given us.”
“Could you open the manifest?”
“You can get it from the release record.” He glanced at the time. “We’ve got two more items.”
“Right. Thanks.”
He moved on. Noor wrote the release identifier in the margin of the agenda. Bem was watching her.
“What does it do?” he whispered.
“The component? Formats an explanation from the fields a service sends it.”
“I thought the Bell wrote those.”
“The Bell calculates decisions. Different services prepare the text.” She kept her voice low. “At least, that’s the division on the diagrams.”
Bem looked at the wall again. “And Ante?”
“I haven’t found out.”
Renny’s phone vibrated against the table. He turned it over, glanced at the message and excused himself. Noor watched him go, then made herself pay attention to the presenter’s remaining slides.
When the meeting ended, Bem closed his notebook.
“You wrote that component, didn’t you?”
“The first production version.”
“Does that mean you can look inside anything that uses it?”
“No. They call an interface. I can see the interface and the published build records.”
“Even if the service is restricted?”
“The logs are separate from its data.”
He considered that. “I’m still learning which doors are doors.”
“So am I.”
At her desk Noor opened the release catalogue. The manifest was available to her engineering role, just as the presenter had said. It listed recon.explain as a dependency of ante.justify, with a version range and dates for the builds. There was no source code for Ante and no description of its purpose beyond JUSTIFICATION SERVICE.
She followed the link to an older release. Then another. The dependency appeared in each one she opened, going back years.
Renny returned while she was comparing dates. He set his phone beside his keyboard and came to her partition.
“You asked about Ante.”
“I saw a dependency on my component.”
“Your old component.”
“I still maintain the interface.”
He looked at the screen. “Did you get what you needed?”
“I found the manifest.”
“That’s not an answer.”
She almost smiled. “I don’t know yet.”
He rested his hand on the partition. “The escalation’s closed, Noor.”
“The build catalogue isn’t.”
For a moment he said nothing. Across the floor, a printer began feeding a long run of paper.
“You’re allowed to read the catalogue,” he said. “I’m not telling you otherwise.”
“Good.”
“I am asking you to be careful what you conclude from a name.”
She thought of ante/q3/cohort_44 in the notebook at home. “Do you know what it means?”
“No.” He took his hand away. “And I need you on the queue this afternoon. We’re behind.”
After he left, she saved the release identifiers to her ordinary work notes and returned to reconciliation. The first case concerned a missing transport notice. She checked the print log, found the kiosk fault and wrote a request for a duplicate. The next three were equally ordinary.
At six, she looked up and found the office thinning around her. Bem had gone. Renny was still at his desk, jacket on, speaking into his phone.
Noor closed her queue and took the train home.
The courtyard fan was running when she opened the flat door. Its loose mounting gave a short scrape every few turns, followed by a pause long enough to make her think it had stopped.
She put rice on the stove, changed her shirt and carried her tablet to the kitchen table. There was one chair opposite hers. Its seat held a folded drying rack she had been meaning to put away.
The build catalogue accepted her login. Noor searched for the earliest release in the manifest and opened its public engineering record. The page showed compilation times, dependency checks and a set of test results. She knew the layout well enough to skim past the green status marks.
One fixture was called quota_exhausted. Another was plausibility_floor.
She selected the first. The catalogue gave her a test identifier, an execution time and a pass result. The underlying fixture was restricted.
The second gave her even less: a name and a check against the explanation component’s output. No sample sentence, no threshold, no account of what the test considered plausible.
The rice boiled over. Noor lifted the pot off the ring and stood with it in her hand while starchy water hissed on the metal.
She ate at the table, scrolling through successive builds between mouthfuls. The same fixture names recurred. Some releases added others; some ran a shorter suite. She opened the documentation for her own component and checked what callers could supply: fields, labels, confidence values, a selected template. The interface accepted those values. It did not determine whether the caller had good grounds for them.
When she had written the first production version, the task had been to make notices consistent across services. A reviewer had complained that one department’s letters read like clinical notes and another’s like parking tickets. Noor had built a way to turn structured fields into sentences that passed the Charter’s formatting requirements. The services supplying those fields retained responsibility for their accuracy.
She put down her spoon.
That division had seemed clear on the diagram. It was less useful beside plausibility_floor.
She fetched the notebook from beneath the appliance manuals and copied the two fixture names, the release identifier and the dependency. Then she drew a line between ante.justify and recon.explain.
A connection, she wrote beneath it. Not an output.
Her phone lit with a message from Sabeen: Did you ask about the lift part?
Noor had meant to call the housing line at lunch. She typed an apology and promised to call in the morning. A moment later Sabeen replied: Ask which part.
Noor sent back a tick and returned to the build page. She searched for Delia Mott’s case number. Nothing appeared. The catalogue was not a case database; it would never contain her name or application.
The envelope would.
Noor opened her work notes and reviewed what she had already seen on Delia’s object. The source reference and batch identifier were visible; the metadata link had refused her role. She had inspected the timing fields for the escalation, but she had not examined every field in the production envelope. Some might be accessible through her reconciliation view even if the source metadata was not.
She wrote envelope beneath the fixture names, then added Delia’s case number. The pencil had gone blunt. She turned it and pressed harder.
The fan scraped again outside. Noor closed the notebook, but left it on the table where she would see it before work.