Vacancy Primary And Fallback Status
Current Primary Runtime
Active primary Vacancy runtime:
services/svc-vacancies
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
Active primary Vacancy runtime:
services/svc-vacancieshttp://localhost:4023This is the runtime now serving Vacancy traffic through the live API seam.
There is no longer an active legacy Vacancy route host.
The old svc-tenders Vacancy host slice has been retired.
Vacancy gateway seam:
VACANCIES_SERVICE_URL ?? TENDERS_SERVICE_URLCurrent live Vacancy cutover state:
VACANCIES_SERVICE_URL=http://localhost:4023Gateway route family remains unchanged:
services/api/src/routes/vacancies.tsservices/api/src/routes/vacancy-postings.tsservices/api/src/routes/vacancy-applications.tsservices/api/src/routes/owner-vacancy-postings.tsservices/api/src/routes/owner-vacancy-applications.tsThe old fast rollback path through svc-tenders is closed.
Rollback now means a new code/config change rather than flipping back to a live legacy Vacancy route host.
Current public Vacancy discovery remains mixed by design.
That means:
GET /vacanciesGET /vacancies/:idstill preserve compatibility-backed behavior when projection-backed posting truth is not available.
This primary/fallback status does not change that architectural truth. The current live cutover proves extracted-runtime parity for the current mixed behavior, not projection-only public-read cleanliness.
svc-vacancies is the active primary route hostsvc-tenders Vacancy hosting is no longer present as a route hostsvc-vacancies as the
normal Vacancy runtime