Choosing Storage Is Choosing What Your System Forgets

State, fact, event, record, and what an event store keeps that a current-state database forgets.

The Command Context Consistency Principle

How Event Stores and Relational Databases Guard Business Decisions

Why Your Software Cannot Explain Its Business Decisions

Make the path from command to outcome explicit in the architecture. How you store state, relational or event-sourced, is a separate decision.

Rethinking REST API Design

Go Beyond CRUD to Uncover Domain Behavior

Thinking in Events

Separating the Modeling of What Happened from the Decision of How to Store It

Simply Event Sourcing

Aggregates Were Never Required — Command Context Consistency and DCB’s Tag-Based Contract

Why the Domain Is Defined by Domain Capabilities, Not Object Models

Additive Domain Evolution Through Autonomous Capabilities

Request Processing Units and Reactors

Decoupling User Interactions from Internal Domain Capabilities

Functional Core / Imperative Shell for Agentic Coding

How Repository Structure, Feature Slices, and Project-Level Skills Guide Coding Agents Toward Self-Contained Features