A response boundary separates work completed before a server response from work performed after the response is sent. It defines what the user waits for and which failures may occur after a success message. section 7.5
Booking cancellation
Before the 200 OK, the booking status change and audit-row creation run synchronously; failures produce a visible error. Afterward, workflow cancellation, webhook delivery, and calendar deletion run asynchronously. Their failure can remain invisible while the user sees a green success screen. section 7.5
Use the boundary to ask:
- Which writes block the response? section 7.5
- Which operations fan out afterward and fail silently? section 7.5
- Which external calls need idempotency keys when retries cross the boundary? section 7.5
