Vacancy Migration Workflow Decision
Canonical migration owner
svc-vacancies is now the canonical migration owner for vacancy-specific schema changes.
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
svc-vacancies is now the canonical migration owner for vacancy-specific schema changes.
migrate:all includes VacancyYes, migrate:all now includes npm --prefix services/svc-vacancies run migrate.
Operators should run npm run migrate:all to apply all migrations, including vacancy schema changes.
Individual vacancy migrations can be run with npm --prefix services/svc-vacancies run migrate.
The following vacancy-related migrations remain in svc-tenders/migrations because they are mixed with accommodation concerns:
0005_vacancies_accommodations.sql (legacy shared vacancy/accommodation)0042_vacancy_accommodation_context.sql (adds accommodation_mode to vacancies, accommodation_need to vacancy_applications, listing_context to accommodations)0043_vacancy_accommodation_declaration_details.sql (adds details_json to both vacancy_postings and accommodation_listings)0044_add_details_json_to_views.sql (adds details_json to vacancy and accommodation views)These are not transferred because they affect both vacancy and accommodation schemas, requiring coordinated migration ownership.
Public vacancy discovery (GET /vacancies, GET /vacancies/:id) remains compatibility-backed, falling back to legacy vacancies table when projection-backed vacancy_postings are not available. This migration ownership cleanup does not change public-read behavior.
svc-tenders to svc-vacancies as (0001)svc-vacanciesmigrate:all to include svc-vacanciessvc-tenders/migrations