← all recipes

Electromagnetic operational

Disagreement Charge

make unresolved conflict visible without turning it into noise

frame bodies 0 relationships 0

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

"Disagreement Charge" — make unresolved conflict visible without turning it into noise. It has a charge layer (attract/repel charged matter), a repel layer (carve a void / keep-clear region), a thermal layer (agitate matter at a temperature), a morph layer (assemble matter into a mark/shape (never words, §11)), and a memory layer (a decaying trail / hysteresis). The active render stack is field-lines, heatmap, links, particles.

Opposing claims carry like charge and repel into visible separation, thermal entropy marking heated conflict; once resolved, the claim morphs and decays into memory rather than alarming. Electric pushes, magnetic bends.

Runtime tokens
charge repel thermal morph memory
Concepts
disagreement
Metrics
disagreement entropy resolution memory disagreement, resolution are host-supplied lanes — drive them with data-field-<metric> (or a domain model); without that, their --field-* stays inert.
Diagnostics
causality topology field-lines
Conditions
conflicted
Render
field-lines · heatmap · links · particles
Reduced motion
conflict pairs with a resolution-state column and a disagreement summary
Without motion
each conflict is a labelled pair of claims with a resolved/open state and an entropy score

Copy this recipe

<field-root></field-root>
  <div data-body="charge" data-strength="1" data-range="340" data-spin="1" data-feedback></div>
  <div data-body="repel" data-strength="0.7" data-range="300"></div>
  <div data-body="thermal" data-strength="0.5" data-range="280"></div>
  <div data-body="morph" data-strength="0.4" data-range="220"></div>
  <div data-body="memory" data-strength="0.4" data-range="260"></div>

See also