Open Compute Project - Bryant McGill

# Open Compute Project **Entity class:** Program or project **Domain:** Open Infrastructure / Data Centers / Standards **Doc Type:** Standards Institution Node **Maturity:** Developed ## Definition The **Open Compute Project** is an open collaboration community developing specifications and designs for scalable computing infrastructure, including servers, racks, power, cooling, networking and storage. ## Governing Boundary OCP moves standardization above the individual server. Its rack and power work treats the data center as a coupled system, aligning mechanical support, electrical delivery, thermal interfaces and serviceability so independently produced equipment can participate in a common facility architecture. ## Higher-Order Capability Shared interfaces can reduce gratuitous differentiation, permit component replacement on different lifecycles and support multi-vendor infrastructure at rack scale. The important result is not merely cheaper hardware. It is a larger unit of interoperability. ## Relation to Governance Standards determine who can build compatible equipment and where innovation remains possible. [[wiki/Open Rack V3|Open Rack V3]] and [[wiki/Open Rack Wide|Open Rack Wide]] illustrate how a standards body can define the boundary between facility and IT gear. ## Constitutional Question and Failure Modes Open publication does not guarantee equal influence, implementation quality or practical portability. Governance depends on contribution rules, certification, tooling and whether operators can replace one component without inheriting an opaque dependency elsewhere. ## Related Ontology [[wiki/Standards as Governance|Standards as Governance]] · [[wiki/Rack|Rack]] · [[wiki/Open Rack V3|Open Rack V3]] · [[wiki/Rack-Scale Computing|Rack-Scale Computing]] · [[wiki/AI Factory|AI Factory]] ## Sources / Provenance - [Open Compute Project — About](https://www.opencompute.org/about) - [Open Compute Project — Rack and Power](https://www.opencompute.org/community/rack-and-power) ## Relationships  This entry is routed through [[collections/Consciousness Continuity|Consciousness Continuity]], [[collections/Neurotech|Neurotech]], and [[collections/Machine Succession|Machine Succession]]. Its source context is developed in [[articles/2026 Annual Report on Brain-Computer Interfaces|2026 Annual Report on Brain-Computer Interfaces]], [[articles/Mind Uploading and AI — The Host is Reusable and the Person is the Delta|Mind Uploading and AI — The Host is Reusable and the Person is the Delta]], and [[articles/Technologies for Consciousness Mapping and Transfer|Technologies for Consciousness Mapping and Transfer]]. Status-qualified source edges are preserved in the terminal Research Edges section. ### Standards and interoperability - **Open Compute Project** is associated with 800 VDC AI data-center power architecture. Power architecture is becoming multi-vendor standard. ### Additional Documented Relationships - [[wiki/Data Center|Data Center]] is associated with **Open Compute Project**.  ## Read First in the Wiki  - [[wiki/AI Factory|AI Factory]] — supplies the related concept or analytic term context needed to place **Open Compute Project** within the wider system. - [[wiki/Hyperscale Data Center|Hyperscale Data Center]] — supplies the related concept or analytic term context needed to place **Open Compute Project** within the wider system. - [[wiki/Open Rack V3|Open Rack V3]] — supplies the related concept or analytic term context needed to place **Open Compute Project** within the wider system. - [[wiki/Open Rack Wide|Open Rack Wide]] — supplies the related concept or analytic term context needed to place **Open Compute Project** within the wider system. - [[wiki/Rack|Rack]] — supplies the related concept or analytic term context needed to place **Open Compute Project** within the wider system. - [[wiki/Rack-Scale Computing|Rack-Scale Computing]] — supplies the related concept or analytic term context needed to place **Open Compute Project** within the wider system. - [[wiki/Standards as Governance|Standards as Governance]] — supplies the related technical standard or protocol context needed to place **Open Compute Project** within the wider system.  ## Related Work in the Corpus  - In [[articles/Mind Uploading and AI — The Host is Reusable and the Person is the Delta|Mind Uploading and AI — The Host is Reusable and the Person is the Delta]], **Host-infrastructure crosswalk** provides the narrative context for **Open Compute Project**: The remaining cross-links make the boundary conditions explicit.  ## Research Edges  #### Host–residual infrastructure patch — 2026-09-10 **Collections:** [[collections/Consciousness Continuity|Consciousness Continuity]] · [[collections/Neurotech|Neurotech]] · [[collections/Machine Succession|Machine Succession]] **Canonical source article:** [[articles/Mind Uploading and AI — The Host is Reusable and the Person is the Delta|Mind Uploading and AI — The Host is Reusable and the Person is the Delta]] **Related acquisition source:** [[articles/Technologies for Consciousness Mapping and Transfer|Technologies for Consciousness Mapping and Transfer]] **Relationship source:** [[research/Mind Uploading and AI Host-Residual Ecosystem Relationship Graph - 2026-09-10|Mind Uploading and AI Host-Residual Ecosystem Relationship Graph — 2026-09-10]] #### Host-infrastructure integration This entry is expanded through the concrete host-side relationships and status-qualified edges below. #### Outgoing typed edges - **HR-0193 — `hosts_standardization_of` → [[wiki/800 VDC AI Data Center Power|800 VDC AI data-center power architecture]]** — **VERIFIED EXTERNAL**; evidence `WEB_OCP_800V`. Power architecture is becoming multi-vendor standard. - **HR-0840 — `wiki_links_to` → [[wiki/AI Factory|AI Factory]]** — **EXISTING WIKI EDGE**; evidence `WIKI_ARCHIVE`. Direct internal link currently present in `Open Compute Project.md`. - **HR-0841 — `wiki_links_to` → [[wiki/Open Rack V3|Open Rack V3]]** — **EXISTING WIKI EDGE**; evidence `WIKI_ARCHIVE`. Direct internal link currently present in `Open Compute Project.md`. - **HR-0842 — `wiki_links_to` → [[wiki/Open Rack Wide|Open Rack Wide]]** — **EXISTING WIKI EDGE**; evidence `WIKI_ARCHIVE`. Direct internal link currently present in `Open Compute Project.md`. - **HR-0843 — `wiki_links_to` → [[wiki/Rack|Rack]]** — **EXISTING WIKI EDGE**; evidence `WIKI_ARCHIVE`. Direct internal link currently present in `Open Compute Project.md`. - **HR-0844 — `wiki_links_to` → [[wiki/Rack-Scale Computing|Rack-Scale Computing]]** — **EXISTING WIKI EDGE**; evidence `WIKI_ARCHIVE`. Direct internal link currently present in `Open Compute Project.md`. - **HR-0845 — `wiki_links_to` → [[wiki/Standards as Governance|Standards as Governance]]** — **EXISTING WIKI EDGE**; evidence `WIKI_ARCHIVE`. Direct internal link currently present in `Open Compute Project.md`. #### Incoming typed edges - **HR-0270 — [[wiki/AI Factory|AI Factory]] `wiki_links_to` → this entry** — **EXISTING WIKI EDGE**; evidence `WIKI_ARCHIVE`. Direct internal link currently present in `AI Factory.md`. - **HR-0711 — [[wiki/Hyperscale Data Center|Hyperscale Data Center]] `wiki_links_to` → this entry** — **EXISTING WIKI EDGE**; evidence `WIKI_ARCHIVE`. Direct internal link currently present in `Hyperscale Data Center.md`. - **HR-0847 — [[wiki/Open Rack V3|Open Rack V3]] `wiki_links_to` → this entry** — **EXISTING WIKI EDGE**; evidence `WIKI_ARCHIVE`. Direct internal link currently present in `Open Rack V3.md`. - **HR-0853 — [[wiki/Open Rack Wide|Open Rack Wide]] `wiki_links_to` → this entry** — **EXISTING WIKI EDGE**; evidence `WIKI_ARCHIVE`. Direct internal link currently present in `Open Rack Wide.md`. - **HR-0915 — [[wiki/Rack|Rack]] `wiki_links_to` → this entry** — **EXISTING WIKI EDGE**; evidence `WIKI_ARCHIVE`. Direct internal link currently present in `Rack.md`. - **HR-1271 — [[wiki/Data Center|Data Center]] `should_crosslink_with` → this entry** — **RESEARCH CANDIDATE**; evidence `WIKI_ARCHIVE`.   ### Research Candidates - **R-002311 — research candidate:** Assess whether **Open Compute Project** and [[wiki/Data Center|Data Center]] warrant reciprocal reader-facing prose. Settlement requires a source that documents the relationship directly. Suggested missing reciprocal/cross-thread edge. Shared internal mediators (4): AI Factory, Hyperscale Data Center, Rack, Rack-Scale Computing  ## Research Inferences  These entries translate the forward-looking register in [[research/Research Inferences|Research Inferences]] into ordinary wiki prose. The tier labels apply to the inference, not automatically to every factual anchor inside it. The interpretive frame comes from [[articles/Technologies for Consciousness Mapping and Transfer|Technologies for Consciousness Mapping and Transfer]] and [[articles/Mind Uploading and AI — The Host is Reusable and the Person is the Delta|Mind Uploading and AI — The Host is Reusable and the Person is the Delta]]. Collection route: [[collections/Neurotech|Neurotech]]. - **INF-0189 — Established.** Standardizing high-voltage DC distribution across Google, Microsoft, and NVIDIA within OCP makes the physical metabolism of AI a common specification. Shared metabolism means any workload written for one facility runs in all of them, which is portability at the layer nobody discusses.  ## Research Inference Attractors  These are secondary semantic placements for the inference attractor network. Each statement keeps its original ID and tier; its canonical cluster page links back to every destination. Source register: [[research/Research Inferences|Research Inferences]]. Interpretive context: [[articles/Technologies for Consciousness Mapping and Transfer|Technologies for Consciousness Mapping and Transfer]] and [[articles/Mind Uploading and AI — The Host is Reusable and the Person is the Delta|Mind Uploading and AI — The Host is Reusable and the Person is the Delta]]. Collection route: [[collections/Neurotech|Neurotech]]. - **INF-0183 — Analytic.** Processing neural data on the implant means raw signal never leaves the body, which converts a legal privacy problem into an architectural property. Regulation that mandates data minimization will functionally mandate neuromorphic edge compute. - **Canonical cluster:** [[wiki/Neuromorphic Computing|Neuromorphic Computing]] - **INF-0185 — Plausible.** Analog computation trades precision for energy, and neural computation is demonstrably noise-tolerant. The substrate that matches the workload's error tolerance wins on cost, which argues that brain-hosting hardware will be analog long before it is exotic. - **Canonical cluster:** [[wiki/Neuromorphic Computing|Neuromorphic Computing]] - **INF-0197 — Plausible.** Remote attestation proves which code is running on which hardware, providing a cryptographic answer to the question of what is executing a hosted state. Attestation converts custody from a contractual promise into a verifiable fact. - **Canonical cluster:** [[wiki/Neuromorphic Computing|Neuromorphic Computing]] - **INF-0200 — Plausible.** Running the same state redundantly across facilities is standard practice for critical workloads and would produce multiple simultaneous instances of a hosted mind. Redundancy engineering and identity philosophy collide the first time an operator enables it for reliability reasons. - **Canonical cluster:** [[wiki/Neuromorphic Computing|Neuromorphic Computing]]