Stored-Program Architecture
Alan Turing's 1936 theoretical machine and John von Neumann's 1945 engineering specification established the architectural principle that defines essentially all modern computers: instructions and data occupy the same memory and are treated identically by the machine. The program can operate on itself. The instruction is the data. This is not merely a useful engineering choice. Read through Wittgenstein's framework, it is a philosophical commitment — the commitment that meaning is exhausted by formal structure — realized at the hardware level. Every computer ever built, from ENIAC to the laptop on which these words were composed, embodies it.
In the AI Story
The architecture's elegance consists in its resolution of the representation problem. There is no gap between what the machine does and what its instructions mean, because the instructions mean nothing beyond what the machine does. The stored program is the picture theory in silicon: structure and meaning are identical, and understanding the program consists in tracing its operations.
The commitment was productive beyond measure. The architecture enabled software as an industry, general-purpose computing as a practice, and the entire edifice of modern digital civilization. The commitment was also restrictive. It committed every computer ever built to a framework in which meaning-as-use has no structural expression — the machine can execute an instruction, but cannot represent why the instruction matters, or what form of life the instruction serves.
The gap between structure and meaning is the gap every user of a computer has felt, however inarticulate their awareness of it, every time they struggled to make a machine understand what they wanted. It is the gap the Orange Pill Cycle identifies as the translation cost. The stored-program architecture is the physical form of that gap.
The language interface does not dissolve the architecture. The processor still executes stored-program instructions. The compiler still maps formal structures. What has changed is that the human no longer needs to interact with the architecture directly. A natural-language-model mediates between the human's form of life and the machine's formal architecture, absorbing the Tractarian commitment on the human's behalf.
Origin
Theoretical foundation: Alan Turing's 1936 paper On Computable Numbers. Engineering realization: John von Neumann's 1945 First Draft of a Report on the EDVAC, which codified the architecture under the name it now bears. First practical implementations: the Manchester Baby (1948), EDSAC (1949), and IBM's early commercial machines.
Key Ideas
Instructions as data. Programs can manipulate themselves because instructions occupy the same memory space as data.
Structure is meaning. The program's meaning is exhausted by the operations it specifies; no interpretive frame is needed or represented.
Philosophical commitment in hardware. The architecture embodies the picture theory of meaning at the physical level.
Productive restriction. Enabled modern computing; excluded meaning-as-use from the machine's representational vocabulary.
Persistence under the interface. Natural language interfaces mediate but do not replace the architecture; the Tractarian commitment still runs beneath.
Appears in the Orange Pill Cycle
Further reading
- Alan Turing, On Computable Numbers, with an Application to the Entscheidungsproblem (1936)
- John von Neumann, First Draft of a Report on the EDVAC (1945)
- George Dyson, Turing's Cathedral (2012)
- Martin Davis, The Universal Computer (2000)