Butkhuzi Legacy Retirement Decision
Rollback Window Closure Decision
Decision: CLOSE rollback window now.
Rationale:
- Primary runtime
svc-butkhuzihas been stable since Sprint 79 live cutover (March 13, 2026). - No rollback incidents have occurred in the stabilization period.
- Parity verification confirmed in Sprint 78, live observations in Sprint 79 showed no mismatches.
- Ownership hardened in Sprint 81, establishing clear primary/fallback boundaries.
- Migration ownership transferred to
svc-butkhuziin Sprint 82. - Team confidence in primary runtime is established.
Why not keep temporary:
- Indefinite fallback drift avoided; stabilization period exceeded 2 weeks.
- Legacy residue removed to prevent future confusion.
- Primary runtime proven reliable.
Retirement Approval
Approved: Yes, legacy Butkhuzi hosting retired now.
Remaining Blockers: None.
Execution: Legacy host slice removed from svc-tenders in Sprint 82.
What Was Removed
services/svc-tenders/src/butkhuzi/directory (contracts, validation, repository)services/svc-tenders/src/routes/registerButkhuziRoutes.tsservices/svc-tenders/src/routes/support/butkhuziRouteSupport.ts- Butkhuzi route registration in
services/svc-tenders/src/server.ts - Butkhuzi methods from
services/svc-tenders/src/repository.ts - Butkhuzi imports and instantiations in server setup
What Remains
- Gateway proxy in
services/api/src/routes/butkhuzi.ts(unchanged) BUTKHUZI_SERVICE_URL ?? TENDERS_SERVICE_URLseam (unchanged)- Auth behavior (unchanged)
- Shared identity expectations (unchanged)
- Seed/setup scripts using API gateway (unchanged)
Migration Ownership Status
- Canonical Owner:
svc-butkhuzi - Migration Files: Transferred to
services/svc-butkhuzi/migrations/0009-0012.sql - Migration Script: Added to
svc-butkhuzipackage.json - Root Migrate: Updated to include
svc-butkhuzi
Gateway/Auth Behavior Status
- Unchanged as required.
- No gateway/auth rewrites performed.
- Shared shell contracts preserved.