What Still Remains Duplicated or Fallback-Hosted

• Contracts: services/svc-tenders/src/butkhuzi/contracts.ts (fallback copy)
• Validation: services/svc-tenders/src/butkhuzi/validation.ts (fallback copy)
• Repository: services/svc-tenders/src/butkhuzi/repository.ts (fallback copy)
• Route Registration: services/svc-tenders/src/routes/registerButkhuziRoutes.ts (required for fallback)
• Route Support: services/svc-tenders/src/routes/support/butkhuziRouteSupport.ts (required for fallback)

What Now Clearly Belongs to svc-butkhuzi

• Primary Contracts: services/svc-butkhuzi/src/butkhuzi/contracts.ts
• Primary Validation: services/svc-butkhuzi/src/butkhuzi/validation.ts
• Primary Repository: services/svc-butkhuzi/src/butkhuzi/repository.ts
• Primary Routes: services/svc-butkhuzi/src/routes/registerButkhuziRoutes.ts
• Primary Route Support: services/svc-butkhuzi/src/routes/support/butkhuziRouteSupport.ts

What Still Blocks Full Retirement

• Route Registration: Must remain in svc-tenders for fallback HTTP surface availability
• Route Support Wiring: Must remain in svc-tenders for shared parser/auth adaptation
• Repository Implementation: Must remain in svc-tenders for fallback data access
• Database Migrations: Ownership transfer not yet completed (still in svc-tenders/migrations/)
• Rollback Testing: Need confidence in primary runtime stability before full removal

Next Steps for Ownership Transfer

1. Migration Ownership: Transfer Butkhuzi migrations from svc-tenders to svc-butkhuzi
2. Dependency Reduction: Consider shared contracts package if duplication becomes problematic
3. Stabilization Monitoring: Allow 2+ weeks of primary runtime stability
4. Gradual Removal: Remove fallback files only after rollback confidence is established</content> <parameter name="filePath">d:\kvary.network\docs\BUTKHUZI_OWNERSHIP_HARDENING.md