Reference docs tell you what each class does. Tutorials show you what to type. These pages explain the model the framework rests on — the dual-write trap that prompted it, the primitives it factors into, the trade-offs each choice inherits. Read them once and the rest of the surface reads like notation.
Why writing to a database and to Kafka separately is the bug your monitoring will eventually find for you — and what an outbox-pattern-by-construction framework looks like instead.
The framework's central guarantee: every action's commit is a single database transaction that touches as many domain tables as the action needs plus the eventlog outbox. They land together, or none of them do.
The two-phase lifecycle: pure construction in Phase 1, single-transaction persistence in Phase 2. Why your action code never opens a transaction itself.
Models emit events when they change; Entities don't. Why the distinction matters and where each fits.
Single-database, embedded-bits UUID, policy-axis routing — what each costs and when each is appropriate. Two axes (policy + capacity) and why splitting them matters.