← all recipes

Strong systems

Provenance Trail

preserve the origin and transformation history of content or data

frame bodies 0 relationships 0

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

"Provenance Trail" — preserve the origin and transformation history of content or data. It has a memory layer (a decaying trail / hysteresis), a link layer (ropes / cloth between neighbours), a morph layer (assemble matter into a mark/shape (never words, §11)), and a cohesion layer (flocking — pull toward neighbours). The active render stack is links, trails, particles, field-lines.

Strong binding keeps sources fused to content while memory holds the trace and morph records each transformation; lineage stays inspectable without flooding the view.

Runtime tokens
memory link morph cohesion
Concepts
provenance lineage
Metrics
provenance memory transform-count source-strength provenance, transform-count, source-strength are host-supplied lanes — drive them with data-field-<metric> (or a domain model); without that, their --field-* stays inert.
Diagnostics
causality topology inspector
Render
links · trails · particles · field-lines
Reduced motion
a provenance drawer with a lineage list and source badges
Without motion
history becomes an ordered lineage list with source badges and a transform count per step

Copy this recipe

<field-root></field-root>
  <div data-body="memory" data-strength="1.1" data-range="320" data-feedback></div>
  <div data-body="link" data-strength="0.8" data-range="360"></div>
  <div data-body="morph" data-strength="0.5" data-range="260"></div>
  <div data-body="cohesion" data-strength="0.6" data-range="280"></div>

See also