UI v2 01 — Reframe home IA around operational flows

[fabriziosalmi]

Objective

Reframe the UI shell and home around operator workflows rather than backend modules. The top-level experience should answer: what is happening now, what needs attention, and what can be done next.

Why

The current UI is structured as a set of feature areas. UI v2 needs a true operational entry point so users orient themselves in seconds instead of navigating tabs to reconstruct state.

Likely files touched

• ui/index.html
• ui/main.js
• ui/components/content.js
• ui/components/sidebar.js
• ui/components/threats.js
• ui/components/security.js
• ui/services/store.js
• ui/services/api.js
• proxy/routes/admin.py

Example implementation surface

• Introduce a home shell with three persistent zones: Now, Needs Attention, Do Next.
• Add a global context bar for environment, auth scope, active time range, workspace, and incident state.
• Add a backend summary payload for the home surface, for example:

DashboardSummary
- now: health, throughput, degradation state, auth mode
- attention: prioritized anomalies with severity and blast radius
- do_next: suggested actions and follow-up tasks
- recent_changes: config/plugin/endpoint/guard mutations

Acceptance criteria

• A first-time operator can understand current state without opening a second view.
• The landing page is organized by operator intent, not by backend subsystem.
• The shell establishes a stable mental model reused by downstream views.