Golden Path

The org-scale member of the good-defaults family (Good defaults): the paved, supported, default route for common work — the platform answer to “50 manual steps and an endless wiki.”

Definition

The Golden Path is the supported, paved way to do a common task in an organization: pre-approved, pre-secured, and easiest because the platform did the work once. Straying off it isn’t forbidden — it’s just unsupported and slower, which is the whole mechanism. (Red Hat’s platform-engineering definition; Spotify Backstage is the canonical implementation.)

In practice

A developer wants to launch a new microservice. Instead of setting up cloud permissions, firewalls, and monitoring from scratch, they run dotnet new or pick a template in an internal developer portal. The template automatically injects security protocols, logging defaults, and deployment pipelines — nobody reads the wiki; the template is the documentation.

Captures

• Red Hat — Golden paths (platform engineering) — the org-scale definition
• PragmaticDX — Make the easy path the right path — gravity over grit; guardrails over wikis

Distinction from the Pit of Success

Same philosophy (Good defaults), different altitude: the Pit of Success (Pit of Success) is an API/language-design property (fall into correctness at the call site); the Golden Path is a platform-engineering property (the paved route exists at org scale). Golden Path = pit dug once by the platform team, for everyone.

Vault kin

• Agent-accessible product — the golden path idea one layer over: make the machine-friendly route the default route.
• Hermes skills — a skill is a golden path: proven steps packaged so the natural route (load skill) is the right route.
• Varick’s “single orchestration layer” (AI engineering) — killing agent sprawl is golden-pathing the org’s AI usage.
• Software engineering in AI era — Uncle Bob’s continuity holds only if the model’s environment is paved; otherwise it leaves the path at machine speed.

Practice

• Invest in the template/scaffold, not the wiki (Backstage-style).
• Make the paved path genuinely easiest — if the shortcut is faster, the path is broken, not the developers.
• Off-path must be possible (escape hatches) but visibly more expensive.