# Changelog ## Score - CAI 46 → 46 (+0.3) ## Lenses - Code Health 87 → 87 (+0.1) - Architecture 84 → 84 (+0.0) - Maturity 60 → 60 (+0.0) - Readiness 34 → 34 (+0.0) - Security 40 → 40 (+0.0) - Domain Modelling 73 → 77 (+4.3) - Event-Driven 100 → 100 (+0.0) ## Resolved (6) - Inconsistent naming for value objects. 'Name' and 'Email' are used as value objects, but there is no consistent suffix or pattern (e.g., 'NameValueObject' vs 'EmailValueObject'). However, this is a minor style issue. Let's look for a stronger inconsistency. - Inconsistent repository interface naming. Some use 'IRepository' or 'IRepositoryBase', while others use specific names like 'IReadModelRepository' or 'IEventStreamRepository'. While some are specific, the base interfaces 'IRepository' and 'IRepositoryBase' create ambiguity about which one is the primary generic repository interface. - Inconsistent verb usage in EventStore methods. One uses 'AppendEventsAsync' while the other uses 'ReadEventsAsync'. While 'Append' and 'Read' are distinct actions, the naming convention for the store itself varies between 'EventStore' and 'EventStreamRepository' in the codebase (see 'EventStreamRepository' vs 'IEventStore'). - The README describes a single bounded context ('Accounts') but does not show how to create or run the Banking example with both write and read models. (README.md) - Thin analysable surface across projects - Typo in property name: 'TransationDate' is a misspelling of 'TransactionDate'. This is a clear inconsistency and error. ## New (2) - The README describes a Banking example with Customers and Accounts Bounded Contexts but never explains how to create an Account write model or run migrations, which are core event-sourcing features the document claims to cover. (README.md) - Typo in property name: 'TransationDate' is a misspelling of 'TransactionDate'. This is inconsistent with the correct spelling used elsewhere (e.g., in the anonymous type parameter list in the same codebase). ## API surface - Unchanged — 12 HTTP endpoints