← Back to the chapter · Previous detail

Technical detail · How RFID Identifies Objects

Locate a failed handoff

Object to tag. Attachment, encoding, and association establish which object or credential the identifier names. They do not establish read reliability, zone control, privacy, or application correctness. Retest after attachment, material, cleaning, repair, replacement, reuse, encoding, or ownership changes.

Tag to reader. Communication establishes a result under tested power, frequency, orientation, distance, and material conditions. It does not establish filtering, application decisions, or every population and environment. Retest after power, antenna, firmware, region, material, tag vendor, orientation, population, or site-layout changes. A powered tag can still collide with other tags; a decoded tag can still be in the wrong zone.

Reader to middleware. Decoded, timestamped observations associated with a reader establish that software received a trace. They do not establish uniqueness, intent, zone membership, or business meaning. Retest after duplicate-window, reader-identity, network-path, timing, filtering, batching, or exception-rule changes.

Middleware to application. A filtered observation mapped to count, receive, return, release, or deny establishes that workflow mapping. It does not establish every future workflow, user, privacy boundary, replacement tag, or support process. Retest after catalog, access-rule, workflow, privacy-policy, audit-rule, integration, or support-ownership changes.

Keep the approval within its tested doorway, object type, and tag population. Preserving these handoffs makes it possible to locate where a claim stopped being supported.

← Back to the chapter · Previous detail