Stages K/L/M/N · read-first · tested · gated actions

Operational Dashboard

Operator-friendly status cards, independent loading/error/empty states, strict read-only integrations first, and explicit gates for every action with side effects.

Operator login

Use admin or operator credentials from the local deployment .env.

API readiness

Version / frozen baseline

Operations summary

Agents · read-only live state + local drafts

Cron jobs · schedule / next run / last run / status

Cron safety policy

Pause/resume and create/update are admin-confirmed write-gate operations. Prompt text is separate from delivery routing fields. Recursive cronjob creation/update from cron-run contexts is blocked by the API.

Memory / shared vault · API status

Project memory browser / durable doc links

Safe memory search

Telegram bridge · service status

Model manager / router · status

Providers and models

Routing health / gated S5 readiness

Policy

Read-only status only. Provider keys are never exposed. No provider/model mutations. No Hermes Telegram routing is added unless explicitly approved in a future stage.

Read-only file browser · strict allowlist

Read allowlisted UTF-8 file

No file selected.

Gated terminal commands

No arbitrary shell. Fixed command IDs only. Command previews and execution attempts are audited. Destructive commands are disabled unless separately whitelisted.

No terminal command submitted.

System/service health

Control API health

Recent task/audit history

admin login required...

Write attempts