Menu

Writing

Notes on building systems that can account for themselves.

Engineering-led, not marketing-led. If a post doesn't teach you something you can use whether or not you ever adopt Cratis, it shouldn't have been written.

Essay · 10 min

Give it a vague codebase and it produces vague code, faster.

Assistants are a multiplier on the structure they work inside — including when that structure is bad. On unstated conventions, contract drift, state that has forgotten its own history, and why a rule without teeth isn't a rule.

Selected writing

· Event modeling · Screenplay

Event modeling with Screenplay: a model you can compile · Script to stage, Part 20

The .play language, compiler diagnostics and a model an assistant can propose changes to.

 · Agentic development · Specifications

AI across the Cratis stack: corpus, CLI and MCP · Script to stage, Part 25

Where assistants meet model contracts and operating tools, and the difference between tool access and authority.

 · Privacy · GDPR

Personal data in an event log: PII and crypto-shredding · Script to stage, Part 13

Subject-key deletion, what remains in the log and the other copies of personal data to account for.

 · Operations · Workbench

Chronicle Workbench: a browser UI for your event store · Script to stage, Part 16

Inspecting the running store, following a failed partition and distinguishing reads from changes.

 · First hour · Templates

Getting started with Cratis: templates, samples and tools · Script to stage, Part 26

From a scaffolded application to registering a name, seeing it in React and inspecting its event.

More engineering writing at blog.cratis.io, or subscribe via RSS. If there's something you'd want us to write about, tell us.