Faultline/ 01

INTERACTIVE SYSTEMS LAB

The booking succeeded.
The response didn’t.

Your client sees a timeout. The service already committed.
Retry the same request. How many visits exist now?

01 / THE COMMIT BOUNDARY

A small failure.
A very expensive assumption.

No login. No real bookings.
Booking workbenchBROWSER SIMULATION
01 · Place the fault
The service commits a visit, then the response is dropped. The client sees a timeout.
CLIENT / RECEIVER EVENTSORDERED TRACE
  1. Meet the uncertainty window.

    Send one request and lose its response.
    Then inspect what actually happened.

1First, create the uncertainty.Send the booking through the selected fault.

THE FIX IS A RECEIVER CONTRACT

Remember the operation.
Not just the attempt.

A retry is safe only when the receiver can recognize the same intended action. A client-side “success” message is not evidence of one effect.

Inspect the source
Atomic receiver model
  1. 01
    Look up the operation key

    Same key and payload? Return the saved result.

  2. 02
    Commit effect + receipt together

    Neither may exist without the other.

  3. 03
    Reject conflicting reuse

    Same key, different payload? Return 409.

A new key means a new operation. The receiver cannot infer your intent.

Real execution. Simulated infrastructure.

The state machine, retries, deduplication, assertions, and downloadable traces execute in your browser. The booking and service are seeded fixtures. State lives only in memory and resets on reload. No requests reach a real provider.

The fix assumes atomic storage of the effect and receipt, a stable key, and retained receipts. This model does not prove crash durability, cross-process locking, or exactly-once behavior for arbitrary services. A real receiver needs transactional storage, payload validation, a retention policy, and reconciliation when it cannot deduplicate.