Shared Shell Residue Map
Residue Inventory
Migration Ownership Residue
-
Residue Item: Accommodations migrations still in
Loading module
Resolving locale, route permissions, and workspace projection.
Resolving locale, route permissions, and workspace projection.
Current scope: Guest
Category: 10_normative | Version: v1.0.0
Owner: DOCUMENT_CUSTODIAN | Review cycle: 90 days
Approval authority: GOVERNANCE_ADMIN
Documentation portal is read-only. Editing and mutation endpoints are disabled.
Kvary platform is originally created in Georgian. Where a Georgian version exists, Georgian is authoritative for platform UI, documentation, and legal interpretation.
Translations into other languages are provided for convenience. Some records may originate in other languages and carry their own source or legal locale for a specific flow, but where a Georgian version is available, the Georgian version prevails for platform-level wording and interpretation.
Metadata incomplete: Document ID, Version, Status, Owner Role, Last Review Date, Next Review Date, Change Log
Residue Item: Accommodations migrations still in
svc-tenders/migrationsWhere 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
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
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
services/api/src/routes/*.ts (ICPI_SERVICE_URL ?? TENDERS_SERVICE_URL, etc.)scripts/butkhuzi-*.js, etc.src/*.js files (e.g., services/api/src/config.js)docs/KES_*.md prep/hardening notes and historical audit logsservices/svc-tenders/src/kes/* paths are no longer presented as live topology