Fundi wa karakana aliangalia saa ya ukutani, kisha screen ya server ndogo iliyokuwa kwenye rack.
“Backup rotation inaanza saa sita usiku,” alisema. “Mkiweka hold sasa, maintenance window yote itasogezwa.”
Afisa wa sheria wa kaunti aliweka preservation notice mezani.
“Ndiyo maana tumekuja kabla ya saa sita.”
Amina alisimama karibu na mlango wa office, si karibu na keyboard. Contractor alikuwa kampuni tofauti na Kituo cha Mwangaza, na data yake ilikuwa na routes za wateja wengine. Notice ilikuwa imeandikwa kwa scope ndogo: vehicle IDs zilizohusiana na Mwangaza, KJN-2 route dates, work-order references na approval fields.
Meneja wa contractor, Bwana Chege, alisoma karatasi na kukunja uso. “Hii server ina commercial data. Hamchukui image ya kila kitu.”
“Hatuhitaji,” afisa alisema. “Tunataka records zilizotajwa hapa zihifadhiwe, deletion job isimamishwe, na export yenye chain-of-custody.”
“Na mkiharibu maintenance?”
“Tutaandika impact.”
Chege akampigia wakili wake. Wakati simu ikiendelea, fundi alionyesha queue bila kufungua records za routes. Job moja ilikuwa marked **AUTO PURGE — 00:00 — archived GPS/work-order cache > retention threshold.**
Amina aliandika jina la job na saa tu baada ya afisa kuthibitisha ilikuwa ndani ya scope.
“Routine?” akauliza.
Fundi akasema, “Routine. Si deletion ya leo kwa sababu mmefika. Job imekuwa scheduled.”
“Vizuri. Hilo liingie pia.”
Chege akarudi. “Tutatii preservation, lakini tunahifadhi right ya kupinga scope na kudai costs.”
Afisa akampa sehemu ya notice ya kuandika objection. “Andika.”
Fundi akaweka purge job on hold mbele ya afisa. System ikatoa confirmation yenye timestamp. Kisha akatengeneza export ya fields zilizoruhusiwa. Hash ilizalishwa, ikaandikwa kwenye chain-of-custody receipt, na copy moja ikabaki kwa contractor.
Amina hakupokea raw database. Alipewa printout ya route rows zilizokuwa tayari filtered kwa vehicle IDs zilizotajwa kwenye notice.
Tarehe ya kwanza ililingana na malipo ya Musa ya Kijani Transfer Support.
Tarehe ya pili ililingana na video metadata day.
Tarehe ya tatu ililingana na van aliyofuata Amina kwenye barabara ya umma.
Approval field ilikuwa na account name: **D. MBELE / PROGRAM OPS.**
Amina akamwangalia afisa. “Hii ni approval ya route, si proof ya kile kilichotokea site.”
“Correct.”
Chege akasema, “Na account approval inaweza kuwa administrative batch.”
“Tutarekodi hivyo pia,” afisa akajibu.
Work orders ziliweka service descriptions: transfer vehicle, route KJN-2, pickup main campus, return/standby status. Hakukuwa na names za watoto kwenye filtered export. Hilo lilikuwa la kutosha kuunganisha route na operational authorization bila kuvuta data ya kila passenger.
Chege akasema, “Sasa mtaenda hearing kusema director aliagiza watoto wapelekwe secretly.”
Amina akatikisa kichwa. “Record inasema account yake ili-approve work orders. Motive itahitaji kitu kingine.”
“Kwa nini wewe ndiyo unaongea kama wakili wetu?”
“Sizungumzi kwa niaba yenu. Nataka kile tunachosema kiwe kile record inasema.”
Fundi alileta maintenance ticket ya usiku uliopita. Ilionyesha main campus staff iliomba sync ya GPS cache na archive rotation baada ya server warning. Request ilikuwa ya kawaida kwa wording, lakini timing yake ilikuwa baada ya inspection notice kuanza. Amina hakuita cover-up. Afisa ali-preserve ticket na metadata yake.
Chege aliandika objection ya civil liability kuhusu delay ya maintenance na privacy ya wateja wengine. Afisa aka-sign receipt ya objection.
“Sasa purge job?” Amina akauliza.
Fundi akaonyesha status: **PAUSED — LEGAL PRESERVATION HOLD.**
“Na hash?”
Ilikuwa sawa kwenye copies zote mbili.
Amina alihisi relief lakini hakupenda jinsi relief hiyo ilivyotegemea dakika. Kama notice ingefika baada ya saa sita, retention process ingeweza kufuta cache kwa utaratibu wa kawaida na kila mtu angeanza kubishana kama deletion ilikuwa ya makusudi.
Afisa akafunga envelope ya export na kuiwekea seal. “Hii inaenda county evidence storage. Amina, unapata summary fields baada ya review, si copy hii.”
“Sawa.”
Chege akasema, “At least mtu mmoja hapa anaelewa data boundary.”
Amina hakujibu kejeli hiyo. Alikuwa amefika ili kuhifadhi record, si kushinda contractor.
Walipotoka karakana, saa ilikuwa dakika ishirini kabla ya usiku wa manane. Simu ya afisa ikapokea confirmation kutoka system monitor kwamba hold ilikuwa active. Hata hivyo, screenshot ya queue iliyowekwa kwenye file ilionyesha wazi job ambayo ingeanza kama hold ingeondolewa au kushindwa.
Amina akamtumia Neema message fupi: **Preservation served. Scoped export sealed. KJN-2 work orders match transfer dates; D. Mbele account in approval field. Purge job paused before 00:00.**
Neema akajibu: **Good. No public claims tonight. Hearing tomorrow.**
Amina akaweka simu mfukoni. Hawakuwa wameiba server. Hawakuwa wamevunja password. Walikuwa wamefika na karatasi kabla mfumo haujafanya kile ulivyokuwa umeandaliwa kufanya.
Kwenye receipt ya preservation, fundi aliandika pia retention rule iliyosababisha purge: cache za zamani zilizungushwa baada ya muda fulani ili kupunguza storage. Hilo lilikuwa muhimu kwa pande zote. Kama hearing ingesikia tu “data ilikuwa karibu kufutwa”, ingeweza kuonekana kama mpango wa kuharibu ushahidi. Record kamili ilisema kulikuwa na routine purge, lakini pia kulikuwa na dispute inayojulikana ambayo ilifanya preservation iwe lazima kabla routine hiyo haijafuta material muhimu. Afisa akaweka note hiyo pamoja na objection ya contractor.
Amina aliomba work-order summary ichapishe exact approval timestamp, si jina la account pekee. Tarehe hiyo ilikuwa kabla baadhi ya transfer-support invoices kutumwa kwa wazazi, ikionyesha route authorization ilikuwa operational step iliyotangulia billing. Hata hivyo, hakukuwa na field inayosema Darius alijua kila mtoto binafsi. Amina akaandika boundary hiyo pia. Hearing ya kesho ingehitaji layered accountability, si hadithi rahisi ya mtu mmoja kubonyeza button ya siri.
Server ina job inayopangwa kufuta data saa sita usiku.
#