The field
A field-ui page has one field. Elements bend it; its density bends them back. Nothing here is a particle pool laid over the page — the page itself is the medium.
Every section below is a body in that field. As one nears the centre of your viewport it gathers attention, and what you dwell on accrues memory.
Reciprocity
The defining law: influence runs both ways. The viewport reads the page, and the page reads the viewport back. A heading you are reading brightens; one you have left dims — but only after a threshold, so a glance does not flicker it.
This reciprocity is what the field buys you over a scroll listener: state with hysteresis, not raw events.
Attention
Attention is the live signal: how centred a section is, scaled by how much of it is visible. It is continuous and momentary — it rises as you arrive and falls as you leave.
Watch the table of contents: the section you are reading is marked current.
Memory
Memory is the slow signal: attention, integrated over time. A section you have truly read stays warm; one you skimmed does not. The left rail of each section fills with its memory, and the contents list carries the same trace.
Memory is why reciprocity feels like reading rather than scrolling — the page remembers where you have been.
Relationships
The cross-references in this page are real relationships, not decoration. The platform reads them from the native HTML — every a[href^="#"] with data-field-relation — into one typed graph, the same graph the topology overlay draws.
A document is a tree; meaning is a graph. The relationship registry recovers the graph the markup already implies.
Reduced motion
Turn on “reduce motion” in your OS and reload. The animation stops; the meaning does not. Attention and memory still track, the current section is still marked, the rails still fill — the values simply snap instead of easing.
Meaning lives in state, not in motion. That is the accessibility contract the platform is built to keep.