Primary Domain
Technology
Within the Primary Domain facet, Technology intelligence groups reporting by primary domain so readers can follow a focused area of internet infrastructure, governance, connectivity markets, or digital capital. The page brings together related articles, public evidence, institutions, companies, people, regional exposure, operating dependencies, and market context that may otherwise sit across separate category pages. It explains the domain, the likely actor class, the market or governance context, and the source material readers should use when comparing signals. Operators, analysts, and governance readers can see how the same domain appears across events, profiles, market shifts, public-source evidence, regional dependencies, and longer-cycle infrastructure decisions over time.
Leaders
Cristiano Amon and the Missing Receipt in Qualcomm's Oryon Story
Qualcomm closed its Nuvia acquisition in March 2021, put Oryon inside Snapdragon X Elite in October 2023 and reached retail shelves with a multi-OEM PC wave in June 2024. A court ruling arrived later. Each event strengthens Cristiano Amon's strategic case, but none proves the…
Academics
Robin Milner and the theorem that search could not mint
A proof tactic may explore thousands of branches and announce success. In the LCF architecture, that announcement is not the acceptance event. The decisive entity is a theorem value that can be created only through a protected set of axioms and inference-rule functions. Robin…
History
The Cheapest Plan Was Only a Forecast
A query optimizer can be perfectly correct about what a query means and still be badly wrong about how long its chosen plan will take. Patricia G. Selinger and the System R team made that tension operational in 1979: let users state the result they want, enumerate plausible…
History
The KWIC Output Matched. The Change Cost Did Not
Run two programs against the same lines and both print the same alphabetized circular shifts. The acceptance test is green. Now change how a line is stored. In one design, the decision leaks through several work assignments; in the other, it remains behind one boundary. David L.…
Leaders
Cristiano Amon and the Two FY2029 Clocks Behind Qualcomm's Expansion
Qualcomm put FY2029 on two investor-day charts, twenty months apart. The date stayed fixed; the businesses inside the target did not. Reading that change as accomplished growth would turn a management plan into a historical result.
Academics
Nancy Leveson and the Accident With No Broken Part
A system can do exactly what its components were built to do and still put people in danger. Nancy Leveson's work asks who was meant to keep that system within safe bounds, what they knew when they acted, and which feedback failed to correct a mistaken picture of the world.
History
Mary Shaw and the Protocol Between the Boxes
In 1994, Mary Shaw argued that software design had become fluent about the boxes and strangely inarticulate about the lines. Calling one procedure from another was useful machinery, but it was too small a language for the flows, events, shared representations, synchronization and…
History
Susan Eggers and the Core That Learned to Share Its Empty Slots
A wide processor can look powerful on a block diagram while leaving execution units idle whenever one instruction stream runs out of independent work. Susan Eggers and her collaborators asked a sharper question: what if several independent threads could compete for those…
History
Betsy Ancker-Johnson and the Plasma That Remembered the Path
In 1964, Betsy Ancker-Johnson mapped a semiconductor plasma whose stability could not be described by one switching point. Its state depended on how the electric and magnetic fields had been approached—a precise lesson in history-dependent systems, and in the danger of turning a…
History
Irene Greif and the Atomic Commit That Could Not Preserve an Author’s Intent
The Collaborative Editing System made shared document changes serializable and recoverable. Its design also exposed a limit that still matters: a transaction can protect bytes from half-finished change without knowing what a writer meant, whether collaborators noticed, or whose…
History
Gladys West’s 1982 Earth Ellipsoid Was a Geodetic Receipt, Not a GPS Blueprint
When Gladys B. West died on January 17, 2026, Virginia’s General Assembly memorialized a career whose satellite-geodesy work had become shorthand for the foundations of GPS. That shorthand is useful only if its evidentiary limits remain visible. West’s 1982 paper, “Mean Earth…
History
Sophie Wilson and the Receipt That Arrived with ARM1 Silicon
When ARM1 returned from fabrication on 26 April 1985, the board was already waiting and much of its software had already run—on models and simulators. The chip's immediate boot was not a miracle of a naturally flawless RISC design. It was the visible receipt for months of…
History
The Root Was a Coordination Shortcut, Not a World Directory: RFC 2120
X.500 drew a clean Directory Information Tree, but its root carried an awkward human obligation. Every administrator of a first-level Directory System Agent was expected to coordinate with every other one through bilateral agreements or private arrangements outside the standard.…
History
Adele Goldberg and the Contract That Let Smalltalk-80 Travel
The Blue Book turned a live system into a portable agreement: preserve the image, implement the entity memory, bytecodes, contexts and primitives, and let unlike machines run the same Smalltalk-80. The agreement made reimplementation possible; it never promised equal speed…
History
The Join Had No Receipt. The Tree Survived by Refresh: RFC 2117
RFC 2117 did not build a sparse multicast tree as one transaction. A local membership indication created one record; a Join/Prune refreshed records hop by hop; a source initially reached a rendezvous point inside Register messages; a branch could later move to source-specific…
History
Evelyn Berezin and the Boundary Between Uptime and Inventory Truth
Teleregister's United Airlines system could lose a processor and keep answering. That was a landmark of online engineering. It was not, however, proof that every answer about an available seat was true.
History
The Address Said Home. The Dial-Up Line Said Away: RFC 2107
RFC 2107 let a remote dial-in client borrow the routing appearance of home. The illusion depended on a Foreign Agent, a Home Agent, a shared secret, a Tunnel ID and state that had to be created and destroyed in the right order.
History
Karen Spärck Jones Made Rarity Count; IDF Did Not Make It True
The same word can be commonplace in one document collection and unusual in another. Karen Spärck Jones turned that difference into a useful retrieval signal. Her achievement was not to discover a universal measure of importance, but to show how a collection can disclose which…
History
The Router Gave the Workstation an Address. It Did Not Give It an Identity: RFC 2106
RFC 2106 solved a real scaling problem by placing many remote SNA and NetBIOS workstations behind one DRAP server. The bargain was precise: fewer backbone peers, more state and judgment concentrated at the boundary.
History
Two Hash Passes Made a Reusable MAC. The Tag Did Not Make a Trust Decision: RFC 2104
RFC 2104 gave protocol designers a compact way to turn existing iterative hash functions into a message authentication code: one keyed inner pass, one differently keyed outer pass, and an interface that could survive replacement of the hash beneath it. What endured was the…