# AMD EPYC ## Identification [[AMD EPYC|AMD EPYC]] is AMD’s server-processor family and explains the repeated “data center,” “hyperscaler,” and “secular growth” language. [[Meta Platforms|Meta]], [[Amazon Web Services|AWS]], and [[Google Cloud|Google]] are being treated as demand-side cloud infrastructure. [[Wigle.net|WiGLE]] is a crowdsourced wireless-network database, which fits the nearby MAC-address capture. `procentric.local` resembles a multicast-DNS or local DNS suffix and should not be treated as a public domain. [[C3.ai|C3.ai]] and [[Palantir Technologies|Palantir]] frame the page’s enterprise-AI theme, while [[Crypto.com|Crypto.com]] and [[iTrustCapital|iTrustCapital]] introduce digital-asset custody. ## Notebook evidence - [[Scanned_20260730-1719#PDF page 2 — Hotel network, cloud equities, domains, and device identifiers|PDF page 2: Hotel network, cloud equities, domains, and device identifiers]] — The page is a convergence map: a real hotel-network observation sits beside investment or market notes about the suppliers of cloud-scale computation, then beside the author’s own account and device identifiers. It begins the notebook at the highest abstraction layer—platform capital and hyperscalers—while already grounding that layer in local radio/network evidence. ## Relationships and overlays The source places this note in a shared evidence cluster with [[Amazon Web Services|Amazon Web Services]] · [[C3.ai|C3.ai]] · [[Crypto.com|Crypto.com]] · [[Google Cloud|Google Cloud]] · [[iTrustCapital|iTrustCapital]] · [[Meta Platforms|Meta Platforms]] · [[Palantir Technologies|Palantir Technologies]] · [[Scanned_20260730-1706|Scanned_20260730-1706]] · [[Wigle.net|Wigle.net]]. Within the larger collection, this evidence extends [[Vendor-Agnostic Recovery|vendor-agnostic recovery]] and [[Continuity Architecture|continuity architecture]] by showing how software, hardware, identity, and pre-OS control depend on recoverable interfaces. ## Evidentiary status and open leads Resolve the hotel’s `procentric.local` service role and OUI owners only from a preserved capture, not handwriting alone. Determine whether “AMD Lands” was a headline fragment and whether “Rex Risc” was meant to contrast x86 superscalar design with RISC/Arm. ## Source - [[Scanned_20260730-1719|Scanned_20260730-1719]] ## Scanned_20260730-1845 overlay PDF pages 47–48 of [[Scanned_20260730-1845]] reuse EPYC as semantic material: EPYC → epic → eye/picture/pick/choice. This is distinct from [[Scanned_20260730-1719]]'s server-market and cloud-compute context. The overlay shows technical naming crossing into the notebook's philosophy of vision and choice. It is creative semantic decomposition, not product etymology, AMD messaging, or evidence of a corporate relationship.