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
Decision: CLOSE rollback window now
The old colocated KES HTTP host in is approved for retirement now, and that retirement has been executed in Sprint 97.
svc-tendersRetirement is approved now because the previously stated cutoff conditions were already satisfied:
svc-kes is the active primary KES runtime through the live API seam.svc-kes as the primary KES host.svc-tenders KES host was no longer the canonical runtime in code, config, or operator guidance.The legacy KES HTTP host slice removed from svc-tenders was:
registerKesRoutes.ts pathkesRouteSupport.ts pathThe removed slice was the old HTTP host only.
The following were evaluated and are not blockers for deleting the old KES HTTP host:
/auth/meThose pieces are still shared on purpose, but they are not reasons to keep the old colocated HTTP route host alive.
The following still remain in svc-tenders, but they are no longer an active KES HTTP host:
The KES compatibility/delegation layer that previously remained in svc-tenders was removed in Sprint 99.
What still remains there now is shared-backbone/runtime code only, not KES HTTP-host or KES compatibility-layer code.
There is no remaining blocker for legacy KES HTTP-host retirement itself.
Remaining blockers apply only to deeper cleanup and fuller KES independence:
Legacy KES HTTP-host retirement is not the same thing as full backbone ownership transfer.
Sprint 97 retires the old HTTP host only. Shared Kafka relay, projection pipeline, idempotency, DLQ/replay, and related orchestration infrastructure remain shared on purpose.