Physical Transformation AtlasPTA
Claim · claim:fluid-flow-carrier-drives-streaming

Fluid flow —drives→ Streaming potential

The atlas records this claim as replicated: a fluid flow drives the streaming potential under the conditions below.

replicatedledger kinetic → electrical · loss to thermalrecord reviewed 2026-09-20

Exploreconditions · evidence · matrix context · uses · cite

2cited sources34enumerated routes using it1routes with composition evidence3recorded pathways

Conditions

  • the produced liquid flow passes a charged surface or through a charged channel; the charged boundary is a condition of the step
  • not something the upstream flow provides
regime: aqueous medium required · bulk flow required · charged surface required

Evidence · 2

  1. [1]
    J. Yin, et al.. Generating electricity by moving a droplet of ionic liquid along graphene (2014)
    Nature Nanotechnology 9, 378–383 · doi:10.1038/nnano.2014.56 · crossref ✓ 2026-09-19 · record
  2. [2]
    J. Yang et al.. Electrokinetic microchannel battery by means of electrokinetic and microfluidic phenomena (2003)
    Journal of Micromechanics and Microengineering 13, 963 · doi:10.1088/0960-1317/13/6/320 · crossref ✓ 2026-09-19 · record

Related matrix context

This claim does not itself create a matrix cell. The context below belongs to Streaming potential, 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 · 3
other enumerated routes · 31 (first 24 shown)

all 34 routes are in /api/paths.json filtered by claims ∋ claim:fluid-flow-carrier-drives-streaming

Cite this claim

Physical Transformation Atlas (2026). claim claim:fluid-flow-carrier-drives-streaming: Fluid flow —drives→ Streaming potential. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/claim/fluid-flow-carrier-drives-streaming

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.