Skip to content
#edge computing Open access

Paper ER=EPR v1.0: Two Readings, One Support

Sep 2026 · Zenodo (CERN European Organization for Nuclear Research)
Quantum Mechanics and Applications

Abstract

We reformulate the ER = EPR hypothesis within the Ontological Resolution Theory (ORT) framework. The central claim: ER (Einstein-Rosen bridge) and EPR (Einstein-Podolsky-Rosen entanglement) are not identical, as conjectured by Maldacena and Susskind, but stand in a proper inclusion: ER ⊂ EPR. The backend substrate consists of nodes with two orthogonal sectors: P-sector (83 bits, topology, addressing) and A-sector (50 bits, budget, throughput). Entanglement (EPR) is defined as two frontend tags addressing a single backend support region S. An Einstein-Rosen bridge (ER) emerges when the same support region S is read by the A-sector as spatially separated (dA > dthreshold), while the P-sector maintains a direct topological connection via a nonlocal edge (shortcut) invisible to metric reading. The photon is treated not as an encoder but as a transport protocol: a commit-trace propagating along FCC edges (E), not along shortcuts (Eshortcut). The A-sector metric ignores shortcuts; spatial distance dA is computed via FCC paths only. Predictions: (1) Bell inequalities are inapplicable because backend distance is undefined for entangled pairs; (2) ER bridges require only topological connectivity, not exotic matter; (3) time is emergent as commit tempo. The ER ⊂ EPR relation is more restrictive than Maldacena-Susskind's ER ⇔ EPR: a bridge appears only when entangled pairs are metrically distant; nearby entangled pairs exhibit EPR without ER. Keywords: ER = EPR, entanglement, Einstein-Rosen bridge, shared support, nonlocal edge, shortcut, two-sector architecture, frontend/backend separation, Ontological Resolution Theory

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54

Related blog posts

Microsoft Research Blog Oct 6, 2026

What AI gets wrong and what failure teaches us

Jennifer Neville did not want to go into computer science—but that’s exactly where she landed. Neville discusses the starts and stops that led to her professional sweet spot and her work identifying “surprising failures” making it hard for AI to handle complexity.  The post What AI gets wrong and what failure teaches us appeared first on Microsoft Research.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.