---
id: murphy-trueman
kind: person
title: "Murphy Trueman"
role: "Writer and practitioner"
confidence: "sourced"
atlas_url: https://designsystems.fly.dev/nodes/murphy-trueman.md
---

# Murphy Trueman

The earliest sustained argument that a design system is already an API and the only question is whether it is a good one. Now arguing a system with agents pointed at it should ship a regression suite the way it ships a changelog.

## Links

- blog: https://blog.murphytrueman.com/

## Edges

- authored -> Design systems need evals, Every fork looks like adoption, In the open: What the modal reveals, The parts of your system you never wrote down, Your design system's newest author is an agent, Your next design system user
- focus -> Adoption and mandate, Agentic governance, Compiled, not written, context, Component contracts, Component registries, Context engineering, Documentation schema, Evals for design systems, MCP servers, Multi-agent build pipelines, Validation loops
- holds -> Yes. Instructions tell an agent the rules; only running it says whether it followed them.

## Sources

- https://blog.murphytrueman.com/design-systems-need-evals/
- https://blog.murphytrueman.com/your-next-design-system-user/
- https://blog.murphytrueman.com/in-the-open-what-the-modal-reveals/