← All threads

Data

What happened, and how do we record it faithfully?

Events as atomic data units — the event log as committed record. Events are data; at best they become information once structured. They are not knowledge.

15 published articles

From Synthesizing Knowledge
00
Synthesizing Knowledge
Series preview — how explicit information becomes something we can act on
From Modeling Truth
01
Before You Model
What Genesis established — synthesis with links, for readers new or returning
02
Domain Events Are Not CRUD
Storage verbs force interpretation where the log should speak plainly
From Genesis
03
Capturing Truth — and the Schema-Evolution Myth
How truth gets into a system in the first place, and why doing it wrong shows up as schema churn
04
Atoms of Truth
What the irreducible units of truth are — and why the most important ones go unrecorded
06
Captured Evidence
Tier one — what the log can claim, and what it cannot
07
Four Capture Modes
Tier 1 contains only events
11
When Facts Are Wrong
Corrections, amendments, and compensating transactions
14
Why Atomicity Matters
How far an artifact sits from the irreducible — and why that governs what may depend on it
27
One Authority Per Invariant
The principle that makes distributed systems consistent makes organisations accountable
29
One Authority Per Invariant — At Scale
How the single writer principle applies when multiple product teams share cross-cutting obligations
31
Event Sourced Science
Why the ML reproducibility crisis is an architecture problem
32
From Immutable Events to Immutable Software
Why a foundation of atomic ground truth makes software cheap to extend in the age of AI
33
Immutable Infrastructure
Why containers are a statement about truth
34
The Unified Theory
One problem. One axiom. Six facets. Zero coincidences.