Architecture: How should the gograb-ai app navigation be restructured to s...

Documentation for Sessions

🏗️ Architecture: How should the gograb-ai app navigation be restructured to s...

Date: 2026-03-12
Time: 16:37:41 UTC
Session: gspace1-208.2
Agent: angular
Confidence: 92%
Status: ✅ Documented

📋 Decision Context

Question:

How should the gograb-ai app navigation be restructured to serve different user audiences (developers, admins, executives)?

Task: S208: Metacognition + App Reorganization

🎯 Decision Made

Chosen:

Split observatory (9 mixed tabs) into /operations (5 technical: Agents, System, Sandbox, Failures, Specialization) and /command (5 business: Mission Control, Approvals, Audit, Trust, Costs). Top nav: Home | Operations | Command | Vitto. Existing CommandCenterComponent from gograb-dev wired into /command/mission.

Options Considered:

  1. A: Keep observatory as-is, add new sections alongside
  2. B: Split into Operations + Governance (corporate naming)
  3. C: Split into Operations + Command (unified with existing Command Center)
  4. D: Move everything into Vitto sidebar, no top-level sections

💭 Reasoning

Observatory had 9 tabs mixing 4 audiences (developer, platform engineer, admin, finance) into one flat tab bar. A finance person looking at costs doesn't need sandbox sessions. An end user approving a tool call doesn't need failure chain analysis. The split follows audience separation: /operations for technical monitoring, /command for business oversight. Command Center was already fully built (WebSocket gateway, 30+ event broadcasts) but stranded in gograb-dev — migrating it to /command/mission gives it a proper home with related business tabs. Backward compat via 10 redirect routes from /observatory/*.

📁 Files Involved

🔗 Related

Auto-generated by MCP Smart Consolidation