Epic: Event sourcing configuration and enablement #22

New issue

Open

opened 2026-03-14 23:53:09 +00:00 by freemo · 0 comments

freemo commented

2026-03-14 23:53:09 +00:00

Owner

Background

Two independent configuration systems exist: ServerConfig (YAML) for the core event store, and a separate Configuration singleton for the unused alt store. The config.yaml file has event_sourcing_enabled: false but no ImmuDB connection parameters.

Demonstrable Outcome

A single configuration path via ServerConfig with documented defaults in config.yaml. All ImmuDB parameters are present with sensible defaults.

Acceptance Criteria

config.yaml includes all ImmuDB parameters with defaults
Configuration singleton removed (absorbed into ServerConfig)
Specification documents all config keys
Unit tests verify config loading and validation

## Background Two independent configuration systems exist: `ServerConfig` (YAML) for the core event store, and a separate `Configuration` singleton for the unused alt store. The `config.yaml` file has `event_sourcing_enabled: false` but no ImmuDB connection parameters. ## Demonstrable Outcome A single configuration path via `ServerConfig` with documented defaults in `config.yaml`. All ImmuDB parameters are present with sensible defaults. ## Acceptance Criteria - [ ] `config.yaml` includes all ImmuDB parameters with defaults - [ ] `Configuration` singleton removed (absorbed into `ServerConfig`) - [ ] Specification documents all config keys - [ ] Unit tests verify config loading and validation