← all recipes

"Handoff Stream" — show ownership or state moving from one person or system to another. It has a fieldflow layer (solar prominences, aurora, plasma streams, guided matter), a propagate layer (travelling waves through the medium), a link layer (ropes / cloth between neighbours), a memory layer (a decaying trail / hysteresis), and a morph layer (assemble matter into a mark/shape (never words, §11)). Matter follows the field geometry because of fieldflow, not the field-owning force itself. The active render stack is streamlines, field-lines, trails, particles.

Magnetism bends the path between owners and fieldflow carries the object along it — the source cools, the target warms, and a memory trace records the transfer.

Runtime tokens

fieldflow propagate link memory morph

Concepts

handoff

Metrics

handoff current memory state handoff, current, state are host-supplied lanes — drive them with data-field-<metric> (or a domain model); without that, their --field-* stays inert.

Diagnostics

field-lines force-vectors topology

Render

streamlines · field-lines · trails · particles

Reduced motion

a transfer timeline with owner badges and a handoff log

Without motion

the transfer reads as a timeline of owner badges plus a handoff log entry, not a flowing animation

<field-root></field-root>
  <div data-body="fieldflow" data-strength="1" data-range="0" data-feedback></div>
  <div data-body="propagate" data-strength="0.7" data-range="320"></div>
  <div data-body="link memory" data-strength="0.6" data-range="300"></div>
  <div data-body="morph" data-strength="0.5" data-range="280"></div>