Skip to content
CAI
Software that uses CAICheck a score

kickstarter/event-sourcing-rails-todo-app-demo

51.0

Adequate · 10 November 2026

686

lines of production code

Ruby

primary language

10

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

This system is an educational demonstration of an event-sourced architecture for managing to-do lists and items. It implements a command and reactor pattern where user actions generate domain events that are persisted and processed asynchronously to trigger side effects. The application includes a custom code generation tool to scaffold commands, events, and reactors, supported by a database schema that tracks state changes for the aggregates.

Features

Add custom code generation tool

A new executable script at bin/generate has been added to the project. This Ruby-based tool allows developers to scaffold new Commands, Events, and Reactors by providing a file path, automatically creating the necessary directory structure and populating the files with pre-defined templates for each type.

bin · high confidence

Added database schema for Todo and TodoItem entities

The database now includes tables for managing to-do lists and individual to-do items. Specifically, the schema introduces \todo\_lists\ (with name and timestamps), \todo\_list\_events\ for tracking changes to lists, \todo\_items\ (with name, due date, and completion status), and \todo\_item\_events\ for tracking changes to items. This provides the underlying data structure for the todo list feature.

db · high confidence

Introduce event-sourced architecture for TodoList and TodoItem aggregates

Adds an event-sourcing foundation for managing TodoList and TodoItem entities. The change introduces a base event class (Lib::BaseEvent) that automatically applies state changes to aggregates and dispatches events to registered reactors (both synchronous and asynchronous via Sidekiq). Specific events (Created, NameUpdated) are defined for TodoList and TodoItem, enabling the system to track and replay state changes for these aggregates.

ruby · medium confidence

Introduces a command and reactor pattern for TodoList and TodoItem

The application now uses a command pattern to handle TodoList and TodoItem creation and updates, generating domain events (e.g., \TodoList::Created\, \TodoList::NameUpdated\) which are then dispatched asynchronously via \ReactorJob\ to trigger side effects like sending a getting started email. This introduces a new \Lib::Command\ mixin and \Events::Dispatcher\ to manage the flow from command execution to event processing.

app/models · high confidence

Behavioural changes

Updated project documentation and added license

The repository now includes an MIT license file (MIT-LICENSE) and the README has been replaced with a description of an Event Sourcing demo application for educational purposes, rather than standard setup instructions.

(repo-wide) · high confidence

Test coverage

Added tests for TodoList and TodoItem models

Added new test files for the TodoList and TodoItem models, covering the creation of todo lists and items, as well as updating list names.

test · high confidence

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

How this codebase got here

Score

  • CAI 48 → 51 (+3.1)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

Lenses

  • Code Health 76 → 76 (+0.0)
  • Architecture 69 → 69 (+0.0)
  • Maturity 74 → 74 (+0.0)
  • Readiness 62 → 62 (+0.0)
  • Security 32 → 38 (+6.8)
  • Domain Modelling 100 → 100 (+0.0)
  • Accessibility 54 → 54 (+0.0)

Resolved (1)

  • Documentation: no installation or build instructions (README.md)

Architecture

  • Unchanged — 0 containers · 1 contexts · 0 edges

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

Survey your own repository

kickstarter/event-sourcing-rails-todo-app-demo 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.

About this page

  • The score is its most recent published measurement, taken on 10 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit 43e6d4ec260a22a0e5fcbed06b4f1ae318810a7f — the exact code this score is about.
  • Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
  • Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.4+preprod-464a0040a931.