Physical Transformation AtlasPTA
Claim · claim:thermal-expansion-produces-stress

Thermal expansion —produces→ Mechanical stress or strain

The atlas records this claim as established: the thermal expansion produces a mechanical stress or strain under the conditions below.

establishedledger mechanical → mechanicalrecord reviewed 2026-09-21

Exploreconditions · evidence · matrix context · uses · cite

2cited sources35enumerated routes using it1routes with composition evidence2recorded pathways

Conditions

  • non-uniform thermal expansion is mechanically incompatible across adjacent regions of a solid, or is constrained by an adjoining material or structure, producing a strain or stress gradient; the constraining region may be the cooler part of the same continuous specimen rather than a separate stiffer body
regime: solid

Evidence · 2

  1. [1]
    J. F. Nye. Physical Properties of Crystals: Their Representation by Tensors and Matrices (1985)
    Oxford University Press · book, no DOI · record
  2. [2]
    S. Iwakiri, Y. Miyata, T. Mori. Observation of universal thermopolarization effect in insulators (2026)
    arXiv:2605.17224 (17 May 2026), National Institute for Materials Science, Tsukuba · arxiv.org/abs/2605.17224 · record

Related matrix context

This claim does not itself create a matrix cell. The context below belongs to Thermal expansion, the phenomenon it is about.

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

Uses of this claim

recorded pathways · 2
other enumerated routes · 33 (first 24 shown)

all 35 routes are in /api/paths.json filtered by claims ∋ claim:thermal-expansion-produces-stress

Cite this claim

Physical Transformation Atlas (2026). claim claim:thermal-expansion-produces-stress: Thermal expansion —produces→ Mechanical stress or strain. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/claim/thermal-expansion-produces-stress

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.