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 persistenceshared Kvary event backboneshared runtime / operational infrastructure
That split is real and should stay explicit during extraction prep.
KES-Owned Event And Persistence Pieces
-
VERIFIEDKES-owned: extracted KES HTTP/runtime surface under services/svc-kes Notes:svc-kesis now the canonical KES HTTP/runtime host after retirement of the old colocatedsvc-tendershost. -
VERIFIEDKES-owned: Notes: Contains the KES SQL, row mapping, payment-note handling, integrity hash-chain logic, and append/read behavior in the canonical extracted runtime.