Architecture: Should /intelligence route stay in gograb-ai or be removed?

Documentation for Sessions

🏗️ Architecture: Should /intelligence route stay in gograb-ai or be removed?

Date: 2026-02-11
Time: 17:06:05 UTC
Session: gspace1-105.14
Agent: angular
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

Should /intelligence route stay in gograb-ai or be removed?

Task: gograb-ai production readiness - remove /intelligence route

🎯 Decision Made

Chosen:

Remove entirely and add cross-app link

Options Considered:

Keep in gograb-ai as-is
Redirect to gograb-admin
Remove entirely and add cross-app link
Keep as simplified navigation hub

💭 Reasoning

gograb-admin already has /intelligence/platform, /intelligence/cursor-agents, /intelligence/vitto-hubs with full navigation. gograb-dev has /intelligence/pyramid, /intelligence/triggers, /intelligence/orchestration, /intelligence/memory-map, /intelligence/command-center. The exact same AiDashboardV2Component was used in gograb-ai /intelligence AND gograb-dev /mcp/status — pure duplication. Each app should own its domain: gograb-ai = embeddable panel/observatory, gograb-admin = platform management/intelligence, gograb-dev = developer tools/debugging. Dashboard link now opens gograb-admin in new tab with dynamic port derivation.

📁 Files Involved

apps/gograb-ai/src/app/app.routes.ts
apps/gograb-ai/src/app/pages/dashboard/dashboard.component.ts

🔗 Related

Decision ID: dev_1770829565674_sc8kffb
Session: 105
Workspace: gspace1

Auto-generated by MCP Smart Consolidation