Butkhuzi Migration Ownership Status
Canonical Butkhuzi Migration Owner
Owner: svc-butkhuzi
Rationale:
- Butkhuzi domain extracted to standalone runtime in Sprint 79.
- Primary runtime established as
svc-butkhuzion port 4024. - Ownership hardened in Sprint 81, clarifying primary/fallback.
- Migration ownership transferred in Sprint 82 to complete extraction.
Migration Files Location
- Current Location:
services/svc-butkhuzi/migrations/ - Files:
0009_butkhuzi_norms.sql,0010_butkhuzi_norms_blocks.sql,0011_butkhuzi_norms_i18n.sql,0012_butkhuzi_chunks.sql - Migration Script:
npm run migrateinsvc-butkhuzi - Included in Root Migrate: Yes,
npm run migrate:allrunssvc-butkhuzimigrations
What Remains in Old Host
- Migration Files: None (transferred)
- Migration References: None
- Database Tables: Tables created by migrations remain in shared database
- Data Ownership: Data owned by
svc-butkhuziruntime
What Can Be Deleted
- Old Migration Files: Already transferred, old copies can be deleted if desired (but kept for history)
- Legacy Residue: Removed in Sprint 82 retirement
Prerequisites for Transfer
- Completed: Primary runtime stability confirmed
- Completed: Ownership boundaries clarified
- Completed: Migration files copied to
svc-butkhuzi - Completed: Migration script added to
svc-butkhuzi - Completed: Root migrate updated
Transfer Execution
- Copied migration SQL files to
services/svc-butkhuzi/migrations/ - Added
migratescript toservices/svc-butkhuzi/package.json - Created
services/svc-butkhuzi/src/migrate.ts - Updated root
package.jsonmigrate:allto includesvc-butkhuzi