Skip to content

SYSTEM Cited by 1 source

Soundcheck / golden state

Soundcheck and golden state are Spotify's standardization layer on top of Backstage. Golden state defines the recommended technologies and practices for each type of component; Soundcheck provides a UI where teams self-assess their components against those standards. (Source: sources/2026-06-03-spotify-coding-is-no-longer-the-constraint-scaling-developer-experie-35c3855d)

From documentation to active guardrail

On their own, Soundcheck + golden state are advisory (self-assessment against recommended practice). Combined with static analysis and linting, they become active guardrails: when a change uses a pattern Spotify knows isn't optimal for its infrastructure, the lint system flags it immediately.

Crucially, this same feedback loop works for agents: when Honk/Claude "works in our codebase and uses a pattern we know isn't optimal for our infrastructure, it gets immediate feedback from our lint system and corrects itself." A guardrail built to keep humans on the golden path doubles as a self-correction signal for coding agents — see lint-feedback-loop-corrects-agents. This is a concrete mechanism behind codebase-consistency-improves-agent-performance: the standards that keep the codebase consistent are also what pull agent output back toward that consistency.

Availability

Soundcheck is a Backstage plugin offered by Spotify (part of the Spotify Portal for Backstage plugin family).

Seen in

  • systems/backstage — the IDP Soundcheck / golden state sit on top of.
  • systems/spotify-honk — the agent that gets lint feedback and self-corrects.
  • codebase-consistency-improves-agent-performance — the effect these standards produce for agents.
  • lint-feedback-loop-corrects-agents — the guardrail-as-agent-feedback pattern.
  • companies/spotify
Last updated · 766 distilled / 2,225 read