← all patterns

Electromagnetic core First release

Signal Path

show information flowing through citations, dependencies, or routes

Running the actual pattern live via applyPattern() — switch the substrate, stack overlays, watch the signals, or reverse the dynamics. Not a mock.

"Signal Path" — show information flowing through citations, dependencies, or routes. It has a charge layer (attract/repel charged matter), a propagate layer (travelling waves through the medium), and a fieldflow layer (solar prominences, aurora, plasma streams, guided matter). Matter follows the field geometry because of fieldflow, not the field-owning force itself. The active render stack is streamlines, field-lines, trails.

A signal travels source → target along declared relationships: charge sets polarity, propagate carries the wave, fieldflow carries matter along the structure. Electric pushes, magnetic bends, fieldflow carries.

Runtime tokens
charge attract/repel charged matterpropagate travelling waves through the mediumfieldflow solar prominences, aurora, plasma streams, guided matter
Metrics
signal a semantic lane — drive it with data-field-<metric> (or a domain model); without that its --field-<metric> stays inertstrength a semantic lane — drive it with data-field-<metric> (or a domain model); without that its --field-<metric> stays inert signal, strength are host-supplied lanes — drive them with data-field-<metric> (or a domain model); without that, their --field-* stays inert.
Diagnostics
field-lines causality force-vectors
Render
streamlines · field-lines · trails
Reduced motion
a persistent path line with step markers replaces the travelling signal
Without motion
the route is also an ordered list of steps with a current-step state

Copy this pattern

<field-root></field-root>
  <div data-body="charge" data-strength="1" data-range="300" data-spin="1"></div>
  <div data-body="propagate" data-strength="0.8" data-range="360"></div>
  <div data-body="fieldflow" data-strength="0.8" data-range="0"></div>

See also