Loading module
Resolving locale, route permissions, and workspace projection.
Resolving locale, route permissions, and workspace projection.
Текущая область: Гость
Категория: 10_normative | Версия: v1.0.0
Владелец: DOCUMENT_CUSTODIAN | Цикл пересмотра: 90 дней
Утверждающий орган: GOVERNANCE_ADMIN
Портал документации доступен только для чтения. Редактирование и mutation endpoints отключены.
Платформа Kvary изначально создана на грузинском языке. Там, где существует грузинская версия, именно грузинский язык является авторитетным для UI платформы, документации и юридического толкования.
Переводы на другие языки предоставляются только для удобства. Отдельные записи и flow могут изначально существовать на других языках и иметь собственный source/legal locale, но там, где доступна грузинская версия, для формулировок и толкования на уровне платформы приоритет имеет грузинский текст.
Метаданные неполные: Document ID, Version, Status, Owner Role, Last Review Date, Next Review Date, Change Log
Correct gateway route family used throughout:
/api/v1/kes/orchestrator/*Checked routes:
GET /api/v1/kes/orchestrator/cases?page=1&pageSize=1GET /api/v1/kes/orchestrator/control-planeGET /api/v1/kes/orchestrator/process-mapGET /api/v1/kes/orchestrator/suggestions?stakeholderId=11111111-1111-4111-8111-111111111111&limit=1PUT /api/v1/kes/orchestrator/process-mapPUT /api/v1/kes/orchestrator/process-mapPOST /api/v1/kes/orchestrator/casesAuth behavior stayed consistent with the verified parity path:
401 missing_bearer_tokenThis window used the same proven auth contract shape as Sprint 94.
Environment caveat:
svc-auth still could not be used in this local Docker-backed execution because of the pre-existing native sharp runtime mismatch/auth/me was provided by a contract-compatible auth responder so the KES/gateway auth path could be exercised without changing auth semanticsPost-cutover responses matched the expected first-cut KES runtime behavior:
200200200200 with an empty set for the chosen stakeholder fixture200201No gateway-specific route-shape issue appeared. No auth-path regression appeared. No KES-runtime mismatch appeared in the checked set.
This cutover validates first-cut KES extracted-runtime parity only.
It does not prove that these pieces have become KES-local:
Those remain shared backbone concerns outside the first-cut KES ownership boundary.
No blocking anomaly was found.
Observed differences remained expected runtime noise only:
snapshotAtupdatedAtcaseIdRollback was not needed.
Rollback path remained simple during the window:
:4020KES_ORCHESTRATOR_SERVICE_URL unset or pointed back to http://localhost:4020That rollback method was preserved even though the window stayed on svc-kes.