Page Data
The JSON the page owns, and the store it becomes at runtime.
What page data becomes once the page runs.
At runtime there is one logical keyspace, presented as a view over two underlying dictionaries — data and memory. Reads are data-wins: a path present in data shadows the same path in memory. Every write goes to data.
- Watching a path subscribes to both dictionaries and de-duplicates, so a handler fires at most once per real change.
- A stale memory change for a path shadowed by data produces no merged change and is swallowed.
- Consumers never need to know which bucket a path lives in; the split survives only for persistence and the SSE frames.