# Changelog

## Score

- CAI 46 → 47 (+0.4)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 71 → 71 (+0.0)
- Architecture 98 → 98 (+0.0)
- Maturity 30 → 30 (+0.8)
- Readiness 38 → 38 (+0.0)
- Security 100 → 100 (+0.0)
- Domain Modelling 83 → 83 (+0.0)

## Resolved (6)

- Duplicate intent across concrete class and interface. 'SizeableAndMatchableString' implements 'HasLength' and 'CanCompareLength', but also defines its own length comparison methods directly. This duplicates the interface contract in the concrete class signature, creating redundancy.
- Grammatical error and inconsistency in comparison method names. 'amountIsEqualsTo' is grammatically incorrect (should be 'amountIsEqualTo'). Furthermore, the interface 'CanCompareAmount' uses 'amountIsEqualsTo' while the concrete 'Money' class uses 'isEqualsTo' for object comparison, creating two different naming conventions for similar operations.
- Inconsistent method naming for event handling lifecycle. The interface uses 'isInterestedInThis' and 'beNotifiedAbout', which are verbose and grammatically inconsistent ('is' vs 'be'). Mock implementations duplicate this inconsistency.
- Inconsistent naming for containment checks. 'ComposedClass' uses 'has'/'doesntHave' (with a typo 'doesnt' instead of 'doesNot'), while 'ClassExtractor' uses 'contains'. These perform similar logical checks on composition.
- Inconsistent verb usage for registering handlers. CommandBus uses 'addHandler', while EventBus uses 'register' for both event handlers and exception handlers. This creates confusion about whether 'add' or 'register' is the standard term for binding a handler to a bus.
- Redundant/Inverse methods. 'eventNeverHappened' is logically the inverse of 'eventAlreadyHappened'. Exposing both increases API surface without adding distinct functionality, potentially leading to confusion about which to use.
