Picture an address-change reply sitting in a review queue. It says the order has not been dispatched. The sentence was accurate when the draft was prepared. While it waited, someone packed the parcel and recorded its departure.
The reviewer opens a fluent, orderly reply. The fact that made its proposed action sensible has already changed.
This is the next small test we’d add to the fictional merchant-support rehearsal in the Shopify essay. We care less about whether the draft sounds finished than whether its evidence is still usable when someone acts on it.
Two versions of one fictional record
At 09:10, supplied order record A1002 reads “Not dispatched.” A draft proposes checking whether the address can be edited. It preserves that record reference and the time it was read.
At 09:14, the supplied fixture changes to “Dispatched.” At 09:15, an operator reviews the draft. Re-reading the earlier snapshot would confirm what the system saw, but wouldn’t establish the current state.
The next move in this rehearsal is to retrieve the relevant record again, compare the state and hold the draft for exception review. Which address-change options remain available is still a missing fact. Neither timestamp supplies that answer.
Keep both versions. The old record explains why the draft was prepared; the newer record explains why its proposed route needs another look. Silently replacing the old snapshot makes the change harder to diagnose later.
Give the check a specific target
“Refresh everything” is too vague for a useful test. Name the fact the action depends on. Here it is dispatch state. In another workflow it might be whether an invoice is already paid or a request has been withdrawn.
A compact review row could read:
Decision-critical fact: dispatch state
Read when preparing: 09:10, Not dispatched
Read at review: 09:15, Dispatched
Disposition: proposed route held; exception capability unconfirmed
Those times are part of this invented exercise, not a recommended freshness interval. The workflow needs a point where the decision-critical fact is checked before the next move. A timestamp alone is a record of a reading.
The full Shopify essay explains the proposed decision packet and both operating views:
https://www.rebuildshow.com/p/shopify-the-ticket-is-classified
Try one changed-record fixture in your next rehearsal. Make the important state change after preparation, then check whether the reviewer notices it and preserves the reason for changing course.
The Rebuild Editorial


