🏗️ Architecture: How should AI routes be segregated across gograb-space, gogr...

Date: 2026-02-07
Time: 13:18:23 UTC
Session: gspace1-0
Agent: angular
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

How should AI routes be segregated across gograb-space, gograb-admin, and gograb-dev after the app separation?

Task: Remove legacy AI_ROUTES and complete route segregation across 3 apps

🎯 Decision Made

Chosen:

Delete monolithic ai.routes.ts (28 routes). Admin routes already in gograb-admin, dev routes already in gograb-dev. Add missing routes (billing, mind drill-down, triggers, orchestration). Replace AI_ROUTES in gograb-space with minimal space-scoped user routes (/space/:slug/my-ai/intelligence, /space/:slug/my-ai/usage).

Options Considered:

• No alternatives documented

💭 Reasoning

The three-app separation was already 90% complete — gograb-admin and gograb-dev had their own route definitions covering most of the 28 legacy routes. But gograb-space still imported the full monolith via ...AI_ROUTES, exposing all dev/admin dashboards to end users. 5 gaps were found: admin missing billing + 3 mind drill-down routes + wrong UsageDashboard component, dev missing triggers + orchestration. User-facing routes moved inside space/:spaceSlug context for proper spaceGuard scoping. 28 legacy routes mapped to new homes with zero loss.

📁 Files Involved

• apps/gograb-admin/src/app/app.routes.ts
• apps/gograb-dev/src/app/app.routes.ts
• apps/gograb-space/src/app/app.routes.ts
• libs/libs-ai/gograb-ai-lib/src/lib/ai.routes.ts
• libs/libs-ai/gograb-ai-lib/src/index.ts

🔗 Related

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

Auto-generated by MCP Smart Consolidation