Designing a Private Command Center Page

A private command center gives humans a place to supervise Rocky. It should not be a flashy dashboard full of vanity metrics. It should answer: what changed, what needs approval, and what happened recently?

Core modules

• Approvals: draft messages, posts, purchases, bookings, or config changes awaiting review
• Alerts: failures, deadlines, exceptions, broken pages, or urgent messages
• Recent actions: verified changes and links to evidence
• Watchlist: sources Rocky checks regularly
• Run controls: pause, resume, or request a manual run where appropriate
• Policy notes: what Rocky may do automatically and what requires a human

Design principles

Keep the page private by default. Do not expose customer data, secrets, private logs, or internal notes to public routes. Use role-aware access if multiple users need different permissions.

Good approval card

Action: Draft reply to new lead
Risk: customer contact
Evidence: source email summarized
Buttons: approve, edit, reject

Verification

Before launch, test logged-out access, direct URLs, mobile layout, and any API endpoints behind the page. If anonymous users can see private state, the command center is not ready.