FIELD NOTE / X
Idempotency does not prove convergence.
The short film, the complete written thought, and the evidence behind it.
The X conversation link will follow its public release.
Idempotency does not prove convergence.
Video caption
Idempotency does not prove convergence. Did the same request repeat, not is the customer healthy. Deduplication is a guard, not the verdict. #EricFieldNotes
Full written post / accessibility read
Suppose the GPU placement API correctly deduplicates a repeated operation key. It returns the original receipt every time. The route and serving process may still be catching up.
Stable identity protects against duplicate initiation. It does not establish that traffic reaches the new pool, that old workers drained or that billing reflects the final placement.
Write the convergence contract before the move: which records must agree, by when, and which source owns each. Keep unknown while any required readback is stale or absent.
Replay the same key in a disposable fixture and confirm no duplicate command. Then hold one downstream system back and require the workflow to stay pending. That catches a false completed flag.
#EricFieldNotes
Four-beat scene transcript
1. Idempotency does not prove convergence.
Suppose the GPU placement API correctly deduplicates a repeated operation key. It returns the original receipt every time. The route and serving process may still be catching up.
Visual: One accepted command can leave three systems in different states.
2. The receipt answers a smaller question.
Stable identity protects against duplicate initiation. It does not establish that traffic reaches the new pool, that old workers drained or that billing reflects the final placement.
Visual: Did the same request repeat, not is the customer healthy.
3. Define terminal state.
Write the convergence contract before the move: which records must agree, by when, and which source owns each. Keep unknown while any required readback is stale or absent.
Visual: Read placement, route, serving and account mapping.
4. Test the accepted outcome.
Replay the same key in a disposable fixture and confirm no duplicate command. Then hold one downstream system back and require the workflow to stay pending. That catches a false completed flag.
Visual: Deduplication is a guard, not the verdict.
Research and claim limits
The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.