Butkhuzi Primary and Fallback Status

Current Primary Runtime

• Service: svc-butkhuzi
• Port: 4024
• Status: Active primary Butkhuzi runtime
• Location: services/svc-butkhuzi/
• Health Endpoint: GET http://localhost:4024/health

Current Fallback Runtime

• Service: svc-tenders (legacy colocated hosting)
• Port: 4020
• Status: Temporary fallback/rollback target
• Location: services/svc-tenders/src/butkhuzi/
• Health Endpoint: GET http://localhost:4020/health

Current Gateway Seam

• Environment Variable: BUTKHUZI_SERVICE_URL
• Fallback Logic: BUTKHUZI_SERVICE_URL ?? TENDERS_SERVICE_URL ?? "http://localhost:4020"
• Current Live Target: http://localhost:4024 (via BUTKHUZI_SERVICE_URL=http://localhost:4024)

Rollback Method

To rollback to legacy fallback:

1. Update services/api/.env:
   • Either remove BUTKHUZI_SERVICE_URL=http://localhost:4024
   • Or set BUTKHUZI_SERVICE_URL=http://localhost:4020
2. Restart the API service on :4001
3. Verify smoke checks on http://localhost:4001/api/v1/butkhuzi/*

Notes

• Post-cutover stabilization is in progress (Sprint 80).
• Legacy fallback remains available to preserve rollback capability.
• Primary runtime svc-butkhuzi is established as the canonical Butkhuzi host.
• Legacy-host retirement planning is underway.</content> <parameter name="filePath">d:\kvary.network\docs\BUTKHUZI_PRIMARY_AND_FALLBACK_STATUS.md