At twenty past six in the morning, the arrivals ticketing office had opened only one window. Beatrice Auma took Juma’s boarding pass, checked his ID and pulled up his booking.
“KT is not a travel agent,” she said before he finished the question. “Kito Transfer Desk is an internal reissue queue. It was used yesterday after the aircraft swap.”
Naima stood behind the privacy line. “So K. Travel Desk on our receipts isn’t a person?”
Beatrice looked at her. “I can discuss Juma’s booking only. I can check yours when you request your own session.”
“That’s enough,” Juma said. “Please show me my history.”
Beatrice printed the first page of the reissue record. The original flight had a larger aircraft. At 21:02 the system recorded an equipment change and cancelled the seat assignment. At 21:14 his booking entered KT-21 with other records needing reaccommodation.
“That matches the coordination token we saw in baggage,” Juma said.
“Likely. Baggage inherits the reprotection state.”
“Does KT-21 mean we were a group?”
“No. It’s an operational transfer queue. The bookings can be completely unrelated.”
Naima let out a victorious breath, but Juma would not enlarge the conclusion. “When was G-17 added?”
Beatrice scrolled. “Here.”
The screen showed a later event: `11:28 disruption group mapped — station EM-04`.
Juma asked for a printed history. Beatrice printed only the section attached to his booking. “This includes the user credential and time.”
“Who is EM-04?”
She hesitated.
Her supervisor, Malik, emerged from the back office. “That is an internal operations code. We cannot discuss employee credentials with passengers.”
“I don’t need anybody else’s records,” Juma said. “This event is on my booking. I need to know whether it was automated or a staff action.”
Malik read the page. “Station operations credential.”
“So not Kito Transfer Desk?”
“Not the automated reissue.”
“And EM-04?”
Malik’s jaw tightened. “Ezekiel Mrema was the station manager on duty. That is all I can say.”
Naima said, “So he made us G-17.”
Juma turned to her. “My booking shows his credential mapped my record. We have not inspected all twenty-one.”
Malik lowered the shutter halfway. “This complaint belongs with the duty manager, not the ticketing counter. Beatrice, end the session.”
“One last question,” Juma said. “If G-17 is removed from my booking, is the ticket itself still valid?”
Beatrice glanced at Malik. He did not answer.
“It is my booking,” Juma said. “I’m asking for my ticket status.”
Beatrice checked the screen again. “Fare, route and reissue entitlement remain valid under KT-21. G-17 is what blocks processing.”
“Enough,” Malik said.
Beatrice closed the record, but the printed history was already in Juma’s hand.
Naima requested her own booking review. Malik refused a shared session and told her to take a number. Ten minutes later, she received her own history with KT-21 and a G-17 event. She did not give Juma the paper. She showed him only the timestamp she chose to share. It fell within the same minute as his.
They sat on an arrivals bench and compared Juma’s printout with his baggage slip. KT-21 had entered legally the night before because of the aircraft swap. G-17 arrived the next morning under a station credential. Two layers the gate and baggage process had treated as one object were now separated.
“So the travel-agent conspiracy is dead,” Naima said.
“Yes.”
“And Mrema’s shortcut is starting to appear.”
“Starting. We still don’t know the reason he used.”
“You can destroy anybody’s cliffhanger with precision.”
Juma filed the printout. He now had something stronger than a theory: his own booking history containing an event, timestamp and credential. He had not needed access to an airline database.
Before the shutter closed completely, Beatrice called after him. “Mr Kilonzo.”
She allowed him to request an audit print of fields belonging only to him. The new sheet separated original booking source, equipment-change event, KT-21 entry, disruption mapping and last station action. KT-21 had changed neither fare basis nor passenger ownership; it was a queue tag. G-17, by contrast, was a restriction layer carrying a station credential.
That distinction explained the baggage records. The nighttime token had coordinated reissue work. It was not evidence that the passengers had been a conduct group since the previous evening.
When Naima entered her own session, Juma sat far enough away that he could not see her screen. When she returned she shared only three fields: equipment swap, KT-21 and G-17 mapping.
“Don’t write my PNR,” she said.
“I don’t need it.”
They compared times verbally and found the mappings occurred within the same minute. It was not proof of all twenty-one records, but it was a second independent example of the process.
Malik later gave them a leaflet for the formal operational audit. He stressed that ticketing staff had no authority to decide misconduct. Juma agreed and asked that his customer note state the question precisely: `why valid KT-21 reissue was overlaid by G-17`.
Malik entered the wording. Even the interrupted session now generated an official record of the question that still needed an answer.
Outside, Juma called Musa at work. His equipment samples were still in the irregular cage. Musa asked whether he should continue preparing an alternate video pitch for the cooperative.
“Yes,” Juma said. “But don’t promise them the panel will reopen. Possible is not the same as approved.”
Juma also checked the time zone printed on the audit history. Beatrice confirmed it used local station time, not UTC. He wrote that in the margin. A small time-zone mistake could reverse the order of events in a later review.
Malik added one more note: Juma had requested no passenger data other than his own. That distinction mattered. His complaint was an operational explanation request, not an attempt to turn grievance procedures into backend access.
Beatrice’s final answer remained the simplest description of the problem.
“If you remove G-17, your booking is still valid.”