Recovery Replay

Recovery Replay is a developer-focused Laravel tool that helps engineers reproduce, investigate, and verify retry-related data integrity defects using persisted evidence. **The problem** A Checkout request can successfully save an order and still return HTTP 503. The client cannot tell whether the operation was persisted, so it retries the same logical request. Without proper idempotency, that retry may create a second order. Looking at HTTP responses alone is not enough to determine what happened or verify that the operation is safe. **The solution** Recovery Replay makes this failure reproducible in a controlled local or testing environment. It provides vulnerable and protected Checkout and Reservation scenarios. The first attempt saves a resource and returns a simulated post-persistence HTTP 503. The second attempt retries the same logical operation. In vulnerable mode, the retry creates a duplicate resource. In protected mode, a database-backed idempotency key allows the retry to reuse the original resource. Each attempt records persistent evidence, including its run ID, attempt ID, operation ID, HTTP status, resource type, resource ID, and timestamp. An evidence evaluator examines these records to determine whether the retry created a duplicate, reused the original resource, or cannot be assessed reliably. Missing, incomplete, or contradictory evidence produces an INCONCLUSIVE result rather than a false safety verdict. **How developers use it** The Investigation Workspace lets developers examine the initial attempt, retry, and verdict; inspect the underlying evidence; and compare vulnerable and protected behavior side by side. Comparisons can be saved and reopened from Run History without executing the scenarios again. An Artisan CLI also provides machine-readable JSON reports and exit codes for repeatable verification and automated regression checks. The same replay engine supports Checkout and Reservation, and its copy-and-instrument approach has been tested in a separate minimal Laravel Invoice application. **What makes it different** Recovery Replay connects controlled fault reproduction with independently recorded database evidence and an explicit safety verdict. It helps developers move from observing an HTTP failure to establishing what was persisted, why a duplicate occurred, and whether an idempotency fix worked. IBM Bob IDE was used throughout development, reliability reviews, testing, and an evidence-backed Checkout investigation. The current MVP targets instrumented Laravel workflows; it does not claim to reproduce real network partitions or provide drop-in support for arbitrary applications.