Node status
What does this mean?
A StegVerse Node is the continuity and capability boundary through which this device participates in StegVerse. The status at the top of a page tells you which Node class this browser currently represents and whether that class is actually established.
Why most StegVerse functions need a Node
A Node gives governed functions a continuity anchor: the system can distinguish an already-established device context from a new one, preserve evidence across later actions, and evaluate function-specific capabilities against the correct boundary. A Node is not a permission slip for every StegVerse function.
Node established does not mean capability established.
Nothing is connected just because you opened a page
For a new device, the default is Unselected Node not established. Public information remains readable. StegVerse does not treat page arrival as consent to create persistent Node state.
Only an unmistakable affirmative action such as Connect a StegVerse Node may begin Node establishment. Returning pages may read enough existing local continuity to display your already-established state, but they may not silently repair, replace, reconnect, elevate, or re-register it.
Observation does not authorize transition.
What happens after connection?
An established Unselected Node is a real continuity-bearing Node with a deliberately bounded introductory capability envelope. You can then choose the persistent operating boundary that matches how you want this Node to participate.
Node class is not rank
Private Sovereign, Main Ecosystem, and StegOS Node classes describe sovereignty, custody, and runtime eligibility. They do not form Bronze/Silver/Gold levels, and a more capable Node does not receive greater governance authority.
Node status describes capability and sovereignty—not rank.