X · Governance & ObservabilityEmerging★

Agentic Golden Path

also known as Paved Road for Agents, Golden Path agentique, Compliant-by-Construction Agent Platform

Constrain an agent to the platform's curated golden path of living, machine-readable standards and check for drift as it works, so its output is compliant by construction rather than corrected later.

Context

A team runs an internal developer platform that gives engineers paved roads — opinionated, supported workflows for building and deploying software. Now agents generate much of that software, scaffolding services, writing configuration, and opening changes. The platform's architectural standards have historically lived in templates, wikis, and the heads of senior engineers. The team has to decide how those standards reach an agent so its output follows the same paved road a careful human would.

Problem

Templates capture standards at scaffold time and then rot: a service generated last year drifts from this year's observability, secret-management, and security conventions, and nobody notices until an audit. Conventions that live in wikis or senior engineers' heads are invisible to an agent, which will confidently produce plausible work that violates them. And when validation only runs at push time in continuous integration, the agent (like a human) discovers the violation after the work is done, forcing an expensive correction loop. The team needs the standards to be present and enforced while the agent works, not discovered afterward.

Forces

  • Standards captured once in a template rot as conventions evolve, while the scaffolded code does not.
  • Conventions living in wikis or experts' heads are invisible to an agent generating work.
  • Validation only at push time makes the agent discover violations after the work is done.
  • Too tight a paved road blocks legitimate work; too loose a one lets non-compliant output through.
  • Standards must be machine-readable for an agent to consume, yet stay authored and owned by humans.

Example

An engineer asks the platform's agent to spin up a new service. A template-driven platform would scaffold last year's layout and let continuous integration reject it three standards later. The agentic golden path instead assembles the current observability, secret-management, and security standards into the agent's context, checks the generated config against policy-as-code as it is written, and flags a missing trace exporter before anything is pushed. The new service lands on the paved road on the first try, and when the organisation updates a standard, the next agent run picks it up automatically.

Diagram

Solution

Therefore:

Shift the platform from template-driven to context-driven. Keep the organisation's standards as versioned, machine-readable artifacts — agent guidance files, architecture decision records, policy-as-code, reference examples — and assemble the relevant ones into the agent's context before it acts, so the golden path is what the agent sees. Run policy and drift checks continuously as the agent edits, surfacing violations in the loop rather than at a push-time gate. Keep the agent inside scoped sandboxes with short-lived credentials, and route high-impact changes to a human. Because the standards are living artifacts the platform propagates, updating a convention updates every agent's paved road at once, instead of leaving older scaffolds behind.

What this pattern forbids. The agent may only operate within the platform's scoped sandbox and against the standards assembled into its context; high-impact changes must route to a human, and work that fails a drift check cannot be promoted past the golden path.

And the patterns that stand alongside it, or against it —

  • complementsOwn Your Prompts (12-Factor Agents)★— Every prompt in a production agent is versioned, tested, and owned by the team in the application repo — never inherited as a framework default.
  • complementsPolicy-as-Code Gate★— Evaluate every proposed agent action against externally-managed machine-readable policies before dispatch, so compliance authorship lives outside the prompt and outside the agent code.
  • complementsAgent Factory★— Manufacture agent instances from a versioned template that renders model, tools, and prompt atomically, with registry-backed identities, so a fleet stays consistent and one template change propagates instead of drifting per instance.

Neighbourhood

Click any neighbour to follow the language. Scroll to zoom, drag to pan.

References

Provenance