ESDM CLI

The model drifts the moment it leaves the room.

Teams share the vocabulary of Domain-Driven Design and Event Sourcing, but not their artifacts – slide decks, whiteboard photos, and wiki diagrams that nobody trusts six months later. ESDM gives the model a first-class home – files next to the code, checked by a linter, in a format every tool can read.

• Drift becomes visible. A pull request that renames an Aggregate has to update the model, or the linter fails the check.
• Gaps show up early. An Aggregate without Events, a Command nobody issues, a Read Model fed by no projection – the linter flags them.
• Built for tools, and for AI. A fixed schema and a named vocabulary, plain enough for LLMs to read and write.

apiVersion: schema.esdm.io/core/v1
kind: command
name: acquire
scope:
  domain: library
  boundedContext: cataloging
  aggregate: book
data:
  type: object
  properties:
    title: { type: string }
    author: { type: string }
    isbn: { type: string }
  required: [title, author, isbn]
publishes:
  - acquired

A Command in ESDM – what it acts on, the data it carries, and the Event it publishes. esdm lint checks it against the schema and the modeling rules.