01 / landing
A token arrives with a clear point of view
The first beat should feel calm and directed. Readers need one object, one path, and one sentence that explains what this machine is about to move.
Overview / scrollytelling system
Make the runtime feel inevitable.
The goal of this explainer is not to pile up cards. It is to lead readers through one continuous model: tokens enter, fields route, energy relaxes, memory writes, and the machine leaves behind a state you can inspect.
scrollytelling runtimefree-energy descentstate-driven memorymobile-first motion
What this rebuild is optimizing for
- A single visual language shared across overview, state, energy, memory, and token flow.
- Clear mobile hierarchy so the story still reads well when the layout stacks.
- Technical fidelity without losing pacing, typography, or narrative confidence.
Primary arc Token -> route -> relax -> write
Narrative mode Sticky scene + guided text rail
Design goal Editorial, technical, and readable
Live narrative stage
A token arrives with a clear point of view
The first beat should feel calm and directed. Readers need one object, one path, and one sentence that explains what this machine is about to move.
Active equation
02 / routing
Routing should escort the eye, not interrupt it
The field bends the signal toward the next decision. That movement needs to feel guided and inevitable, like a line of thought tightening into structure.
03 / energy
Energy makes the runtime legible
The explainer gets stronger when free-energy descent feels visible rather than abstract. Brighter cores, darker floor tones, and a cleaner equation make the cost function feel real.
04 / relax
Relaxation should feel precise on small screens
This is where the story usually loses discipline. The state needs to settle in one crisp sweep, with labels, spacing, and motion that still feel premium on mobile.
05 / write
The write lands as a durable result
The closing beat should emphasize persistence rather than spectacle. The memory node gets the halo, the path completes, and the viewer leaves with a lasting mental model.
Chapter map
The rest of the explainer should feel like one atlas.
Each chapter below drills into one part of the runtime, but they should all inherit the same voice: editorial top matter, a confident centerpiece, and then a precise technical breakdown.
- The overview establishes the emotional and visual grammar for every other page.
- State and token flow carry the heavy visual lift, so they need especially tight framing.
- Energy, memory, and anytime inference should explain, not merely restate, the equations.
How the original coupled-field narrative became a runtime with inspectable state.
HAWF-2M stateThe x / p / m / z / n state map, source weighting, and memory-bank geometry.
Energy lensThe free-energy terms that explain why relaxation moves the way it does.
Token flowA camera-driven pass through the runtime from read x to emit n.
Memory writingMerge, replace, and the slot-bank decisions that shape persistence.
Anytime inferenceConfidence thresholds, early exits, and the cost of another step.