Who.
Every event carries two attributions, and neither is the sender's to assert. who is the attested observer. capturedBy is the warrantor: the account whose key opened the door.
The observer can be a human, an agent, or an embodied agent. The warrantor is the account that authenticated. The gateway stamps both at the door and strips whatever you sent in those fields, so the party attribution is something the door records rather than something the payload claims.
The party and organisation grain is derived from grant chains at read time, never written into the event. The pages below are the industries the old tree carried, refreshed to what capture means in each. They describe how the standard models the actors; they do not describe a hosted service, because there is no hosted door yet.
whospine:capturedBy
Build state, 29 July 2026. The capture gateway is written and passing its conformance tests; nothing is hosted yet. The dated ledger is What ships today.
Who, page by page.
-
01
Automotive
Automotive supply chains move serialised parts through tiers of suppliers. An EPCIS 2.0 event records which party observed a part at a step; the gateway stamps the observer and the warrantor, so the chain of custody is attributable rather than asserted.
-
02
Computer Hardware
Computer-hardware distribution tracks serialised components and finished units by GTIN and serial. Each capture attributes the observer and the account behind the key, so a return, an RMA, or a warranty claim resolves to who actually saw the unit.
-
03
Consumer Goods
Fast-moving consumer goods generate high event volume across manufacturing, distribution and retail. Capture is $0 per event by policy precisely so a stream that grows with volume is never a stream you stop feeding; the observer and warrantor are stamped on every one.
-
04
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.
-
05
Medical Devices
Medical-device UDI and custody depend on a defensible record of who handled a device at each step. The gateway stamps the observer and the warrantor and can only ever append, so the custody record is evidentiary rather than editable.
-
06
Pharmaceuticals
Pharmaceutical serialisation and verification are built on attributable observation events. EPCIS 2.0 models the who and the business step; the gateway validates each capture against GS1's schema and stamps the observer, so an aggregation or a verification event is checkable, not merely stored.
-
07
Retail
Retail EPCIS spans receiving, replenishment and point of sale. Each event attributes the observer and the account that captured it; minimally-scoped reads mean a partner sees its own scope and nothing outside it, with no redacted shape left behind to argue about.