operator-panel

Build a local operator panel by organizing UI components and backend endpoints to surface status, runs, experiments, portfolio state, settings, and logs. This ensures observability and governance for paper-research workflows without enabling live trading or runtime changes.

An operator panel for paper-research workflows is a local, safety-bound UI surface. It exposes advisory decision support, governance history, and supervisor state while restricting all critical controls to remain non-editable and prevent runtime alterations.

Surface logs and settings by wiring backend endpoints into the panel UI while keeping critical controls explicitly guarded or non-editable. This restricts runtime effects to advisory surfaces, providing auditable summaries and maintaining safety boundaries.

No, the operator panel does not support live trading or runtime changes. It maintains safety and governance requirements by restricting runtime effects to advisory surfaces, keeping all critical controls non-editable, and providing only auditable summaries.

No, you cannot use this operator panel for public product UI or live trading controls. It is designed specifically as a local-only surface for paper-research workspaces to maintain safety boundaries and bounded governance.

Extend the operator panel UI safely by editing app/operator_panel.py and app/ui/* components. This allows you to surface learning-readiness indicators and governance details while ensuring all integrations remain local-only and advisory.