Getting an Event Model into code Added in 1.11.0
Get an Event Model into a Critter Stack codebase as C# and drive the spec-driven loop from it: importing an eventmodelers.ai board export with bobcat import-event-model (stub records in Features/{Chapter}/{Slice}.cs, one EventModelDefinition per chapter, and with --specs one WolverineFx.Bobcat spec per board example), reviewing and correcting the inferred aggregates and stream starts (--aggregate, --starts-stream, --chapter, --json callout codes), giving each aggregate a strong-typed identifier (--strong-typed-ids), or declaring the model by hand with the JasperFx.Events fluent EventModelBuilder; registering it, the declared-versus-derived merge and describe-event-model, the whole loop from board to green specs (import, spec project, wolverine scaffold, implement), and re-importing after the board changes (the additive merge, its callouts, and what to do when the board gives an existing slice a new event: slice-differs-from-board, merged-slice-roles).
Use when the user has an Event Model (a board export or a whiteboard session) and wants code, specs or a Stoat plan from it, or asks how the SDD workflow fits together. The curated .emodel.yaml format is retired.
Skill details
- Skill name:
critterstack-sdd-event-model-import - Applies to:
wolverine,marten,polecat,fisher - Tags:
sdd,bobcat,event-modeling,emlang,eventmodelers,import,scaffolding,stoat,specifications,EventModelDefinition - Added in: 1.11.0
- License: Proprietary. Copyright JasperFx Software LLC.