Quantum Computing in Academia and Industry Monroe’s broader thesis is that atoms are already close to ideal quantum hardware, so the remaining challenge is increasingly one of engineering rather than discovering fundamentally new qubit physics. In his view, a large-scale quantum computer is therefore unlikely to emerge simply by making one monolithic processor larger and larger. A more plausible path is to build high-performance atomic QPUs, scale them locally through better control and ion transport, and then connect those modules through photonic links. Seen through that lens, the lecture draws a surprisingly natural line from IonQ’s origins to Oxford Ionics, Lightsynq, and ultimately a photonic modular architecture. Monroe explicitly says that IonQ’s genesis came from a paper on modular quantum computer architecture. In other words, IonQ was not founded merely around the idea of building a better ion trap. From the beginning, the ambition was to commercialize a quantum computing architecture that could continue scaling after any single physical module eventually reached its practical limits. That makes the Oxford Ionics acquisition especially interesting. Monroe describes Oxford’s combination of microwave gates and ion shuttling as a highly compelling architecture. From this perspective, Oxford Ionics does not simply add another trapped-ion technology to IonQ’s portfolio. It appears to fill an important gap in IonQ’s original scaling thesis: how to scale efficiently within a local QPU before moving to inter-module networking. The hierarchy Monroe describes can therefore be viewed in two layers: Local scaling: Qubits → better control → QCCD / ion shuttling → qudits → larger and higher-fidelity QPU modules Global scaling: QPU modules → communication qubits → photonic interconnect → modular quantum data center The second layer is where quantum networking, remote entanglement, and quantum memory become critical. Photons are excellent carriers of quantum information because they can travel long distances through optical networks, but they also present a fundamental architectural problem: photons move extremely fast and do not naturally stay where you need them. If entanglement generation is probabilistic, one successful link may need to wait while another link is retried. Without a memory, there is nowhere to hold that quantum state. That is why Monroe repeatedly comes back to the need for Photon + Memory rather than photonics alone. In this architecture, the photon acts as the flying qubit that connects physically separated QPUs, while a quantum memory stores the successfully generated state, allowing the network to operate asynchronously. This is precisely where Lightsynq fits. Its role is not simply to improve photon collection, but to provide the memory and interface layer needed to make photonic interconnects practical enough for modular quantum computing. So the larger picture is quite coherent: Oxford Ionics helps solve local scale-up. Lightsynq helps solve global scale-out. Photonic interconnects tie the QPU modules together. Put together, Monroe’s vision looks less like a single enormous quantum processor and more like a quantum data center built from high-fidelity atomic QPUs, ion shuttling, communication qubits, quantum memories, and a reconfigurable photonic fabric. What makes the lecture particularly interesting is that these pieces do not feel like disconnected acquisitions or research programs. They can be read as successive layers of the same scaling architecture that Monroe says was already embedded in IonQ’s original founding thesis. Continued in Part 3 of the lecture.