Good point. When the receiving system durably enforces an idempotency key, rerunning with the same key is much safer than asking a person to decide. Kiso’s executionId is currently a local ledger identity; it is not automatically passed through as a remote idempotency key. I also agree that checking authoritative state after a crash could shrink the ambiguous cases. Kiso doesn’t currently define a generic reconciliation hook, so a human verdict is the fallback when neither mechanism exists. How would you handle a stale or inconclusive status query?