A new discipline inside Developer Relations
When a developer asks AI to integrate with your platform, does it work?
Most DevRel programs don't know. Agentic Relations is the discipline that makes the answer knowable — and then systematically improves it.
The problem
The developer community has a new member.
It doesn't attend your conferences. It doesn't read your blog posts. It doesn't care about your ambassador program. But it touches every integration your platform hosts, amplifies every ambiguity in your documentation, and makes a decision about your platform on behalf of every developer who asks it to write some code.
That member is the AI coding agent. And Developer Relations, as a field, has no framework for serving it.
Agentic Relations is that framework.
The Fundamental Triad, extended
01
One platform. Two audiences. A missing framework.
The original Fundamental Triad of Developer Relations — Community, Company, Customer — assumed every vertex was human. That assumption has broken. Each vertex now has an agent-era extension.
02 · Three principles
What Agentic Relations assumes about the world.
01
The agent ecosystem is shaped by deliberate choices or by neglect.
AI tools draw on whatever corpus is available — your docs, your open-source examples, your MCP servers. That corpus is being shaped right now. The only question is whether it is being shaped intentionally.
02
Agent failures are silent and systemic.
A developer whose AI tool generates a broken integration may debug silently or abandon the platform. No support ticket. No forum question. The traditional DevRel dashboard shows green while adoption degrades.
03
Encoded judgment is the moat.
AI models are commodities. What is not commoditized is encoded judgment about what a correct integration looks like. That judgment, maintained by practitioners with deep platform expertise, becomes institutional capital that compounds.
Start here
03
Five pages worth reading first.
What Is Agentic Relations
The canonical definition, three principles, and how it extends the Fundamental Triad.
Read
The Amdahl Tax
Why the environment is the binding constraint, and what DevRel can do about it.
Read
The 37 Patterns Reframed
How every DevRel activity pattern bifurcates for the AI-agent era.
Read
New Roles
The Agent Champion, the Documentation Architect, and the API Experience Designer.
Read
Measurement
FAISR and the four-layer Agent Ecosystem Health Dashboard.
Read
Essays
Read the argument, one essay at a time.
01 Apr 18, 2026
Your Developer Community Now Has Members Who Can't Read
AI coding agents now integrate with developer platforms on behalf of the humans who asked them to. Agentic Relations is the discipline for managing that relationship.
Read essay
02 Apr 12, 2026
The Agent Champion: A Role DevRel Didn't Know It Needed
The Agent Champion is a specific, definable practitioner role, distinct from the Developer Advocate. It exists in pieces in most organizations today.
Read essay
03 Apr 5, 2026
The Amdahl Tax on Developer Relations
The METR and Jellyfish data are not about AI capability. They are about environment. DevRel owns the environment.
Read essay
About the author
Chris Woodruff
Chris Woodruff co-authored Developer Relations Activity Patterns (Apress, 2026) — the field's first systematic catalog of DevRel activity patterns. He is the founder of EcoSynt, an agent ecosystem health and observability platform, and has been working at the intersection of DevRel and AI systems since the earliest multi-agent frameworks reached production. He coined the term Agentic Relations and maintains this site as the canonical resource for the discipline.
The Agentic Relations Brief
New frameworks, delivered twice a month.
One original observation, one annotated link, one action item — for DevRel practitioners working through the agent era.
Subscribe