# Core Data Core Data is Apple’s object-graph management and persistence framework. In this notebook it matters less as an application-development convenience than as the probable origin of internal `Z...` tables and fields being used to reconstruct accounts, cloud state, and device usage. ## Historical and Technical Context Core Data manages model objects, relationships, change tracking, validation, undo, and persistence. SQLite is one supported persistent-store format, but Apple treats that schema as a private implementation detail. Commonly observed columns such as `Z_PK`, `Z_ENT`, and `Z_OPT` respectively support row identity, entity identification, and optimistic locking; application-specific entities and attributes are often materialized with `Z`-prefixed names. The framework should not be confused with [[SQLite|SQLite]] itself. SQLite stores records; Core Data supplies the higher-level object model and may change its physical schema across versions. ## Role in Scanned_20260730-1802 Pages 4 and 6 show the author descending beneath Apple’s visible cloud and account interfaces into database fields. The reconstruction strongly infers inspection of a `Usage.db` or related Apple store containing device, cellular, account, and iCloud-like entities. This is an early expression of the notebook’s recurring method: infer a system’s true identity and authority boundaries from internal names rather than marketing labels. ## Notebook Evidence - `Scanned_20260730-1802.pdf`, PDF page 4: "\"in cellular Usage.db\"" - `Scanned_20260730-1802.pdf`, PDF page 4: "\"mach_uuid\"" - `Scanned_20260730-1802.pdf`, PDF page 4: "\"Z_ENT\"" - `Scanned_20260730-1802.pdf`, PDF page 4: "\"Z_PK, OPT, Ent\"" - `Scanned_20260730-1802.pdf`, PDF page 6: "\"Z_ENT, Z_name, Zsuper,\"" - `Scanned_20260730-1802.pdf`, PDF page 6: "\"Zmax Z_PK, Z_opt\"" **Visible evidence:** a `Usage.db` reference and canonical Core Data-like fields. **Independently verified fact:** Core Data supports SQLite persistent stores, whose representation is implementation-dependent. **Strong inference:** the notebook records schema inspection or reverse engineering of an Apple device database. ## Relationships [[SQLite|SQLite]] is the likely storage engine, [[iCloud|iCloud]] appears in probable entity names, and [[Apple Platform Internals|Apple Platform Internals]] provides the broader forensic context. Conceptually, Core Data connects to [[Universal Object Interaction|Universal Object Interaction]] because entities, identifiers, attributes, and relationships are the semantic machinery needed to turn records into addressable objects. ## Cross-Notebook Significance The reconstruction connects this schema-reading practice to `Scanned_20260730-1756.pdf`, PDF page 2, which contains Android package and hidden-interface terms. The relationship is methodological and provisional: both notebooks appear to infer systems through internal identifiers. ## Missed Signals and Open Leads Recover the original database, if preserved, and record its schema, provenance, timestamps, and hashes without opening private account records unnecessarily. Resolve the uncertain build string and entity spellings before assigning application ownership. ## Sources - [Apple Developer Archive, “Persistent Store Features”](https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/CoreData/PersistentStoreFeatures.html) - `Scanned_20260730-1802.md`, PDF pages 4 and 6.