Physical Transformation AtlasPTA
Phenomenon · phenomenon:casimir-effect

Casimir effect

Two closely spaced conducting plates attract because the vacuum field modes between them are restricted. A static force from the ground state; it does one-off work while the plates close and none in a cycle.

Quantum transportfirst reported 1948

Atlas record: 3 claims reference this phenomenon — 3 established.

Explorerelations · matrix context · sources · cite

conditions: vacuum required
3claims0enumerated routes0routes with complete-composition evidence0candidate routes not searched2cited sources

Relations

drives · 1
Quantum vacuum fluctuations—drives→Casimir effectestablished
  • two conducting plates closer than a micrometre; force measured to 5%
The attraction is real and measured. It does one-off work while the plates approach; separating them again costs at least as much. No energy ledger is recorded because no continuous conversion exists.
member of · 1
Casimir effect—member of→Fluctuation / information-drivenestablished
bounded by · 1
Casimir effect—bounded by→Second law of thermodynamicsestablished

Matrix context

D = disequilibrium row · C = coupling family column. A cell reads the state of the atlas for that pair.

D.22 × C.31 · Quantum vacuum fluctuations × Fluctuation / information-driven · Established
family: Fluctuation / information-driven (C.31)

Cited sources · 2

  1. [1]
    S. K. Lamoreaux. Demonstration of the Casimir force in the 0.6 to 6 μm range (1997)
    Physical Review Letters 78, 5 · doi:10.1103/PhysRevLett.78.5 · crossref ✓ 2026-09-19 · record
  2. [2]
    M. Bordag, U. Mohideen, V. M. Mostepanenko. New developments in the Casimir effect (2001)
    Physics Reports 353, 1–205 · doi:10.1016/S0370-1573(01)00015-1 · crossref ✓ 2026-09-19 · record

Cite this entity

Physical Transformation Atlas (2026). entity phenomenon:casimir-effect: Casimir effect. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/phenomenon/casimir-effect

Ids and matrix addresses are stable across revisions; the revision hash identifies the exact canonical files the record was compiled from and is meta.data_hash in every /api export. Reuse terms: see the license field in any export.