Skip to content

Moore's law

The empirical observation that transistor count per economically optimal integrated circuit doubles roughly every two years — a self-fulfilling industry roadmap that coordinated investment across the semiconductor supply chain so the complementary inputs for each process node arrived together.

Core Idea

Moore's law is the empirical observation that transistor count on an economically optimal integrated circuit doubles roughly every two years. The proximate mechanism was photolithographic feature shrink plus expanding viable die size, complemented by Dennard scaling. What distinguishes it from a bare regularity is that it became a self-fulfilling industry roadmap (ITRS/IRDS): the forecast coordinated investment across chip designers, equipment makers, and suppliers so each node's complementary inputs arrived together. The forecast shaped the investment that shaped the outcome.

Scope of Application

Bounded to the semiconductor industry and the computing economy that builds to its cadence; "Moore's law for X" elsewhere is co-instance or analogy.

  • Semiconductor roadmapping — the home: ITRS/IRDS coordinating the supply chain.
  • Chip architecture — committing to transistor-budget-dependent designs before silicon exists.
  • Fab capital planning — setting process-node cadence and plant-capacity timing.
  • Computing-economics analysis — the benchmark in productivity and Solow-residual debates.
  • Adjacent doubling-laws — Koomey's, Kryder's, Cooper's, Edholm's borrowing the cadence shape.

Clarity

Moore's law's sharpest clarification is that the doubling is a coordination device the industry builds to, not a passive physical fact — separating an exogenous "technology permits it" reading from an endogenous "coordinated investment produces it" one. It holds the count axis distinct from clock speed, energy, and delivered performance, making the "More than Moore" transition legible as a change of axis. And it licenses a per-generation binding-constraint question.

Manages Complexity

Forecasting an entire interlocking industry compresses into a single coordinating cadence the industry codifies and resources against, so "will the transistor budget be there?" reads off the roadmap. Two branches ride on it: the count axis held apart from the others (so post-2005 history reads as an axis shift, not collapse), and a per-generation single-binding-constraint reading (yield, resolution, leakage) that renders a slowdown as a reached limit.

Abstract Reasoning

Turning on its endogenous character, the law licenses cadence-as-plan forecasting (commit to a design before silicon exists), self-fulfilling-roadmap diagnosis (why it held where uncoordinated exponentials stall), count-axis discrimination (an axis shift, not collapse), per-generation binding-constraint diagnosis (which single limiter to relax next), and extrapolation-boundary discipline (a "Moore's law for X" carries only if that substrate shares the coordination-plus-learning machinery).

Knowledge Transfer

Within the semiconductor industry the law transfers as a working coordination device across the whole supply chain, mechanistically, because all share the one apparatus it operationalizes. Into the broader computing economy it propagates as a cadence expectation borrowed by sibling laws. Beyond computing the real shared mechanism — industry-coordinated learning-curve doubling — travels as the parents learning_curve, coordination_problem_and_equilibrium_selection, self_fulfilling_prophecy, and exponentiation; the semiconductor apparatus stays home.

Relationships to Other Abstractions

Local relationship map for Moore's lawParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Moore's lawDOMAINPrime abstraction: Exponentiation — is a decomposition ofExponentiationPRIMEDomain-specific abstraction: Bell's Law of Computer Classes — presupposesBell's Law ofComputer ClassesDOMAIN

Current abstraction Moore's law Domain-specific

Parents (1) — more general patterns this builds on

  • Moore's law is a decomposition of Exponentiation Prime

    Moore's Law decomposes to Exponentiation because its portable quantitative skeleton is repeated doubling at an approximately fixed interval.

Children (1) — more specific cases that build on this

  • Bell's Law of Computer Classes Domain-specific presupposes Moore's law

    Bell's recurring class formation presupposes the sustained semiconductor scaling described by Moore's Law, which supplies the cost-and-capability trajectory that repeatedly crosses new feasibility thresholds.

Hierarchy paths (2) — routes to 2 parentless roots

Neighborhood in Abstraction Space

Moore's law sits in a sparse region of the domain-specific corpus (75th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (309 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-07-12