KES Persistence Slice Status
Current Status Note
The historical persistence move is complete, and the current canonical KES persistence slice now lives in services/svc-kes/src/kes/repository.ts.
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
The historical persistence move is complete, and the current canonical KES persistence slice now lives in services/svc-kes/src/kes/repository.ts.
Sprint 90 started the move, and later extraction/cleanup sprints completed the current state:
svc-tenders/src/kes/* compatibility layer were later removedEffect:
repository.ts is no longer a KES compatibility/delegation surfacesvc-tenders no longer exposes KES persistence through TendersRepositoryNo active KES persistence surface remains in repository.ts.
What remains in svc-tenders is shared backbone/runtime only, not KES repository compatibility.
Left in place on purpose:
services/svc-tenders/src/kafkaReason:
Nothing in the persistence slice still blocks runtime/bootstrap prep, because runtime/bootstrap extraction is already complete.
What remains for later is fuller KES independence: