From Spotify (Gary Niemen): "The Golden Path is the opinionated and supported path to build your system." A golden path is not a constraint — it's a curated default. The team can deviate, but the path offers the lowest-friction route to production. Charity Majors frames the goal as: "developers can easily choose good defaults, self-serve their infra, and own their own code in production." Contrast with Vlad Ionescu's critique: full-platform abstraction creates mediocre service and destroys velocity. Guardrails + DX tooling built on public cloud can be the golden path without the overhead of a full internal platform. ## Cross-Domain Applications **Framework design**: Rails/Django are golden paths for web development — opinionated, batteries-included, with escape hatches. The tradeoff is the same: faster for the common case, friction at the edges. **Onboarding and training**: Structured learning paths (e.g., Math Academy's determined sequence) are institutional golden paths — maximally effective for most learners, may miss edge-case needs. **API design**: A "happy path" API that covers 90% of use cases with clean defaults, with power-user extensions available, applies the same principle. **Process design**: Standard operating procedures are golden paths — opinionated defaults that reduce decision fatigue while allowing documented exceptions. ## Related - [[Image Cascading Fallback]] — Rails example of golden path fallbacks in action - [[Constraint Based Agent Governance]] -- Curated defaults as enabling constraints for AI agents - [[Platform Engineering, DevOps, and Cognitive Load]] (InfoQ, Oct 2022) - Spotify — Gary Niemen