kumiko ops

kumiko ops <subcommand>

Event-store seeds are checked-in .ts files that emit a deterministic sequence of events when applied. They’re how you ship “factory data” that has to live in the event log (vs. fixture data, which lives in test setup).

Subcommands

Subcommand	What it does
seed:new <slug>	Create a new seed file from the template
seed:status	List pending vs. applied seeds
seed:apply [--dry-run]	Apply pending seeds as events

Workflow

kumiko ops seed:new initial-admin-user
# → seeds/2026-05-21-initial-admin-user.ts
# … edit the file, add r.systemWriteAs(…) calls …

kumiko ops seed:status
# pending: 2026-05-21-initial-admin-user

kumiko ops seed:apply --dry-run   # see the events that would be emitted
kumiko ops seed:apply              # actually emit them

Idempotency

Applied seeds are tracked by filename. Re-running seed:apply is a no-op once a seed has been applied — safe to call repeatedly.

For schema-level changes use kumiko migrate; for event-level “data” changes use kumiko ops.