The mobile public help desk had been set up beneath a blue tent in the parking lot of the ward office. There were two folding tables, one small printer, and an extension cable running beneath a plastic mat. The queue had split itself into rough categories: rent complaints, relocation questions, and ordinary service forms.
Mariam arrived after getting Tunu to school early and opening the tailoring stall for one hour. Jonas had printed the comparison table in small but readable type, with a cover sheet headed QUESTIONS FOR ALLOCATION REVIEW.
There was no use of the words fraud, theft, corruption, or stolen unit.
The queue was anything but quiet. An elderly man argued about a misspelled name on a form. A woman with a baby tied to her back complained that her number had been called twice without her hearing it. Two younger men who had come about relocation spoke loudly about systems always having “their own people.” Every few minutes wind lifted one corner of the tent and made the papers on the tables shiver.
Rukia Masanja sat at the second desk wearing the same housing-office badge. When she saw Mariam, recognition crossed her face before professional calm returned.
“Mrs. Mariam. You are back.”
“I came with organized questions.”
“The portal still shows the same status.”
“I know. I do not want a portal screenshot today.”
Rukia looked at the folder.
“What exactly do you want?”
Mariam sat down and placed the first page in front of her.
“A unit-by-unit allocation audit for my priority reference and the matching codes.”
Rukia narrowed her eyes slightly. “That is not a normal help-desk request.”
“That is why I want it made formal.”
“What evidence do you have that your unit assignment was wrong?”
“I have not said it was wrong. I have payment confirmed, allocation not found, batch BM-17, older priority wording, and resident records showing the same code. I also have public observations from old-phase units whose statuses are not fully explained by the board.”
Rukia raised one hand.
“Site observation is not allocation evidence.”
“I agree.”
Rukia looked surprised that Mariam had not argued.
“Then why bring it?”
“Because I want an official comparison between the allocation table, reservation status, and handover register. I am not saying B-214 belongs to me. I want to know what sold out means inside the old queue.”
Rukia pulled the page closer.
“Who helped you prepare this?”
“Jonas from the printing shop. He organizes documents. No hacking. No system access.”
“And these resident rows?”
“Consent. Names are hidden where they are not required. Originals stay with their owners.”
Rukia read the columns one by one.
“P-0417 appears twice.”
“Yes.”
“You think that is the problem?”
“I do not know. It could be legacy mapping, a typo, duplicate coding, or a group marker. I want an official explanation.”
Rukia leaned back.
“Mrs. Mariam, the old system was migrated. Some codes were shortened.”
“Then there is a crosswalk?”
“Internal.”
“Can it be audited?”
“By internal review, yes.”
“That is what I am requesting.”
Someone behind them complained that the conversation was taking too long. The officer at the first table told him to wait his turn. Mariam felt the same pressure she had felt the first day at the housing office—the shame of becoming the person holding up a line because she wanted a complete sentence.
This time she did not retreat.
The noise rose again when the mobile desk supervisor, Mr. Mussa, came out from the main office carrying a tablet and a clipboard of stapled forms.
“What is happening here?” he asked, looking first at the queue and then at Mariam’s folder.
Rukia said, “Priority-reference duplication question. She is asking for internal allocation review, not help-desk correction.”
Mussa picked up the comparison sheet.
“P-0417 appearing twice does not prove duplicate households. Migration used short codes on some records.”
Mariam answered, “That is why I wrote cause unknown.”
“But if you bring seven people and tables like this, others may conclude the system gave one code to two families.”
“That is why the other names are hidden and my complaint does not say that.”
Mussa studied her for a moment, then turned to Rukia.
“Is the legacy crosswalk available in archive?”
“Yes, but help desk does not have full rights. We can see reference class, not the complete assignment history.”
“Check the class.”
Rukia turned the monitor slightly away from the public queue and entered the code. The screen loaded, then showed two new-system rows with different fields. Mariam did not lean forward to read information that had not been shown to her.
She waited for them to explain.
Rukia said, “One came through migration import. The other has a later activity flag.”
Mariam gripped her pen.
“What kind of activity?”
“It does not show the detail here.”
Mussa said immediately, “Do not speculate. Just state that the two flags require audit.”
Something shifted inside Mariam. For the first time, somebody within the institution was using the same discipline she had forced on herself: do not invent a reason before the record shows it.
Rukia reached for a complaint form.
“Normally we need this first.”
“Give it to me.”
“There is a limit on attachments.”
“Tell me which ones you need.”
Rukia began listing them.
Priority card copy.
Deposit receipt.
Written note stating payment confirmed / allocation not found.
SACCO batch proof.
Comparison table.
Supporting resident extracts with consent statements.
Mariam produced each document in order.
Rukia looked at her again.
“You prepared everything.”
“I am tired of carrying a story somebody else can reinterpret.”
Rukia examined the SACCO batch cover.
“BM-17. This batch entered the old ledger close to the migration window.”
Mariam felt her pulse jump, but she did not leap toward a conclusion.
“Close means before, during, or after?”
“I cannot tell you from this screen without the export.”
“Then write it as a question.”
Rukia wrote on the complaint form: verify posting sequence relative to legacy-to-new allocation migration.
“That is the language I want,” Mariam said.
“Do not teach me my job.”
“I am not. I am saying that is my question.”
Rukia exhaled and continued.
Mussa remained beside them.
“Add duplicated-reference reconciliation,” he said. “And do not write duplicate allocation unless audit confirms it.”
Rukia nodded. So did Mariam.
“What about the old letter wording?” Rukia asked.
“Compare policy or template changes. Mama Pendo has a version containing priority allocation. Newer letters do not.”
“Wording alone does not create entitlement.”
“I agree.”
“You keep agreeing today.”
“Because I do not want my case to collapse on something I never claimed.”
Rukia was silent for a few seconds. Then she entered the resident-letter comparison as supporting context, not proof of unit ownership.
Mariam felt some of the tension ease.
That was what she wanted: boundaries.
They reached the site observation.
“B-214,” Rukia said. “You photographed it?”
“From the public area.”
“You are claiming that unit?”
“No.”
“Then why mention it?”
“Because the public board says handover in progress. The seal shows inspection checked and the handover date blank. I want audit to distinguish allocated, reserved, handed over, site hold, and unassigned. The word SOLD OUT on the portal is not enough.”
Rukia slowly nodded.
“That is broader than an individual complaint.”
“My problem may be individual. The process question does not have to be.”
A woman at the first desk turned to listen, but Mariam did not name residents or turn her case into a speech for the queue.
Rukia filled in the escalation field.
“Internal allocation review,” she said. “I cannot guarantee the timeline.”
“Give me the case number.”
“If the printer works.”
The printer made a grinding noise, pulled a sheet halfway in, and stopped.
Another officer opened the tray.
“Paper jam.”
The whole queue made the same frustrated sound at once. The elderly man with the form said, “Even the printer has a queue.” A few people laughed. Others complained about the heat and the time.
Mariam almost laughed too, but it came out bitter in her chest. Her housing problem had become a portal, a spreadsheet, a batch code, and now a printer jam.
Rukia said, “I can write the number by hand.”
“I will wait for the print.”
“You have work, don’t you?”
“I do.”
“Then why waste time?”
“Because verbal reassurance is how I got here.”
Mussa looked at Rukia.
“Let the print come out. If this case enters audit, it must be traceable from the first receipt.”
Rukia said nothing.
They waited ten minutes. Mariam took a call from a customer asking about a uniform and promised to return to the stall by noon. Then she received a message from Tunu: I got to class early today.
Mariam read it twice.
When the printer was fixed, Rukia submitted the complaint. The screen spun for several seconds.
Referral status appeared:
INTERNAL AUDIT QUEUE.
“If we need additional documents, we will call you,” Rukia said.
“And the case owner?”
“Not assigned yet.”
“And the number?”
Rukia pressed print.
The printer releases one sheet: CASE BM-AUD-118.
---