Architecture: Where should the /intelligence route live across gograb apps...

Documentation for Sessions

🏗️ Architecture: Where should the /intelligence route live across gograb apps...

Date: 2026-02-11
Time: 17:12:28 UTC
Session: gspace1-105.18
Agent: angular
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

Where should the /intelligence route live across gograb apps?

Task: Session 105.3: Remove /intelligence from gograb-ai, enforce app boundaries

🎯 Decision Made

Chosen:

Remove from gograb-ai. Keep in gograb-admin (full platform intelligence) and gograb-dev (developer intelligence tools). Dashboard link cross-navigates to admin app.

Options Considered:

Keep /intelligence in all three apps
Remove from gograb-ai only
Redirect from gograb-ai to admin

💭 Reasoning

App boundaries: gograb-ai = embeddable AI panel + observatory (the product surface users/extensions interact with). gograb-admin = platform management including intelligence/training/billing. gograb-dev = developer debugging/monitoring. The AiDashboardV2Component was duplicated in gograb-ai /intelligence AND gograb-dev /mcp/status. gograb-admin already has /intelligence/platform, /cursor-agents, /vitto-hubs. Each app owns its domain. Dashboard Quick Actions now link to admin app's intelligence page using dynamic port derivation (AI port - 300 = admin port by workspace convention).

📁 Files Involved

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

🔗 Related

Decision ID: dev_1770829947941_6o2rt6p
Session: 105
Workspace: gspace1

Auto-generated by MCP Smart Consolidation