The right message. Once.
An event-driven notification workflow, made visible.
- Contribution
- Automation design & workflow engineering
- Project
- Studio project
- Disciplines
- events / retries / deduplication
Run an event. Test a retry.
Interactive reconstruction · sample data
The demonstration couldn’t load. You can still explore the project below.
How this works ＋
Separate event receipt, scheduling and delivery state. A sample event identifier makes repeated submissions identifiable; retrying a failed step resumes the demonstration.
The boundary. A local simulation cannot reproduce provider limits or delivery guarantees. No messages leave this demo.
The problem worth solving.
Notifications need to survive temporary failures without sending the same message twice.
A considered approach.
Separate event receipt, scheduling and delivery state. A sample event identifier makes repeated submissions identifiable; retrying a failed step resumes the demonstration.
A local simulation cannot reproduce provider limits or delivery guarantees. No messages leave this demo.
Let’s make it work.
And make it feel right.
Build something like this
03ABX Engine
A look inside consistent visitor assignment for storefront experiments.
Product architecture & experiment tooling
05Glaze
A simple feedback interface built around a shareable identity.
Product design & web application engineering