# SQLite SQLite is an embedded relational database engine stored in ordinary files; it matters here as the likely physical store beneath Apple's Core Data entities. ## Historical and Technical Context The repeated `Z_`/`Z` field names and the canonical triad `Z_PK`, `Z_ENT`, and `Z_OPT` strongly indicate an Apple [[Core Data|Core Data]] SQLite backing store. Core Data commonly materializes entities and attributes as `Z...` tables and columns, while `Z_PK` serves as a primary key, `Z_ENT` identifies the entity type, and `Z_OPT` supports optimistic locking. Apple warns that the SQLite store is an implementation detail rather than a schema applications should manipulate directly. [S03] “cellular Usage.db,” `mach_uuid`, cloud/account fields, and an iPad reference suggest that the author was inspecting a device database and trying to infer **identity, account, and usage relationships**. “XSAN,” Apple’s clustered file system, may be a separate lead or an attempt to situate the database within a broader Apple storage taxonomy. ## Role in Scanned_20260730-1802 The primary identifying evidence appears on PDF page 4. A crowded diagnostic page with a circled “XSAN” at top and numerous short database-like field names scattered around the center. Several terms begin with “Z,” and there are arrows, underlines, overwritten fragments, and a boxed lower section. The page looks like a hand-built schema map copied from a database browser. Some words are faint or malformed. Within that page, SQLite helps the notebook move from a visible name or artifact toward the underlying identity, protocol, ownership, or control structure. ## Notebook Evidence - `Scanned_20260730-1802.pdf`, PDF page 4: "XSAN" - `Scanned_20260730-1802.pdf`, PDF page 4: "Lamp" - `Scanned_20260730-1802.pdf`, PDF page 4: [uncertain: "Plumners" / "Plummers"] - `Scanned_20260730-1802.pdf`, PDF page 4: [uncertain: "Sau old iPad"] - `Scanned_20260730-1802.pdf`, PDF page 4: "in cellular Usage.db" **Evidentiary status:** Visible evidence: field names and explicit `Usage.db`. Verified fact: Core Data’s SQLite representation is private and implementation-dependent. Strong inference: a forensic or reverse-engineering session around iOS/macOS usage and cloud-account records. Unresolved: whether the `Z...` names were copied exactly or normalized in memory. The canonical name **SQLite** is normalized outside the quotations. The quoted lines preserve the completed reconstruction's spelling, capitalization, and uncertainty markers. ## Relationships On PDF page 4, SQLite appears in the same evidentiary cluster as [[Apple Xsan|Apple Xsan]], [[Core Data|Core Data]], [[iCloud|iCloud]]. These links record page-level proximity and the reconstruction's systems map; they do not by themselves prove corporate ownership or a direct technical dependency. ## Cross-Notebook Significance The page links directly to page 6’s second Core Data-like field list and page 26’s hunt for internal constants and log artifacts. Across the notebook, “cloud” is repeatedly pursued not as a marketing abstraction but as **database rows, account identifiers, daemons, and enrollment state**. ## Missed Signals and Open Leads Recover the original `Usage.db` file, if preserved, and map each handwritten field to its exact SQLite schema. Resolve “Plumners/Plummers,” the build string, and the possible Apple domain. Do not infer personal activity from field names alone without the records themselves. ## Sources - [[Scanned_20260730-1802|Scanned_20260730-1802]], especially PDF page 4. - `Scanned_20260730-1802.pdf`, cited as a plain archival filename; the PDF is not stored in `wiki-notes`. - **[S03]** Apple Developer Archive, “Persistent Store Features” (Core Data). https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/CoreData/PersistentStoreFeatures.html