Records reconciliation desk haikuwa desk moja. Ilikuwa chumba chenye monitors tatu, printer ya laser, makabati ya files na whiteboard iliyojaa mishale ya tarehe. Mariam alifika saa nne asubuhi na kukuta Nuru tayari amesimama karibu na screen kubwa. Rukia alikuwa na notebook yake. Mwanaume aliyekuwa amevaa shati la kijivu alijitambulisha kama Hamisi Mtemi, specialist wa migration aliyekuwa amesaidia kuhamisha records kutoka mfumo wa zamani kwenda mpya.
Mariam aliposikia jina Hamisi, alifikiria marehemu mume wa jirani yake kwa sekunde, kisha akajikumbusha kuwa hapa kila jina lilikuwa mtu mwingine, si ishara.
Hamisi akasema, “Leo hatutafungua portal. Portal ni mwisho wa process. Tunataka kuona process yenyewe.”
“Good,” Mariam alisema.
Nuru akaweka karatasi mbili mezani. Kila moja ilikuwa na current code P-0417, lakini legacy household IDs zilikuwa tofauti kabisa.
“Ndiyo hii?” Mariam akauliza.
“Ndiyo,” Nuru alisema. “Rows mbili. Code moja ya current priority. Household mbili tofauti kwenye legacy system.”
Mariam alihisi moyo wake ukipiga haraka. “Basi duplicate ilikuwa real.”
Hamisi akainua kidole. “Duplicate code, ndiyo. Duplicate entitlement, bado hatujasema.”
Mariam akakaa.
Hamisi alieleza mfumo wa zamani. Priority ilihifadhiwa kwenye table moja. Payment status ilikuwa kwenye table nyingine. Household relocation profile ilikuwa na legacy ID ndefu, na printed cards zilikuwa na short priority reference iliyotumiwa na staff kwa urahisi. Wakati migration ilifanyika, prefixes fulani ziliondolewa na records zilipitia merge rules.
“Kwa nini code mbili zikawa moja?” Mariam akauliza.
“Possibilities ziko kadhaa,” Hamisi alisema. “One: typo. Two: code reuse baada ya record kufungwa. Three: merge rule ilichukua short suffix na kupoteza distinguishing prefix. Four: manual reassignment ilitumia code ya current queue badala ya legacy household ID.”
“Na hapa?”
“Hapa tunafuata timestamps.”
Nuru akaonyesha row ya Mariam. Legacy household ID yake ilikuwa LJ-MD-8841. Priority card ya zamani: BM-P-0417. Current priority: P-0417. Payment batch: BM-17. Housing receipt confirmation: Ijumaa mchana.
Kisha akaonyesha row ya pili bila jina la familia. Legacy ID tofauti. Priority reference ya zamani ilikuwa na suffix ile ile lakini prefix tofauti iliyokuwa imekatika kwenye scanned letter. Current system nayo ilikuwa P-0417.
Mariam akasema, “Hiyo familia ililipa lini?”
Nuru akasema, “Hatuwezi kukupa amount wala personal detail. Tunachoweza kusema ni kwamba wao pia walikuwa verified relocation household na walifuata offer waliyopewa.”
“Walipata unit?”
“Ndiyo.”
Chumba kikawa kimya.
Mariam aliona picha ya mlango wa B-214 kichwani, ingawa Nuru hakuwa amesema unit hiyo ndiyo ya familia ya pili. Alijua sasa ni hatari gani ya akili kutengeneza story haraka.
“Je, ni unit ambayo ningepewa mimi?”
Hamisi akasema, “Swali sahihi ni: wakati assignment yao ilifanyika, system ilionyesha priority yako katika status gani?”
“Basi tuangalie.”
Hamisi akafungua assignment history.
Tarehe ya kwanza ilikuwa kabla ya payment batch BM-17 ku-link kwa household ID ya Mariam. Payment ilikuwa imeingia housing ledger, lakini field ya allocation engine ilionyesha PAYMENT NOT LINKED. Siku mbili baadaye, priority record ya Mariam ilikuwa marked pending reconciliation. Wakati huo, current code P-0417 ilitumika kwenye row ya pili ambayo system iliona eligible.
Rukia akasema kwa sauti ya chini, “Mfumo uliona hakuna malipo.”
Mariam akamgeukia. “Lakini pesa ilikuwepo. Hiyo ndiyo tofauti ninayotaka mrekebishe.”
Rukia hakubisha.
Hamisi akafungua batch table. BM-17 ilikuwa na fourteen households. Kwenye import log, households kumi na mbili zili-link automatically. Mbili zilikuwa exception. Mariam alikuwa mmoja wao.
“Kwa nini?”
“Legacy household identifier mismatch,” Hamisi alisema. “SACCO cover ilikuwa na relocation reference inayolingana na printed card, lakini new allocation table ilitaka canonical household ID. Merge job haikupata exact match.”
“Na mtu aliona exception?”
Nuru akasema, “Exception queue ilikuwa ipo.”
“Ilifanyiwa kazi?”
“Baadaye.”
“Baada ya assignment?”
“Ndiyo.”
Mariam alishika mkanda wake wa kupimia uliokuwa ndani ya handbag. Hakuwa ameutumia siku hiyo, lakini aliuleta karibu kila mahali kwa mazoea. Alifikiria jinsi sentimita moja ikipotea kwenye measurement ya suruali, mteja angeiona mara moja. Hapa identifier ilikuwa imepotea kwenye mfumo, na matokeo yake yalikuwa nyumba.
“Nani alifanya manual reassignment?” aliuliza.
Rukia akasema, “Team ya old phase. Lakini hatujaona evidence kwamba walijua payment yako ilikuwa posted but unlinked.”
“Kwa hiyo hamsemi walininyang’anya kwa makusudi.”
“HatusSemi hivyo.”
“Na mimi sisemi.”
Nuru akaangalia Mariam. “Hiyo ndiyo muhimu.”
Hamisi akaonyesha audit trail. Assignment ya familia ya pili ilikuwa na staff approval, reservation acceptance na later handover. Hakukuwa na red flag kwamba waliingia kwa rushwa, wala kwamba walijua code ilikuwa imeshawahi kuhusishwa na household nyingine.
Mariam akauliza, “Mkiamua priority yangu ilipaswa kuwa active, mtafanya nini kwao?”
Hakuna aliyejibu haraka.
Nuru akasema, “Ndiyo reason remedy si simple reverse transaction.”
“Sitaki waondolewe.”
Rukia akamwangalia. “Hujui hata unit yao.”
“Sihitaji kujua. Kama walifuata process waliyoonyeshwa na wakapewa nyumba kwa good faith, sitaki Tunu apate mlango kwa kumfanya mtoto mwingine atoke kwenye mlango wake.”
Hamisi akaegemea kiti. “Then remedy question becomes equivalent allocation plus systemic control.”
“Systemic control gani?”
Nuru akaandika kwenye whiteboard: FREEZE SAME-FLAG REALLOCATIONS PENDING REVIEW.
“Hatuna haki ya kufreeze kila allocation,” Rukia alisema. “Tunahitaji scope.”
“Scope ni records zenye same migration/payment-linkage flags,” Nuru akajibu. “Si whole project.”
Mariam akasema, “Na records ambazo tayari watu wamehamia?”
“Review without automatic displacement,” Nuru alisema. “Remedy inaweza kuwa different kwa status tofauti.”
Rukia alionekana kutulia baada ya kusikia hilo. “Hiyo inawezekana.”
Walifuata second exception kwenye BM-17. Haikuwa P-0417. Ilikuwa family yenye legacy ID ambayo pia payment yake ilichelewa ku-link, lakini assignment yake haikuwa imehamishwa. Walipata unit baadaye. Hilo lilithibitisha kwamba linkage gap haikuleta matokeo sawa kila wakati; timing ya reassignment ndiyo ilikuwa muhimu.
Mariam akaandika kwenye notebook yake:
PAYMENT POSTED ≠ PAYMENT LINKED. PRIORITY CODE ≠ HOUSEHOLD ID. DUPLICATE CURRENT CODE ≠ PROOF OF FRAUD. REASSIGNMENT DURING GAP = REMEDY QUESTION.
“Unaandika nini?” Hamisi akauliza.
“Ninajaribu kutokurudi nyumbani na story ambayo ni rahisi kuliko facts.”
Nuru akatabasamu kidogo.
Baada ya saa mbili, walikuwa wamefika kwenye chronology ambayo Mariam angeweza kuieleza bila kupandisha sauti: aliweka deposit; SACCO ilituma batch; housing ilipokea; payment record ilikaa bila household linkage kwa sababu ya migration mismatch; allocation engine ikaona priority bila linked payment; manual reassignment ikafuata current code ambayo ilikuwa pia ime-merge vibaya; baadaye payment ika-link, lakini assignment ilikuwa tayari imefungwa.
“Hiyo ndiyo root cause?” Mariam akauliza.
Hamisi akasema, “Kwa case yako, ndiyo working finding. Lazima review sign-off ikamilike.”
“Na P-0417 ya pili?”
“Good-faith assigned household. Code collision kupitia merge/crosswalk, si evidence ya wao kuchukua payment yako.”
Mariam akavuta pumzi ndefu. Ilikuwa answer ngumu kuliko “wameiba nyumba yangu.” Lakini kwa mara ya kwanza, ilikuwa answer yenye steps.
Nuru akaanza kuandaa recommendation ya freeze kwa unresolved rows. Rukia akasema, “Kabla hatujapanua, lazima tujue kama flag hii ni rare au widespread.”
Hamisi akachuja export kwa `LEGACY-MERGE` pamoja na payment-link exception ndani ya relocation pool.
Screen ilionyesha rows zaidi ya moja.
Mariam alidhani labda tatu.
Nuru scrolls chini: “P-0417 si peke yake. Tuna rows tisa zenye flag hii.”
---