Selection Wake
leave a subtle trail of user interaction and selection
Running the actual pattern live via applyPattern() — switch the substrate, stack overlays, watch the signals, or reverse the dynamics. Not a mock.
"Selection Wake" — leave a subtle trail of user interaction and selection. It has a memory layer (a decaying trail / hysteresis), a diffuse layer (spread a quantity over the medium), a fieldflow layer (solar prominences, aurora, plasma streams, guided matter), and a stream layer (flow matter along a heading). Matter follows the field geometry because of fieldflow, not the field-owning force itself. The active render stack is trails, heatmap, particles.
Memory holds the wake while diffuse lets it fade, and fieldflow carries repeated paths into usage trails — transport that remembers where attention has been.
Copy this pattern
<field-root></field-root>
<div data-body="memory" data-strength="0.9" data-range="300" data-feedback></div>
<div data-body="diffuse" data-strength="0.6" data-range="280"></div>
<div data-body="fieldflow" data-strength="0.6" data-range="0"></div>
<div data-body="stream" data-strength="0.5" data-range="320" data-angle="0"></div> <script type="module">
import '@fundamental-engine/elements';
</script>
<field-root></field-root>
<div data-body="memory" data-strength="0.9" data-range="300" data-feedback></div>
<div data-body="diffuse" data-strength="0.6" data-range="280"></div>
<div data-body="fieldflow" data-strength="0.6" data-range="0"></div>
<div data-body="stream" data-strength="0.5" data-range="320" data-angle="0"></div> import { FieldField } from '@fundamental-engine/react';
export default function SelectionWake() {
return (
<FieldField>
<div data-body="memory" data-strength="0.9" data-range="300" data-feedback />
<div data-body="diffuse" data-strength="0.6" data-range="280" />
<div data-body="fieldflow" data-strength="0.6" data-range="0" />
<div data-body="stream" data-strength="0.5" data-range="320" data-angle="0" />
</FieldField>
);
} {
"id": "selection-wake",
"name": "Selection Wake",
"intent": "leave a subtle trail of user interaction and selection",
"naturalField": "weak",
"primitives": [
"memory",
"diffuse",
"fieldflow",
"stream"
],
"bodies": [
{
"body": "memory",
"strength": 0.9,
"range": 300,
"feedback": true
},
{
"body": "diffuse",
"strength": 0.6,
"range": 280
},
{
"body": "fieldflow",
"strength": 0.6,
"range": 0
},
{
"body": "stream",
"strength": 0.5,
"range": 320,
"angle": 0
}
],
"render": [
"trails",
"heatmap",
"particles"
],
"metrics": [
"memory",
"recency",
"trail"
],
"diagnostics": [
"heatmap",
"contours",
"force-vectors"
],
"accessibility": {
"reducedMotion": "selection-history marks with recent-item badges and a static trail rail",
"meaningWithoutMotion": "a static history rail lists recently touched items with recency badges in place of a fading wake"
},
"notes": "Memory holds the wake while diffuse lets it fade, and fieldflow carries repeated paths into usage trails — transport that remembers where attention has been.",
"tier": "applied",
"status": "shipped",
"concepts": [
"wake"
],
"conditions": [
"selected"
]
} See also
- Conflict Field make contradiction, uncertainty, and unstable state visible
- Memory Trace show where a user has been, paused, returned, or accumulated attention
- Decay Notice let stale, temporary, or completed state fade gracefully
- Phase Shift show a state transition: draft → published, pending → complete, hidden → active
- Attention Weather show system urgency, density, and activity across a dashboard
- Navigation Current make routes, breadcrumbs, and likely next paths feel connected