← all recipes

Weak systems

Threshold Bloom

reveal meaningful state changes only when a threshold is crossed

frame bodies 0 relationships 0

Running the actual recipe live via applyRecipe() — not a mock.

"Threshold Bloom" — reveal meaningful state changes only when a threshold is crossed. It has a gate layer (admit or deflect matter at a boundary), a morph layer (assemble matter into a mark/shape (never words, §11)), a spawn layer (emit new matter (a budgeted source)), a charge layer (attract/repel charged matter), and a memory layer (a decaying trail / hysteresis). The active render stack is metaballs, heatmap, particles, trails.

A weak event waits quietly until the gate opens, then morph and spawn bloom the transition while charge marks the moment; memory keeps the event inspectable after it settles.

Runtime tokens
gate morph spawn charge memory
Concepts
threshold bloom
Metrics
threshold activation heat memory threshold, activation, heat are host-supplied lanes — drive them with data-field-<metric> (or a domain model); without that, their --field-* stays inert.
Diagnostics
causality energy inspector
Conditions
threshold
Render
metaballs · heatmap · particles · trails
Reduced motion
a threshold marker with a status badge and an event log entry
Without motion
crossing the threshold flips a status badge and writes a dated event log entry instead of a bloom

Copy this recipe

<field-root></field-root>
  <div data-body="gate" data-strength="1" data-range="280" data-feedback></div>
  <div data-body="morph" data-strength="0.7" data-range="260"></div>
  <div data-body="spawn" data-strength="0.6" data-range="300"></div>
  <div data-body="charge" data-strength="0.5" data-range="320" data-spin="1"></div>
  <div data-body="memory" data-strength="0.5" data-range="240"></div>

See also