← Latest Update

Agent Ops: docs, Git-agents, MCP, TDD, and opaque A/Bs

Optimizing Content for Agents — Sentry reworks docs and endpoints to serve agents Markdown and structured APIs, reducing context bloat and improving agent accuracy. Outcome engineers should treat docs and endpoints as first-class agent inputs: serve compact, structured context to raise signal-to-noise and cut token costs (Principle 06).

GitAgent — An open standard turning any Git repo into an AI agent — GitAgent defines an open standard that makes any Git repository behave as a native AI agent. That changes how teams package agent behavior: versioned, reviewable artifacts live in Git, enabling reproducible deployments and CI-driven agent pipelines (Principle 08).

MCP Is Dead; Long Live MCP — The post argues enterprises still need a Model Control Plane for auth, telemetry, and organizational agent control despite CLI-driven hype. This is a reminder that centralized governance and telemetry are non-negotiable for production agent fleets—build auditability and access controls in from day one (Principles 06 & 10).

My fireside chat about agentic engineering at the Pragmatic Summit — Simon Willison maps developer AI adoption stages, champions test-driven development for coding agents, and warns against blindly trusting generated code. He provides practical TDD and staging patterns for treating agents as testable systems, a direct playbook for outcome engineers building reliable agent pipelines (Principles 03 & 16).

Claude Code conducts A/B tests on core features — Anthropic runs opaque A/B tests inside Claude Code that degrade professional workflows and prompt calls for opt-outs and configurability. Outcome engineers must treat runtime experiments as product-level risks: bake in opt-outs, configuration, and observability to protect workflows and maintain trust (Principles 15 & 10).