Epic: Centralize ES Command Emission #159

New issue

Open

opened 2026-03-15 23:08:35 +00:00 by freemo · 0 comments

freemo commented

2026-03-15 23:08:35 +00:00

Owner

Background and Context

ES commands are currently emitted inline in 8+ methods across Manager, GameObject, and StorageMachine, each with duplicated guard-check-rescue boilerplate. Some methods in both Manager and StorageMachine emit ES commands for the same operation, creating a double-emission risk. This Epic extracts all ES emission into a single EventSourceService class with unified configuration checking, retry logic, logging, and error handling.

This is distinct from the EventSourcingMiddleware (issue #110) which is a future ActionPipeline middleware. The EventSourceService is a standalone service that can be used now and later wrapped as middleware when the pipeline is ready.

Demonstrable Outcome

All ES command emission flows through EventSourceService. No inline Sequent.command_service.execute_commands calls remain. Double-emission is prevented.

Acceptance Criteria

EventSourceService class handles all ES emission
Zero inline Sequent calls in Manager/GameObject/StorageMachine
Unified logging, retry, and error handling
Write-mode-aware behavior (respects es_write_mode)

## Background and Context ES commands are currently emitted inline in 8+ methods across `Manager`, `GameObject`, and `StorageMachine`, each with duplicated guard-check-rescue boilerplate. Some methods in both Manager and StorageMachine emit ES commands for the same operation, creating a double-emission risk. This Epic extracts all ES emission into a single `EventSourceService` class with unified configuration checking, retry logic, logging, and error handling. This is distinct from the `EventSourcingMiddleware` (issue #110) which is a future ActionPipeline middleware. The `EventSourceService` is a standalone service that can be used now and later wrapped as middleware when the pipeline is ready. ## Demonstrable Outcome All ES command emission flows through `EventSourceService`. No inline `Sequent.command_service.execute_commands` calls remain. Double-emission is prevented. ## Acceptance Criteria - `EventSourceService` class handles all ES emission - Zero inline Sequent calls in Manager/GameObject/StorageMachine - Unified logging, retry, and error handling - Write-mode-aware behavior (respects `es_write_mode`)