← all recipes

"Recovery Path" — guide users back from error, drift, or interrupted state. It has a memory layer (a decaying trail / hysteresis), a morph layer (assemble matter into a mark/shape (never words, §11)), a link layer (ropes / cloth between neighbours), a fieldflow layer (solar prominences, aurora, plasma streams, guided matter), and a gravity layer (universal attraction toward mass). Matter follows the field geometry because of fieldflow, not the field-owning force itself. The active render stack is field-lines, streamlines, links, particles.

When a process fails or interrupts, memory holds the last coherent path while gravity pulls the user back toward it and fieldflow carries them along the guided return, morphing the broken state back into a stable one.

Runtime tokens

memory morph link fieldflow gravity

Metrics

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

Diagnostics

heatmap prediction causality

Conditions

stale

Render

field-lines · streamlines · links · particles

Reduced motion

a recovery checklist with a last-good-state marker and a restore path

Without motion

the last coherent state is marked and recovery is an ordered checklist back to it, not a generic error screen

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