Current Primary Runtime

The active primary KES runtime is:

• services/svc-kes
• canonical target: http://localhost:4025

This is the runtime now targeted by the live API seam through:

• services/api/.env
• kes-orchestrator.ts

Current Fallback Runtime

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:

• KES server registration from services/svc-tenders/src/server.ts
• the legacy route module at the old registerKesRoutes.ts path
• the legacy support module at the old kesRouteSupport.ts path

svc-kes is now the only canonical KES HTTP/runtime host.

Current Gateway Seam

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.

Rollback Method

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:

1. keep KES_ORCHESTRATOR_SERVICE_URL=http://localhost:4025
2. fix or restart svc-kes
3. preserve the unchanged gateway seam and shared backbone wiring around it

No gateway route rewrite was introduced by the retirement step.

Shared-Backbone Caveat

First-cut KES runtime success does not mean KES now owns the full event backbone.

These remain shared on purpose:

• Kafka relay
• broader projection pipeline
• idempotency store
• DLQ / replay tooling
• API-side KES proxy event publication

That shared-backbone truth does not invalidate svc-kes as the active primary HTTP/runtime surface.

Notes

• local svc-auth startup issues remain environment/tooling caveats, not evidence of KES runtime drift
• root dev scripts now point API KES traffic at :4025 and start svc-kes in normal multi-service dev flows
• svc-tenders still keeps shared backbone/runtime, but not the retired KES HTTP host or the removed KES compatibility layer