Asynchronous interaction acceptance

Request board

AX23 · latest request wins

NoneCurrent request owner

0Visible order records

0Visible units

0Stale responses ignored

Queue a search with its own identity

The browser fetches a synthetic JSON fixture. Hold its response here, then choose when to release it to the result panel.

Order groupResponse fixture

Held responses

Request	Query snapshot	HTTP	State	Replay action

Ready. Queue Dock, then Bench, to reproduce an out-of-order response.

Expected sequence

1. Queue R1 for Dock and R2 for Bench.

2. Release R2 → AX-207, 7 units.

3. Release R1 → ignored stale; Bench stays visible.

Fixture inventory

AX-110 · Dock · Ready8 units

AX-111 · Dock · Picking4 units

AX-207 · Bench · Held7 units

Visible result context

Applied responseNone

Displayed queryNo successful response

Result records0

Result unit sum0

Acceptance rule

A request keeps the query that created it. Arrival order cannot change which request owns this screen.

response.id === activeRequest.id

✓ Current success replaces the result.

✓ Older success is recorded, then ignored.

✓ Current failure labels the retained result.

✓ Cancellation prevents later application.

Orders from the applied response

Order	Group	Work status	Units

Latest replay decision

Queue and release a response to inspect the decision.

Receive an inspectable sequence

Keep the request identity, query snapshot and visible result together when reviewing the commissioned interaction.

No transitions recorded.

Step	Request	Query	Outcome	Visible result

Receiving owner’s review

Check the accepted sequence against the application endpoint and supported browsers. Attach the trace to the source revision and repeat any failed case before release.

Extend the commissioning brief

Add actual authentication, timeout, empty-result and write-operation requirements where the screen needs them.

Download the 20-case checklist