bringmeister/event-sourcing-with-kotlin

This is a product management system that has been refactored to use an event sourcing architecture, where the current state is derived from a sequence of persisted events. It features a message-based communication layer and includes a demo web application for visualizing the event stream and product state. The codebase is supported by updated tests that validate the new message and event handling logic.

The application now uses a message-based communication pattern, replacing the previous event-based approach. This is supported by the introduction of an EventStore for persistence, shifting the system towards an event sourcing architecture where the current state is derived from a sequence of events. Additionally, a demo web application has been added to visualize the event stream and current product state.

src/main · high confidence

The acceptance and domain tests have been updated to reflect the shift from an event-based to a message-based architecture. The tests now use \MessageBus\ and \MessageListener\ instead of \EventBus\ and \EventListener\, and \StubbedEventStore\ instead of \StubbedProductRepository\. Additionally, the tests verify that the \Product\ domain entity correctly applies events like \ProductCreatedEvent\, \MasterDataUpdatedEvent\, and \MediaDataUpdatedEvent\ to update its state, and that it throws events when handling commands.

src/test · high confidence

The Gradle build file has been updated to use modern Groovy syntax, specifically switching from the deprecated \ext\-based repository configuration to the standard \repositories\ block. Additionally, string literals in dependency declarations have been converted from single quotes to double quotes.

(dependencies) · medium confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 53 → 43 (-9.4)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 100 → 100 (+0.0)
• Architecture 69 → 69 (+0.0)
• Maturity 82 → 58 (-24.4)
• Readiness 39 → 26 (-13.7)
• Security 100 → 89 (-11.4)
• Accessibility 47 → 47 (+0.0)

• Coverage not included — suite not readable by the collector
• Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
• No exposed public API
• Test reliability not included
• early-stage repository — too little history to judge knowledge freshness
• git history depth insufficient
• git history depth insufficient
• single-maintainer — knowledge-concentration (bus factor) risk

• Dependency hygiene PARTLY measured — Maven/Gradle declarations read, no dependency graph resolved
• Documentation: no installation or build instructions (README.md)
• High interface indirection
• No dependency advisory monitoring

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

bringmeister/event-sourcing-with-kotlin was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.