Personal demonstration · local HTTP server · fictional operations
The request was sent.
Did it happen once?
A lost response is not proof that an operation failed. Explore a recorded test run: valid signatures, rejected changes, repeated identifiers and a timeout after the simulated operation.
Loading the recorded test report…
These controls display recorded results. They do not run the server, send requests or contact a provider. Download the code to reproduce the checks locally.
Choose a test case
Test evidence
The report must load before results can be displayed.
No result loaded.
Reproduce it on your machine
Download and unzip the package, then run this command with Node.js 18.2 or later. No dependencies or accounts are required.
node demo.cjs my-results.json
The script uses real HTTP requests to a temporary server on 127.0.0.1. RSA keys are generated in memory and never written to the report. The records and effects are fictional.
What this does not prove
- This is not a WordPress plugin, provider integration, payment or client delivery.
- Deduplication is held in memory in one Node.js process. Restarting it loses the ledger. It does not establish production exactly-once execution or recovery after a crash.
- The signing format and fault headers are invented for this demo. Production needs the provider’s protocol, secure keys, TLS and persistent transaction handling.
- Only the mock fault guarantees that its 503 happened before processing. A real 503 or timeout can leave the outcome unknown. A safe retry depends on documented provider behavior.