Holon Context Switching
Holon Context Switching is the dynamic UX and logic layer that allows users to fluidly move between nested holons, each representing a distinct scope of governance, resources, identity, and simulation. This module enables localized action within a larger system—mirroring how individuals, teams, and organizations navigate multiscale networks.
What Is a Holon Context?
A holon context refers to the currently active holon for a given user session. It determines:
What data is visible or editable Which proposals, simulations, and dashboards are shown What roles, permissions, and automations apply The default scope for creating new items (proposals, resources, feedback) Why Context Switching Matters
Enables multiscale interaction — from team → org → network Supports future access control per holon Provides clarity — users always know "where" they are acting from Powers recursive simulation and governance at any layer UI Integration in Lovable
🌐 Header Context Dropdown: allows switching between holons visible to the user 🧭 Sidebar Context Panel: reflects current context and breadcrumbs ➕ Create Buttons: auto-populate with current holon_id 👁️ Filters + Views: scoped to holon context unless global view enabled System Logic
Auto-select default holon on login (first holon user is a member of) Store context in user session (optional: Supabase session or localStorage) Query filtering and UI rendering respect current_holon_id Future Enhancements
Role-based holon switching (only allow switching into roles user has access to) Multi-context tabs for power users API endpoint for setting/retrieving active context (for automations) Admin view to impersonate holon contexts for testing Would you like to:
Implement session context binding logic next? Visualize holon switching in a UX flow? Build onboarding flows that guide users into their default holon?