KES Legacy Retirement Decision

Rollback-Window Decision

Decision: CLOSE rollback window now

The old colocated KES HTTP host in svc-tenders is approved for retirement now, and that retirement has been executed in Sprint 97.

Retirement Approval

Retirement is approved now because the previously stated cutoff conditions were already satisfied:

1. svc-kes is the active primary KES runtime through the live API seam.
2. normal root startup/dev flow already provisions svc-kes as the primary KES host.
3. direct parity, authenticated mutation parity, and the first live env-only cutover window were already completed without a remaining HTTP/runtime mismatch.
4. the old svc-tenders KES host was no longer the canonical runtime in code, config, or operator guidance.

What Was Retired

The legacy KES HTTP host slice removed from svc-tenders was:

1. KES server registration and composition in server.ts
2. the old route module at the former registerKesRoutes.ts path
3. the old support builder at the former kesRouteSupport.ts path

Why Retirement Is Safe

The removed slice was the old HTTP host only.

The following were evaluated and are not blockers for deleting the old KES HTTP host:

• gateway seam in kes-orchestrator.ts
• auth ingress and /auth/me
• KYC/signature semantics
• API-side KES proxy publication
• Kafka relay
• projection pipeline
• idempotency store
• DLQ/replay tooling

Those pieces are still shared on purpose, but they are not reasons to keep the old colocated HTTP route host alive.

What Still Remains

The following still remain in svc-tenders, but they are no longer an active KES HTTP host:

• shared Kafka/backbone files under src/kafka

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.

Remaining Blockers

There is no remaining blocker for legacy KES HTTP-host retirement itself.

Remaining blockers apply only to deeper cleanup and fuller KES independence:

• clarifying longer-term migration ownership
• moving or re-homing shared backbone/runtime pieces only when that work is explicitly chosen

Backbone Separation Note

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.