← all recipes

"Flow Checkpoint" — stabilize multi-step flows around milestones. It has a fieldflow layer (solar prominences, aurora, plasma streams, guided matter), a link layer (ropes / cloth between neighbours), a cohesion layer (flocking — pull toward 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, links, field-lines, particles.

Multi-step flows form a current that fieldflow carries forward, but checkpoints bind like strong anchors: completed milestones hold structure with cohesion while progress keeps streaming ahead (the strong bind stabilizes, transport carries).

Runtime tokens

fieldflow link cohesion memory morph

Metrics

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

Diagnostics

topology force-vectors prediction

Render

streamlines · links · field-lines · particles

Reduced motion

a stepper with a checkpoint rail and completed-step markers

Without motion

the flow is an ordered stepper; completed milestones are marked and anchor the remaining steps

<field-root></field-root>
  <div data-body="fieldflow" data-strength="0.9" data-range="0" data-feedback></div>
  <div data-body="link" data-strength="0.7" data-range="320"></div>
  <div data-body="cohesion" data-strength="0.7" data-range="300"></div>
  <div data-body="memory" data-strength="0.5" data-range="260"></div>
  <div data-body="morph" data-strength="0.4" data-range="220"></div>