Getting started with Sliceworkz EventModeling

Gettings started with the Sliceworkz EventStore

Declaring personal data as Shreddable values in domain events, configuring where the keys live, erasing a person or one category of their data, and what erasure does not reach.

What a bounded context reports about itself — lifecycle and outcome events for a monitoring stream, scoped observations for metrics and tracing, and correlation ids that follow one flow across every step.

PostgreSQL storage, several instances of one deployment, leader election, splitting front and batch instances, failure handling and the operator's controls.

The published test bases of sliceworkz-eventmodeling-testing — given/when/then for commands, aggregates, read models, automations, policies, translators, publishers, dispatchers and SQL read models — and how to run every one of them against every event storage you deploy on.

Handing each caller the narrow capability type its job needs instead of the whole bounded context

How a feature slice reaches outside its bounded context through a port the application binds, and how every call through it is timed, sorted into an answer or a failure, and attributed to the slice that made it.

How events cross the edge of a bounded context — translators bring external events in, publishers map recorded facts into the published language, dispatchers send them out.

Reacting to what happened — a to-do list worked off by an automation, or a policy that turns one event into one command — and what each costs when the work fails.