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.

  • One governed tool gateway

    Every action goes through one gateway. It checks authorization, policy, risk, budget and approval, writes the action ledger first, and reads back each external write. A model answer can only add a requirement.

  • Read-back of external writes

    After a connector writes, it reads the object again, and the gateway compares the declared fields. A mismatch that stays fails verification.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.