Surface energy difference → Electrical work
Surface energy differenceDroplet contact electrificationSeparated surface chargeElectrical work
Epistemic state of the route
- known constituent relations
- 3 / 3 established or replicated · weakest constituent replicated
- constituent maturity floor
- K4 · experimentally observed
- search for this exact route
- Not assessed — complete composition not searched.
- recorded-pathway overlap
- none recorded
- route-level evidence
- 0 sources for the complete composition · 3 cited by the constituent steps
- boundaries and interfaces
- BOUNDARY compatible · no region transition
Explorematrix context · physics checks · steps · route evidence · constituent evidence · cite
Matrix context
D = disequilibrium row · C = coupling family column. A cell reads the state of the atlas for that pair.
D.15 × C.12 · Surface energy difference × Triboelectricfamily: Triboelectric
Steps
- 01surface → electrical · loss to thermal
- water droplets impacting a pre-charged PTFE surface bridging to an electrode
liquidrefs [1] [2] - 02electrical → electricalrefs [1] [2]
- 03electrical → electrical · loss to thermal
- electrodes on the charged surfaces connected through a load
refs [3]
Evidence for the complete composition · 0
No source on record for this exact composition. The sources below support the individual steps, not the route as a whole.
Evidence for the constituent relations · 3
- [1]W. Xu, et al.. A droplet-based electricity generator with high instantaneous power density (2020)
- [2]J. Yin, et al.. Generating electricity by moving a droplet of ionic liquid along graphene (2014)
- [3]H. B. Radousky, H. Liang. Energy harvesting: an integrated view of materials, devices and applications (2012)
Cite this route
Physical Transformation Atlas (2026). route p-1ae841e969: Surface energy difference → Droplet contact electrification → Separated surface charge → Electrical work. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/path/1ae841e969
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.