Food and Beverage.
Food and beverage traceability turns on who observed a lot and when. EPCIS 2.0 with CBV dispositions records the business step and the attested observer; append-only storage means a recall trace reads a history that cannot have been rewritten after the fact.
whospine:capturedBy
The trace-back, as a query.
GET /events?MATCH_epc=…&EQ_bizStep=receiving
→ receiving dc-west who: human · dock crew capturedBy: distributor
→ receiving store 214 who: human · crew lead capturedBy: operator
→ receiving store 219 who: — (absent) capturedBy: operator
→ ErrorDeclaration: store 219 receiving corrected, declared — not editedIllustrative: one lot walked backward through its own events. The query surface (SimpleEventQuery, per-EPC trace) is implemented and runs locally; the corrected hop shows the standard's own correction law — an ErrorDeclaration event, never an edit.
For the engineer handed the recall drill.
The hop with no observer is the finding, and the record shows it as an absence rather than papering over it. Corrections are declared events appended to the history, so the drill reads what happened and what was corrected — both, in order, hashed.
Proof, not adjectives. The gateway's conformance tests pass against GS1's normative artifacts. See Who for the dimension, and What ships today for the dated ledger.