# Changelog

## Score

- CAI 62 → 65 (+2.5)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 76 → 76 (+0.0)
- Architecture 97 → 97 (+0.0)
- Maturity 49 → 54 (+5.3)
- Readiness 67 → 67 (+0.0)
- Security 100 → 100 (+0.0)
- Performance 75 → 75 (+0.0)

## Resolved (6)

- Inconsistent constructor signatures for EventStore implementations. The generic EventStore module defines EventSource and EventSink which take an event_store. However, the Memory::EventStore constructor takes 'events' and 'event_builder' directly, not an event_store. This breaks the abstraction if one expects to inject an event_store into these components. It suggests that Memory::EventStore is a concrete implementation that doesn't follow the same initialization pattern as the abstract concepts.
- Inconsistent method naming for error handling strategies. All retry strategies and the base ErrorHandler use 'with_error_handling'. This is consistent. However, the constructor names are 'ConstantRetry', 'ExponentialBackoffRetry', 'NoRetry', which are clear. The issue is that 'with_error_handling' is a verb phrase that implies an action, but it's used as a method that likely returns a wrapper or configures the handler. This is a minor naming convention issue but not a major inconsistency.
- Inconsistent naming for configuration accessors across modules. Both EventSourcery and Memory modules expose 'configure' (setter) and 'config' (getter). However, the main EventSourcery module also exposes 'config()' which returns the Config object, while Memory does the same. This is consistent within itself but creates a potential confusion if users expect a unified 'settings' or 'options' interface. More critically, the presence of both 'configure' and 'config' is a standard Ruby pattern, but the duplication of this pattern across top-level modules without a shared base interface makes the API feel fragmented.
- Inconsistent parameter naming in serializers. ClassName and Underscored use 'event_class', while Legacy uses '_event_class' (with an underscore, implying unused). This is a minor inconsistency in Ruby style but indicates a lack of uniformity in the serializer interface.
- Off-boarding risk: anonymized user #1
- Semantic ambiguity in method naming. 'apply' in AggregateRoot is a domain-specific term for replaying events to rebuild state. 'process' in EventStreamProcessor is a domain-specific term for handling events in a projection. However, to an external reviewer, 'apply' and 'process' might seem like synonyms for 'handling' or 'executing'. The signatures are similar (taking event classes and a block), but their intents are fundamentally different (rebuilding state vs. reacting to events). This is not a strict inconsistency but a potential source of confusion.

## New (1)

- Off-boarding risk: anonymized user #1
