Distributedsystems

Worker A holds epoch 41 and pauses. The authority grants epoch 42 to worker B. The resource accepts B and rejects the resumed worker A.

Claude Code restarted. Its old MCP worker kept writing.

A replacement worker does not silence the old one. Fence stale MCP writes at the resource boundary before a resumed job overwrites newer work.

Claude Code's audit trail put the effect before the approval

Clock skew made an approved Claude Code run look unauthorized. Wall-clock timestamps cannot prove the order of a production agent’s approval, dispatch, commit, and revocation.

A timed-out Claude Code MCP write enters an unknown state, checks an operation journal, and either verifies the existing effect or retries with the same idempotency key

Treat a timed-out MCP write as an unknown outcome

A timed-out MCP write may have failed, succeeded, or finished after the client gave up. Use an operation journal and effect lookup before Claude Code retries it.