Hyperflow UI
Concepts

State ownership

Where transport, behavior, and presentation state belong.

Work in progress. This documentation is actively being written and may change.
ConcernOwner
HTTP, WebSocket, protocol parsing@hyperflow/client
Session reconciliation, actions, application behavior@hyperflow/react
Markup, tokens, layout, purely visual state@hyperflow/chakra-ui

This separation is the extension contract. A component may own local menu or collapse state, but it should not call the client directly or duplicate headless session derivation.