# Meta Platforms ## 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]] · [[AMD EPYC|AMD EPYC]] · [[C3.ai|C3.ai]] · [[Crypto.com|Crypto.com]] · [[Google Cloud|Google Cloud]] · [[iTrustCapital|iTrustCapital]] · [[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-1659 overlay **Source evidence:** [[Scanned_20260730-1659#PDF page 33 — Cloudflare firewall and autonomous-system numbers|page 33]]. An [[Autonomous System Number|ASN]] identifies an independently routed network. AS15169, AS32934, AS8075, AS16276, and AS14618 map to Google, Meta, Microsoft, OVHcloud, and Amazon network domains. [[Cloudflare|Cloudflare]] can proxy customer DNS through its anycast edge. A [[User Agent|User Agent]] identifies client software in application protocols and is distinct from ASN ownership. **Relationship overlay:** [[Amazon Web Services|Amazon Web Services]] · [[Autonomous System Number|Autonomous System Number]] · [[Cloudflare|Cloudflare]] · [[Google|Google]] · [[Microsoft|Microsoft]] · [[OVHcloud|OVHcloud]] · [[User Agent|User Agent]]. This evidence supplements rather than replaces earlier notebook interpretations. It connects the existing note to [[Identity Continuity|identity continuity]], [[Device Sovereignty|device sovereignty]], and [[Scanned_20260730-1659|Scanned_20260730-1659]]. ## Scanned_20260730-2016 overlay PDF pages 37 and 41 of [[Scanned_20260730-2016]] connect Facebook recovery, WhatsApp, and the discontinued Novi wallet pilot within one identity and asset-custody surface. The notebook therefore records Meta not only as a social platform company but as an attempted bridge among social identity, communications, and payments. The page grouping does not establish that the services shared all credentials or data, that any Novi balance existed, or that the Facebook compromise notation identifies a mechanism or actor.