Fable
The messenger who ran through the shops learned not to look only at the signboard
In the southern market there was a messenger who at first was only responsible for delivering letters for the chamber of commerce. He knew every street and also knew which shop sold salt and which shop exchanged money. When the chamber asked him for information, he would run out to ask around and then come back and report orally.
Later, the guild handed him more tasks: checking ship schedules, comparing prices, filling customs forms, downloading vouchers, booking cargo space. The shops on the street became more and more like mazes—some required taking a number first, some hid prices on the second page, and some added a fee at the last step.
The guild leader first gave the messenger a thick map, with each shop's door number and counter location written on it. The map quickly became outdated. Shops moved, counters were renamed, forms changed order, and the paths on the old map still led to the doorway but could not reach the actual matter to be handled.
Someone also said that as long as the messenger runs faster, it will be fine. The messenger could indeed visit more shops in a day, but began bringing back contradictory messages: one showed stock available, but at checkout there was none; one had a low price but high shipping; one form submitted successfully but had no receipt. Speed amplified uncertainty.
A procurement incident caused heavy losses for the chamber of commerce. The messenger saw the lowest price on a webpage and ordered immediately, only later discovering that it was a price without tax and that the supplier had no compliance certificate. The president found that the messenger could browse, but could not judge the evidence, constraints, and delivery conditions in a web task.
So the chamber of commerce gave him a new set of operating procedures. Before each departure, write down the goal and boundaries clearly: look up information, fill out forms, download files, or execute transactions. During the trip, record the pages visited, key fields, screenshots, and source timestamps. When payment, external submission, or contract confirmation is involved, a summary must be brought back to the chamber president for approval.
The messenger learned to maintain task state across web pages. He no longer just looked at the signboard; he checked login identity, whether the page had finished loading, whether the button had actually submitted, whether the receipt was downloadable, and whether the result matched the original goal. When he encountered CAPTCHAs, insufficient permissions, or changed terms, he did not force his way through but marked them as blocked.
Later, the chamber of commerce still had people decide large purchases, but daily price checks, form filling, downloads, and status follow-ups were handed to the messenger. What everyone valued was not that he could open web pages, but that in an open, changing, risky web environment he could carry a task through to an acceptable result.