🏗️ Architecture: How should the 4-app route strategy be structured after remo...

Date: 2026-02-07
Time: 14:11:19 UTC
Session: gspace1-0
Agent: orchestrator
Confidence: 92%
Status: ✅ Documented

📋 Decision Context

Question:

How should the 4-app route strategy be structured after removing the legacy AI_ROUTES monolith?

Task: Perfect 4-app route strategy with user AI dashboard

🎯 Decision Made

Chosen:

4-app segregation: gograb-space (user-facing with /space/:slug/my-ai/), gograb-admin (platform admin with /ai/, /agents/, /intelligence/), gograb-dev (developer tools with /mcp/, /agents/, /intelligence/, /analytics/, /testing/, /learning/), space-admin (space owner admin with /ai/usage, /ai/assistant, /ai/intelligence). Each app uses appropriate guard (authGuard for space, strictAuthGuard for admin/dev/space-admin).

Options Considered:

• No alternatives documented

💭 Reasoning

Clean separation by audience: end users see only their space-scoped AI data, platform admins see global management, developers see internal tools, space owners manage their space's AI config. Space-admin upgraded from placeholder (no auth, no routes) to proper app with strictAuthGuard, login, and AI admin routes. User dashboard uses AiExperienceHubComponent for a rich landing page.

📁 Files Involved

• apps/gograb-space/src/app/app.routes.ts
• apps/gograb-admin/src/app/app.routes.ts
• apps/gograb-dev/src/app/app.routes.ts
• apps/space-admin/src/app/app.routes.ts
• apps/space-admin/src/main.ts

🔗 Related

• Decision ID: dev_1770473479582_4zike80
• Session: 0
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation