Events have provenance
A line can reflect a direct parcel observation, an association, a partner report, a status rule, public wording, or automatic sensing. The mix varies by carrier and service.
Episode V013 · Source record
What Package Tracking Actually Shows
The evidence, limits, and original fictional information model behind Hidden Logic's explanation of tracking events and update gaps.
- Research recheck
- August 2, 2026
- Evidence stack
- 11 source records · 18 direct links
- Visual proof
- Original fictional model
FICTIONAL TRACKING EVENTS
IT DIDN'T TELEPORT
REPORTED EVENTS ≠ COMPLETE JOURNEY
The sourced answer
A tracking timeline is a reported event history, not a complete movie.
More than one middle can fit
The original model produces the same four customer events from two different hidden histories. Sparse output cannot identify a unique path by itself.
The gap is not a diagnosis
A blank interval alone proves neither movement nor stoppage, normal routing nor error, safety nor loss. Current carrier guidance is the right place to decide whether action is needed.
Original Black Box Event Test
Two hidden histories. One public timeline.
History A and history B share the same four customer-visible events. Their sampled physical states differ, and each produces a different six-record internal ledger.
Toy information model. Not carrier software.
- 2 different fictional physical histories
- 6 system records in each history
- 4 identical customer-visible events
Every location, time, status, association, rule, and record is invented for teaching. The model proves an information boundary, not the cause of a real package's gap.
Direct source library
Trace every public claim.
Each note states what its reference supports and where the evidence stops. External sources open in a new tab.
USPS event structure
A public line can have more than one kind of provenance
These USPS references distinguish recorded observations, associated events, public wording, status rules, and display filters. The details are USPS-specific.
C01Rechecked 2026-08-02
Product Tracking and Reporting
U.S. Postal Service
USPS says its system stores scan data for barcoded packages and receives tracking information from mailer files, handheld scanners, retail equipment, processing equipment, and other Postal systems.
C02-C06Rechecked 2026-08-02
April 2026 Product Tracking event descriptions
U.S. Postal Service
The glossary separates internal event fields from public wording. It also documents repeated-scan filtering for one processing event, visibility-gap statuses, and item events associated with a scanned container or trailer. These mechanisms do not diagnose a real package.
Tracking gaps and handoffs
Carrier and service rules vary
The public histories described here are useful but bounded. None of these references reveals the unique cause of one shipment's update gap.
C07Rechecked 2026-08-02
Shipment information and physical possession
USPS and UPS
USPS documents pre-shipment and shipping-partner records. UPS says Label Created means shipment details were received before it took possession. A precise timestamp can describe information entering a system without proving the parcel entered a building then.
C08Rechecked 2026-08-02
Understanding tracking status
UPS
UPS says scans capture movement information and a long-distance shipment can remain On the Way without another scan until it reaches a destination hub. This is UPS-specific and does not explain one package's gap.
C09Rechecked 2026-08-02
Tracking updates during long transit
FedEx
FedEx says update frequency varies, a gap longer than 24 hours can occur during long transit, and On the way can describe travel or time at a facility. The guidance does not guarantee that a gap is harmless.
C10Rechecked 2026-08-02
Milestone tracking and local delivery partners
DHL eCommerce and DHL developer support
DHL eCommerce says parcels can keep traveling between displayed milestones and final delivery can pass to a local postal operator, depending on service. Separate API support says bulk handling can omit an individual pickup event.
Sensing and maps
More information can exist without becoming a complete route history
Automatic sensing, limited delivery maps, and dedicated monitoring products are important counterexamples to a scan-only explanation.
C11Rechecked 2026-08-02
Conventional scans and RFID sensing
UPS
UPS says conventional scans and RFID sensors contribute to tracking history. Its April 2026 announcement describes automatic sensing at equipped U.S. points and RFID labels for packages shipped through more than 5,500 UPS Store locations. RFID is not GPS.
C12Rechecked 2026-08-02
Conditional last-mile maps
UPS and FedEx
UPS and FedEx describe map views for some eligible deliveries. UPS calls its displayed driver location approximate. FedEx requires an eligible shipment and an estimated delivery window. Neither feature is a universal end-to-end route recording.
C13Rechecked 2026-08-02
SenseAware enhanced monitoring
FedEx
FedEx offers a separate sensor-device product for sensitive or critical shipments. Its documentation says air-travel data is stored and reported after landing. This is not ordinary customer tracking.
Technical context and original proof
The information boundary can be tested
One standards reference supplies vocabulary. The actual black-box comparison is an original deterministic teaching model built from fictional data.
C14Rechecked 2026-08-02
EPCIS and Core Business Vocabulary 2.0
GS1
EPCIS supplies technical context for event dimensions, association, and sensor data. It is not evidence that any carrier named in this episode uses EPCIS.
C15Rechecked 2026-08-02
V013 Black Box Event Test
Hidden Logic · Original deterministic model
Two different fictional physical histories create different six-record internal ledgers while producing the same four customer-visible events. The result proves ambiguity in this toy output, not what happened to a real package.
Reproducible model record retained with the episode.