Agent Infrastructure: orchestration, speedups, and multi‑model control
Intercom, now Fin, launches an AI agent whose only job is managing another AI agent. Fin launches Operator, an AI whose sole purpose is managing its customer-facing Fin agent—automating tuning, debugging, and knowledge handoffs. Outcome engineers should treat manager-agents as a first-class orchestration layer for operationalizing reliability and continuous improvement (Principle 09, Principle 04).
How RecursiveMAS speeds up multi-agent inference by 2.4x and reduces token usage by 75%. RecursiveMAS replaces text-based agent handoffs with embedding recursions, cutting latency 2.4× and token usage 75%. That technique directly lowers cost and scale limits for multi-agent pipelines, enabling higher-frequency coordination and denser agent graphs (Principle 09, Principle 11).
Databricks brings GPT-5.5 to enterprise agent workflows. Databricks integrates GPT-5.5 into AgentBricks workflows and reports large error reductions in OfficeQA Pro. Outcome engineers can now rely on higher-capability models inside enterprise context platforms, but must redesign context engineering and validation around model upgrades (Principle 09, Principle 06).
GitHub adds Claude and Codex to Copilot. GitHub centralizes multi-model coding agents, billing, and governance under an Agent Control Plane inside Copilot. That pattern shows how developer-facing platforms can expose multi-model orchestration, observability, and policy controls—critical building blocks for production agentops (Principle 09, Principle 11, Principle 15).
Karpathy Explains Vibe Coding to Agentic Engineering. Karpathy frames vibe coding as democratized development while warning that agentic systems demand new verification, orchestration, and observability to manage uneven model competence. Outcome engineers should adopt rigorous verification primitives and guardrails as part of the culture shift toward agent-first delivery (Principle 09, Principle 14, Principle 16).