# Device Identity Device identity is layered rather than singular. A model names a family; a serial identifies a manufactured unit; MAC addresses identify interfaces; IMEI/MEID identifies cellular equipment; EID identifies eSIM hardware; ICCID identifies a SIM or profile; FCC/Canadian identifiers identify an authorized radio design. ## Notebook contribution [[Scanned_20260730-1230]] repeatedly preserves several layers for one object and uses color, ordinal numbers, and labels to distinguish otherwise identical units. The page-15 iPhone serial discrepancy illustrates why confidence and source-image comparison matter. ## Boundary An identifier supports correlation. It does not alone prove current owner, user, location, integrity, compromise, or authorization. ## Scanned_20260730-1946 overlay PDF page 13 elevates GUIDs/UUIDs from file-format trivia into the connective tissue of edge, blockchain, industrial, and IoT systems. PDF pages 14–15 then place an [PERSON REDACTED] name and fully redacted bank/PIN material at the center of a dense identity mesh. The diagram usefully anticipates identity graphs but leaves node and edge semantics undefined. Identifiers, authenticators, recovery secrets, account ownership, and authority must remain separate; a link or central placement is not proof of control, transaction, communication, or compromise. ## Scanned_20260730-2016 overlay PDF pages 19, 29, 38, 41, and 42 of [[Scanned_20260730-2016]] bind iPhone, Pixel, Apple Watch, AirPods, Garmin, hotspot, SIM/eSIM, and carrier records to account recovery. The new evidence shows device identity as an authentication and routing dependency rather than only a hardware inventory label. A device name or model does not establish current possession, subscriber assignment, enrollment, integrity, or account authority. Those states require dated device, carrier, and provider records. ## Scanned_20260730-1958 overlay PDF pages 3, 6, 8, 21, 26, 32, 35, 43, 46, and 49 of [[Scanned_20260730-1958]] show device identity changing by layer: retail model, model code, IMEI, radio label, encrypted-backup attribution, enterprise-management domain, Android codename, and account/dashboard name. The Nexus 5/Pixel 3 `blueline` mismatch is especially important. It preserves conflicting labels without deciding that spoofing, emulation, stale metadata, or restore history caused them. The necessary next artifact is the exact interface plus build fingerprint and dated device inventory.