The author warns that “agentic design systems” often blur the line between using AI for tasks and handing off core judgment to autonomous loops with no human oversight. He argues design systems are governance tools requiring human-owned gates and accountability, and that removing those humans risks unchecked drift.

• "Agentic design systems" conflates using agents to do work with letting them make final judgment calls—two very different things.
• Agentic loops differ from vibe coding because they add hard gates (token checks, linting, accessibility tests, design-parity reviews) after generation, each owned by a named human.
• Without human-owned gates, systems produce drift that just gets mistaken for official, validated output.
• The right split is agents handling the mechanical 80 percent while humans own the final 20 percent of judgment.

The article argues that design systems remain essential but their scope is too narrow in an AI-driven world. Instead of just components and tokens, teams must capture and operationalize product context—decision rules, voice, governance and historical exceptions—to keep AI outputs coherent at scale.

• Design systems fail AI at scale because the actual decision logic lives in Slack threads and tribal knowledge, not component libraries.
• When engineers translated designs into code, they implicitly filled context gaps; AI removes that translation layer, exposing the missing rules.
• Small AI outputs that ignore invisible constraints compound into structural product drift rather than staying as isolated errors.
• The fix isn't bigger component libraries but formalizing "product context" as machine-readable rules covering governance, voice, and risk tolerance alongside human docs.