Idempotent action ledger
The idea
Each outside action is written with an idempotency key before it runs and settled after. A crash between the two leaves it 'unknown', and the model checks the outside system instead of repeating the action.
- The problem
- A crash between doing an action and recording it could repeat a push or a message.
- Why it matters
- Each side effect happens at most once, and uncertain ones stay visible.
- Where it stands
- In production as of
A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.