Token flow

Show the runtime as a camera move, not a wiring diagram.

This chapter follows the same HAWF-2M stages, but the emphasis is cinematic: x enters, p routes, m writes evidence, z condenses the hub, and n becomes the next-step signal.

  • The scene should make spatial relationships obvious before it explains implementation details.
  • Zoom and pan turn the explainer into an inspectable instrument panel instead of a static graphic.
  • The motion is tighter than the overview, but it still needs to feel readable on touch devices.

Trace mode

Every token’s microsteps stay visible.

The camera stays loose, the ribbon breathes, and each stage keeps its own depth so the runtime reads like an instrument panel.

Drag to pan · pinch / wheel to zoom
X · 1Read xtoken + local contextP · 2Project pfield / position routingM · 3Write mmemory evidenceZ · 4Score zhub aggregationN · 5Emit nnext-step signal
Reading lens

Each stop in the chain answers a different question.

  • x anchors the current token and local context.
  • p adds routing and positional bias to the path.
  • m writes memory evidence before the hub mixes it down.
  • z condenses the field and n exposes the next-step score.
Update rule

The runtime stays faithful even when the presentation gets richer.

The redesign is about framing, hierarchy, and legibility. The underlying state transition stays the same while the scene makes its order of operations easier to parse.