Residue Inventory

Migration Ownership Residue

• Residue Item: Accommodations migrations still in svc-tenders/migrations

• Where It Lives: services/svc-tenders/migrations/ (files like 0005_vacancies_accommodations.sql, 0042_vacancy_accommodation_context.sql, etc.)

• Why It Still Exists: Mixed with vacancy migrations or legacy shared concerns, preventing clean transfer claim

• Safe to Clean Now: No, mixed migrations require separate handling

• Notes: Pure accommodation migrations transferred to svc-accommodations in Sprint 85

• Residue Item: Vacancies migrations still in svc-tenders/migrations

• Where It Lives: services/svc-tenders/migrations/ (files like 0005_vacancies_accommodations.sql, 0042_vacancy_accommodation_context.sql, etc.)

• Why It Still Exists: Mixed with accommodation migrations or legacy shared concerns, preventing clean transfer claim

• Safe to Clean Now: No, mixed migrations require separate handling

• Notes: Pure vacancy migrations transferred to svc-vacancies in Sprint 86

svc-tenders Compatibility Residue

• Residue Item: Accommodations contracts in svc-tenders

• Where It Lives: services/svc-tenders/src/accommodation/contracts.ts

• Why It Still Exists: Compatibility residue for older callers

• Safe to Clean Now: No, still supports compatibility

• Notes: Not active route host

• Residue Item: Accommodations read repositories in svc-tenders

• Where It Lives: services/svc-tenders/src/accommodation/ownerReadRepository.ts, compatibilityReadRepository.ts

• Why It Still Exists: Compatibility hosting for older callers

• Safe to Clean Now: No, still in use

• Notes: Root compatibility in repository.ts

• Residue Item: Vacancies contracts in svc-tenders

• Where It Lives: services/svc-tenders/src/vacancy/contracts.ts

• Why It Still Exists: Compatibility residue

• Safe to Clean Now: No, still supports compatibility

• Notes: Not active route host

• Residue Item: Vacancies domain and read models in svc-tenders

• Where It Lives: services/svc-tenders/src/vacancy/domain.ts, readModel.ts, readRepository.ts

• Why It Still Exists: Compatibility for public-read fallback

• Safe to Clean Now: No, still active for compatibility

• Notes: Root residue in repository.ts

• Residue Item: Vacancies compatibility repositories in svc-tenders

• Where It Lives: services/svc-tenders/src/vacancy/compatibilityReadRepository.ts, compatibilityApplicationRepository.ts

• Why It Still Exists: Supports compatibility cleanup work

• Safe to Clean Now: No, separate from route-host retirement

• Notes: Public-read still compatibility-backed

KES Shared Backbone Residue

• Residue Item: KES shared Kafka/backbone workers

• Where It Lives: services/svc-tenders/src/kafka/kesOutboxRelay.ts, kesDomainEventConsumer.ts, kesEventConsumer.ts, kesDlqReplay.ts, kesOutboxPoisonReplay.ts

• Why It Still Exists: Intentional shared event-backbone retention after KES HTTP/runtime extraction

• Safe to Clean Now: No, this is later backbone-transfer work, not host-retirement residue

• Notes: svc-kes is already the canonical KES runtime; these files remain because the shared backbone is still hosted here on purpose

• Residue Item: Kafka idempotency store used by KES consumers

• Where It Lives: services/svc-tenders/src/kafka/idempotencyStore.ts

• Why It Still Exists: Shared infra for consumer safety and replay handling

• Safe to Clean Now: No, generic shared infra

• Notes: Not evidence of an active svc-tenders KES host

Root Orchestration Residue

• Residue Item: TENDERS_SERVICE_URL as fallback in gateway seams
• Where It Lives: services/api/src/routes/*.ts (ICPI_SERVICE_URL ?? TENDERS_SERVICE_URL, etc.)
• Why It Still Exists: Intentional fallback for rollback
• Safe to Clean Now: No, preserves rollback capability
• Notes: Correct shared shell behavior

Seed/Setup Residue

• Residue Item: Scripts use API gateway paths
• Where It Lives: scripts/butkhuzi-*.js, etc.
• Why It Still Exists: Correct, scripts target API not direct services
• Safe to Clean Now: No change needed
• Notes: No old-host direct targeting found

Stale Source-Tree JS Residue

• Residue Item: Compiled JS files under src
• Where It Lives: Various src/*.js files (e.g., services/api/src/config.js)
• Why It Still Exists: Expected build artifacts
• Safe to Clean Now: No, not an error
• Notes: Code scan shows 242 files, but these are compiled outputs

Docs/Runbook Residue

• Residue Item: Historical KES prep docs with former path references
• Where It Lives: Older docs/KES_*.md prep/hardening notes and historical audit logs
• Why It Still Exists: Some docs intentionally preserve pre-extraction state, but they need explicit historical labeling once paths are deleted
• Safe to Clean Now: Yes, for source-of-truth docs; historical audit logs should stay intact
• Notes: Sprint 100 adds current-state clarification so deleted services/svc-tenders/src/kes/* paths are no longer presented as live topology