A photograph appears on a government website. A product name. A lot number. A warning not to eat something sitting in a refrigerator.
To the public, that may look like the beginning of a food recall. Operationally, it is closer to the end of a much longer investigation.
Before a warning can become specific, someone has to determine what happened, which food is involved, where it traveled, who handled it, what other products may be connected, and how far the problem might extend.
The difficult question isn't always “what is contaminated?”
Often the harder question is: what else is connected to it?
Those boundaries matter because an investigation has two competing responsibilities. Move too slowly and potentially affected food may remain in circulation. Draw the boundary too broadly and perfectly safe products can be discarded, businesses disrupted, and confidence damaged.
Records can exist without creating understanding.
Modern food systems produce enormous amounts of information. The existence of records does not automatically mean investigators can reconstruct events quickly.
Different organizations maintain different systems for different purposes. A laboratory record is not a distributor record. A shipping record is not a restaurant receiving record. A grower's information is not necessarily organized the same way as a buyer's.
The problem is therefore not simply digitization. It is continuity of meaning: can the relevant pieces of an item's history be understood together when circumstances require it, without destroying the origin and meaning of the individual records?