KES Primary And Fallback Status
Current Primary Runtime
The active primary KES runtime is:
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
The active primary KES runtime is:
http://localhost:4025This is the runtime now targeted by the live API seam through:
There is no longer an active colocated KES HTTP fallback runtime in svc-tenders.
The old KES HTTP host slice was retired in Sprint 97 by removing:
registerKesRoutes.ts pathkesRouteSupport.ts pathsvc-kes is now the only canonical KES HTTP/runtime host.
Current seam shape remains unchanged:
KES_ORCHESTRATOR_SERVICE_URL ?? TENDERS_SERVICE_URL ?? "http://localhost:4020"Route family remains:
/api/v1/kes/orchestrator/*The API now treats KES_ORCHESTRATOR_SERVICE_URL=http://localhost:4025 as the required active KES target in practice.
The fallback branch remains in code only because the shared gateway contract has not been rewritten in this sprint.
The old rollback window is now closed.
There is no supported env-only rollback to an old colocated KES HTTP host because that host has been retired.
Operational rollback now means:
KES_ORCHESTRATOR_SERVICE_URL=http://localhost:4025svc-kesNo gateway route rewrite was introduced by the retirement step.
First-cut KES runtime success does not mean KES now owns the full event backbone.
These remain shared on purpose:
That shared-backbone truth does not invalidate svc-kes as the active primary HTTP/runtime surface.
svc-auth startup issues remain environment/tooling caveats, not evidence of KES runtime drift:4025 and start svc-kes in normal multi-service dev flowssvc-tenders still keeps shared backbone/runtime, but not the retired KES HTTP host or the removed KES compatibility layer