# Changelog

## Score

- CAI 50 → 50 (+0.0)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 71 → 71 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 51 → 51 (+0.0)
- Readiness 37 → 37 (+0.0)
- Security 100 → 100 (+0.0)

## Resolved (6)

- Documentation: no installation or build instructions (README.md)
- Documentation: no project overview (README.md)
- Documentation: no usage examples (README.md)
- Duplicate reconstitution logic. The interface EventSourcedAggregateRoot defines reconstitute as a method on the aggregate itself, while the trait AggregateRootReconstitutionTrait provides the same method but returns the aggregate. This suggests a design conflict: should reconstitution be a method called on the aggregate instance (which is impossible before the instance exists) or a static/factory method provided by a trait? The trait returns the aggregate, implying it's a factory, while the interface method implies an instance method.
- Redundant types with identical signatures. EventStream (Contract) and DomainEventStream (Domain) have nearly identical method signatures (append, newEvents, markCommited, count, id, name, version, newVersion). This duplication suggests that the contract and domain layer are not properly separated or that one is an unnecessary wrapper. The contract should define the interface, and the domain should implement it, but here both expose the same public API surface, leading to confusion about which type to use.
- Semantic ambiguity between 'id' and 'name' across related types. In EventStream, 'id' and 'name' are distinct string properties. In Transaction, 'id' and 'name' are also distinct. However, looking at EventStore.create(id: Identifier, name: string) and EventStore.load(id: Identifier), the 'id' is the primary key. In EventStream, id() returns string, but the constructor/creation uses Identifier. More critically, Transaction and EventStream have identical surface methods (id, name, version, count, events) but represent different stages (in-memory stream vs persisted transaction). This creates confusion on whether 'id' refers to the aggregate root ID or the stream/transaction ID.
