--- title: AI governance is now an engineering problem | daily.dev description: Most organizations using AI are experiencing negative consequences not from lack of capability but from lack of control. Three recurring failure patterns... canonical: https://daily.dev/posts/ai-governance-is-now-an-engineering-problem-p4jterxae twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: AI governance is now an engineering problem | daily.dev og:description: Most organizations using AI are experiencing negative consequences not from lack of capability but from lack of control. Three recurring failure patterns... og:url: https://daily.dev/posts/ai-governance-is-now-an-engineering-problem-p4jterxae og:image: https://api.daily.dev/og/posts/P4JTerXae.png og:image:alt: AI governance is now an engineering problem og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # AI governance is now an engineering problem **[LeadDev](https://daily.dev/sources/leaddev)** · 9 min read · 1 upvotes · 0 comments ## Summary Most organizations using AI are experiencing negative consequences not from lack of capability but from lack of control. Three recurring failure patterns emerge: unclear ownership over AI-generated code changes, missing audit trails in AI-assisted incident response, and rollback paths that cause secondary incidents when multi-step agent workflows are partially reversed. Uber burning its entire 2026 AI budget in four months illustrates the financial cost of ungoverned AI adoption. The core argument is that governance must be embedded directly into engineering workflows — version control, CI/CD pipelines, deployment gates — rather than delegated to policy documents. Practically, this means explicitly defining where AI can act autonomously, implementing automatic decision logging, and designing rollback boundaries for agentic workflows before deployment, not during incidents. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why did Uber run out of its annual AI budget so quickly after adopting agentic coding tools? Uber burned through its entire annual AI budget in four months after encouraging engineers to adopt agentic coding tools like Claude Code at scale. When asked whether that spend had produced more value for customers, the company's leadership said the connection was not yet visible, illustrating how agentic tools consume compute faster than teams can measure the resulting output. _Teams weighing agentic coding rollouts can track real-world cost and governance lessons like this on daily.dev._ ### What questions should a team ask to find gaps in AI governance before an incident happens? Three questions expose governance gaps: who is accountable if an AI-driven change produces a wrong outcome, can the decision be reconstructed after the fact, and can the action be reversed without breaking something else. A 'no' answer to any of these signals an accountability, traceability, or rollback gap that should be closed before deployment, not during an incident. _Engineers designing safeguards around AI agents can follow governance frameworks like this via daily.dev._ ### Why did rolling back a multi-step AI agent's CI/CD actions cause a second incident? An AI agent had completed three sequential CI/CD steps before a deployment failed on the third step, but steps one and two had already produced downstream effects, including another service reading an updated configuration. Rolling back the failed step was simple, but reversing the earlier steps took four hours and knocked out an unrelated service that had started depending on the changed configuration. _Anyone designing rollback paths for multi-step agents can weigh cases like this via daily.dev._ ## Similar posts on daily.dev - [AI Governance Is a Developer Experience Problem](https://daily.dev/posts/ai-governance-is-a-developer-experience-problem-t8aan7wce) · Docker · 0 upvotes · 0 comments - [Why Your AI Governance Is Holding You Back, and You Don’t Even Know It](https://daily.dev/posts/why-your-ai-governance-is-holding-you-back-and-you-don-t-even-know-it-1vakt5mse) · JetBrains · 1 upvotes · 0 comments - [How to govern agentic AI so as not to lose control](https://daily.dev/posts/how-to-govern-agentic-ai-so-as-not-to-lose-control-jykcxtuoh) · CSO Online · 0 upvotes · 0 comments - [Why AI Governance Needs to Catch Up with AI Adoption](https://daily.dev/posts/why-ai-governance-needs-to-catch-up-with-ai-adoption-zjekqtbo0) · SD Times · 0 upvotes · 0 comments - [AI Governance Is the Strategy: Why Successful AI Initiatives Begins with Control, Not Code](https://daily.dev/posts/ai-governance-is-the-strategy-why-successful-ai-initiatives-begins-with-control-not-code-6f3iyalxs) · databricks · 1 upvotes · 0 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#cicd](https://daily.dev/tags/cicd), [#ai-governance](https://daily.dev/tags/ai-governance) [View this post on daily.dev](https://daily.dev/posts/ai-governance-is-now-an-engineering-problem-p4jterxae) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"AI governance is now an engineering problem","url":"https://daily.dev/posts/ai-governance-is-now-an-engineering-problem-p4jterxae","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/ai-governance-is-now-an-engineering-problem-p4jterxae"},"datePublished":"2026-08-03T12:23:34.377Z","dateModified":"2026-09-13T19:30:35.853Z","description":"Most organizations using AI are experiencing negative consequences not from lack of capability but from lack of control. Three recurring failure patterns...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b74d596785c718d213210d97d2facc62?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b74d596785c718d213210d97d2facc62?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"LeadDev","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"LeadDev","logo":"https://media.daily.dev/image/upload/s--u_Q34nzh--/f_auto,q_auto/v1774514111/logos/leaddev?_a=BAMAMiWQ0","url":"https://daily.dev/sources/leaddev"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/ai-governance-is-now-an-engineering-problem-p4jterxae","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,cicd,ai-governance","timeRequired":"PT9M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"LeadDev","item":"https://daily.dev/sources/leaddev"},{"@type":"ListItem","position":3,"name":"AI governance is now an engineering problem"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/ai-governance-is-now-an-engineering-problem-p4jterxae#faq","mainEntity":[{"@type":"Question","name":"Why did Uber run out of its annual AI budget so quickly after adopting agentic coding tools?","acceptedAnswer":{"@type":"Answer","text":"Uber burned through its entire annual AI budget in four months after encouraging engineers to adopt agentic coding tools like Claude Code at scale. When asked whether that spend had produced more value for customers, the company's leadership said the connection was not yet visible, illustrating how agentic tools consume compute faster than teams can measure the resulting output. Teams weighing agentic coding rollouts can track real-world cost and governance lessons like this on daily.dev."}},{"@type":"Question","name":"What questions should a team ask to find gaps in AI governance before an incident happens?","acceptedAnswer":{"@type":"Answer","text":"Three questions expose governance gaps: who is accountable if an AI-driven change produces a wrong outcome, can the decision be reconstructed after the fact, and can the action be reversed without breaking something else. A 'no' answer to any of these signals an accountability, traceability, or rollback gap that should be closed before deployment, not during an incident. Engineers designing safeguards around AI agents can follow governance frameworks like this via daily.dev."}},{"@type":"Question","name":"Why did rolling back a multi-step AI agent's CI/CD actions cause a second incident?","acceptedAnswer":{"@type":"Answer","text":"An AI agent had completed three sequential CI/CD steps before a deployment failed on the third step, but steps one and two had already produced downstream effects, including another service reading an updated configuration. Rolling back the failed step was simple, but reversing the earlier steps took four hours and knocked out an unrelated service that had started depending on the changed configuration. Anyone designing rollback paths for multi-step agents can weigh cases like this via daily.dev."}}]} ```