Convention: Where should production URLs be documented as the canonical ...

Documentation for Sessions

📏 Convention: Where should production URLs be documented as the canonical ...

Date: 2026-02-03
Time: 03:22:05 UTC
Session: editor2-76.91
Agent: documentation
Confidence: 100%
Status: ✅ Documented

📋 Decision Context

Question:

Where should production URLs be documented as the canonical reference to prevent mistakes?

Task: Session 82.5 - Environment-Aware URLs: Production URL source of truth

🎯 Decision Made

Chosen:

Use environment.shared.ts as canonical reference

Options Considered:

Keep URLs in multiple places (docs, code, configs)
Use environment.shared.ts as single source
External configuration file (JSON/YAML)

💭 Reasoning

Made mistake of inventing mcp.gograb.space instead of checking actual config. environment.shared.ts already exists, is well-documented, TypeScript provides type safety, used by all Angular apps, has clear comments with Railway URLs. Easy to reference during development. Single source of truth prevents URL inconsistencies.

📁 Files Involved

apps/gograb-space/src/environments/environment.shared.ts

🔗 Related

Decision ID: dev_1770088921551_6ani3wo
Session: 76
Workspace: editor2

Auto-generated by MCP Smart Consolidation