Legacy bridge
Explain how the architecture story became a state story.
The legacy chapter is the hinge in the atlas. It should show what the first narrative got right, where it was still coarse, and why the HAWF-2M runtime demanded a more explicit notion of state.
- The original model introduced the coupled-field idea clearly.
- The newer runtime needed inspectable memory banks, source weighting, and state slices.
- This page should make that conceptual jump feel continuous instead of abrupt.
Mode switch
Legacy ThermoField
The first pass kept the language-model story close to the field model, but the state system was still coarse and mostly architectural.
What the viewer should notice
Legacy emphasis
Show the big idea first: a coupled field that lives next to the model.
HAWF-2M emphasis
Show the runtime next: explicit session state, bank updates, and source-aware writes.
Why the bridge matters
It turns a broad systems pitch into a runtime you can actually inspect.
That shift is what makes the rest of the explainer legible: the state route can show concrete tensors, and the energy route can show why those tensors relax the way they do.