glossary · term
golden path
Also called paved road
The supported way to build and ship on an internal platform. Its templates, defaults, and guardrails settle hundreds of decisions every team would otherwise make differently. A good golden path makes the right way the easy way. With agents in the loop, it becomes the target that stated intent gets compiled into.
in practice
How I use the term
The paved road works. What it never fixed is the interface, which still speaks implementation. To use a platform well, a developer has to hold its taxonomy, module names, pipeline stages, and exception processes in their head.
That knowledge doesn't transfer. A developer who masters one company's golden path starts over at the next, because what they learned was the company.
Agents raise the value of the path. Generating infrastructure gets easier, while generating correct infrastructure for your organization stays hard. The paved road becomes the boundary between what an agent can create and what the organization is prepared to operate.
in the essays · 4
Where it shows up
- The Golden Path Needs an Intent Interface
Developers state intent, and the golden path becomes the compiler target.
- Complexity Is Inevitable. Drag Is Optional.
Good platforms convert unavoidable complexity into defaults and automation.
- Building Cloud From Zero: Five Decisions That Compounded and Three I’d Redo
Two greenfield cloud builds, and why defaults have to be inherited.
- Your Platform Has a New User: The Agent
Why the paved road matters more once agents arrive.
see: agent-readiness test · agent · Context Spine