Vacancy Rollback Window Status
Is Rollback Closed
Yes.
Cutoff Condition Satisfied
Rollback closed after the normal root startup paths were updated so that:
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
Yes.
Rollback closed after the normal root startup paths were updated so that:
devdev:coredev:oneall now provision svc-vacancies as part of the expected primary startup path.
Current live Vacancy routing already points the API seam at:
http://localhost:4023But current root startup still launches:
svc-authservices/apisvc-tendersand does not launch:
svc-vacanciesSo the old Vacancy host still acts as practical safety coverage for the normal developer/operator startup path.
Implications:
svc-tenders Vacancy route host no longer needs to remain live