This page lists every Orange Pill Wiki entry hyperlinked from Melvin Conway — On AI. 24 entries total. Each is a deeper-dive on a person, concept, work, event, or technology that the book treats as a stepping stone for thinking through the AI revolution. Click any card to open the entry; in each entry, words colored in orange link to other Orange Pill Wiki entries, while orange-underlined words with the Wikipedia mark link to Wikipedia.

The quality of a system whose every decision reflects one intelligence operating according to unified principles—historically rare, now common.
The gradual accumulation of unrecorded coupling decisions that produces accidental system structure—enabled by zero-cost refactoring.
The multiplicity of perspectives, experiences, and ways of seeing a problem that a team provides as a byproduct of its existence — and that the solo builder working with AI must now deliberately import to compensate for its absence.
The function (perspective diversity, challenge generation, accountability) remains essential; the process (meetings, reports, hierarchical review) is obsolete.
Organizations designing systems produce designs that copy their communication structures — the 1968 observation that became software engineering's most durable principle.
Self-imposed maintenance of component boundaries that organizational structure no longer enforces—the hardest architectural skill in the AI age.
The cultivated capacity — developed through years of practice, refined by the study of failures, calibrated by direct encounter with materials and forces — to sense, before calculation confirms it, that a design or situation is wrong. The s…
The formal operational capacity to reflect on one's own cognitive processes — the last and most demanding of the new cognitive tools, and the one required to interrogate the premises of an identity framework.
Claude Shannon's 1948 distinction between the message you intend to transmit and everything that interferes with its transmission — the spine of information theory and the diagnostic framework for what an amplifier carries.
Vagueness, ambiguity, and contradiction present in the originator's mental model before entering any communication channel—the signal quality AI faithfully amplifies.
Capra's synthesis of the systems tradition — the discipline of attending to relationships, patterns, and context rather than components in isolation, and the cognitive method adequate to phenomena that component-level analysis systematical…
Amazon's decree that all teams expose functionality through defined interfaces only—no shared databases, no back-channels—engineering communication to shape architecture.
The multiplicative signal degradation that occurs as messages pass through serial human interpreters—the children's game made organizational reality.
Crawford's claim that sustained attention to resistant material is not merely a cognitive skill but a moral achievement — and that AI-mediated workflows threaten the conditions under which such attention can be cultivated.
Deliberately structuring one's own thinking to produce desired system architecture—Conway's maneuver turned inward when the org chart dissolves.
The deliberate structuring of an organization to produce a desired system architecture—working with Conway's Law rather than against it.
A system designed by a single cognitive architecture rather than an organizational network—coherent, fast, and vulnerable to systematic blind spots.
The threshold crossing after which the AI-augmented worker cannot return to the previous regime — The Orange Pill's central metaphor for the qualitative, irreversible shift in what a single person can build.
Perrow's term for systems in which processes are time-dependent, invariant in sequence, and admit no slack — so that when disruption occurs, it propagates at the speed of the process itself, outrunning the cognition required to intervene.
Signal degradation introduced by the organizational communication chain—distinct from source noise, and the species AI tools eliminate.
Amazon's principle that no team should be larger than can be fed by two pizzas—limiting communication overhead to preserve architectural coherence.