KES Event Boundary Status

Current Boundary

KES now owns its core route, contract, validation, support, and persistence surface in code, but its event-driven surroundings are still split across three layers:

• KES-owned domain and persistence
• shared Kvary event backbone
• shared runtime / operational infrastructure

That split is real and should stay explicit during extraction prep.

KES-Owned Event And Persistence Pieces

• VERIFIED KES-owned: extracted KES HTTP/runtime surface under services/svc-kes Notes: svc-kes is now the canonical KES HTTP/runtime host after retirement of the old colocated svc-tenders host.

• VERIFIED KES-owned: services/svc-kes/src/kes/repository.ts Notes: Contains the KES SQL, row mapping, payment-note handling, integrity hash-chain logic, and kes_orchestrator_events append/read behavior in the canonical extracted runtime.

• VERIFIED KES-owned: KES route-triggered domain mutations through services/svc-kes/src/routes/registerKesRoutes.ts Notes: Case creation, task assignment, inspection submission, payment request/approve/settle, and case closure all land in KES-owned persistence through the extracted runtime.

• VERIFIED KES-owned: Control-plane and projection-oriented reads served by KES routes, backed by services/svc-kes/src/kes/repository.ts Notes: These are still KES-facing reads even when some of their freshness assumptions depend on shared projection flow later.

Shared Backbone Pieces

• VERIFIED shared-backbone-owned: services/svc-tenders/src/kafka/kesOutboxRelay.ts Notes: Reads kes_outbox_events, publishes to Kafka, tracks attempts, lag, poison rows, and monitoring. This is a durable delivery bridge, not KES-local request logic.

• VERIFIED shared-backbone-owned: services/svc-tenders/src/kafka/kesDomainEventConsumer.ts Notes: Consumes domain-event envelopes, applies projection writes, and manages domain-event DLQ behavior. This is broader event backbone / projection infrastructure, not just KES route hosting.

• VERIFIED shared-backbone-owned: domain-event topics and projection pipeline described in docs/EVENT_DRIVEN_ARCHITECTURE.md Notes: kes.orchestrator.domain-events and its projection tables are the meaningful downstream event-processing path today.

• INFERRED shared-backbone-owned: projection rebuild and control-plane freshness assumptions Notes: Current KES reads are still compatible with shared projection ownership. Full projection autonomy is later cleanup, not first-cut extraction truth.

Shared Runtime / Operational Infrastructure

• VERIFIED shared-infra-owned: services/svc-tenders/src/kafka/idempotencyStore.ts Notes: Generic Kafka consumer idempotency table and claim logic. Not KES-specific.

• VERIFIED shared-infra-owned: services/svc-tenders/src/kafka/kesDlqReplay.ts Notes: Operational replay tooling for the KES proxy-event DLQ.

• VERIFIED shared-infra-owned: services/svc-tenders/src/kafka/kesOutboxPoisonReplay.ts Notes: Operational recovery tooling for poison outbox rows.

• VERIFIED shared-infra-owned: API-side proxy event publishing in services/api/src/routes/kes-orchestrator.ts Notes: Publishes transport/operational events after mutation proxying. Useful, but not the canonical durable event path because it is not transactionally tied to KES persistence.

• VERIFIED shared-infra-owned: services/svc-tenders/src/kafka/kesEventConsumer.ts Notes: Handles API-side proxy events with idempotency, retry, and DLQ support. Current default usage is transport/ops-oriented rather than the primary business mutation engine.

What Stays Shared In The First KES Extraction Cut

• API gateway routing in services/api/src/routes/kes-orchestrator.ts
• Shared auth ingress and /auth/me identity resolution
• Shared KYC/signature ingress helpers described in docs/KES_SHARED_SHELL_CONTRACT.md
• Kafka idempotency store
• KES outbox relay
• Domain-event consumer and projection pipeline
• DLQ and replay tooling
• API-side Kafka transport-event producer

What Can Move Later

• Outbox relay ownership, if the team wants KES to own end-to-end durable publication
• Domain-event consumer and projection rebuild ownership
• Topic naming and projection-table ownership cleanup
• DLQ replay ownership consolidation
• Stronger KES-local control-plane freshness guarantees that stop relying on shared projection runtime

Notes

• KES already owns its canonical durable state and event log writes.
• the post-retirement KES compatibility layer inside svc-tenders has now been removed
• Shared Kafka, outbox, projection, idempotency, and replay tooling do not need to move in the first extraction cut to make runtime/bootstrap prep credible.
• Full event-backbone independence is later cleanup, not required proof for the first extracted KES runtime.