TL;DR: AI systems can collapse request, approval, execution and review into one continuous path, leaving static governance unable to contain a toxic super-user, according to Singul AI. Runtime oversight has to track behaviour, authority and lifecycle drift, not just a single sign-off.
Editorial analysis by NHI Mgmt Group, based on content published by Singul AI: “New Tools, Old Rules: Closing the AI Governance And Control Gap - Part 2”.
Key questions
Q: Why do agentic AI systems break segregation of duties models?
A: They break SoD models because the conflict can be created and consumed inside one runtime sequence.
Q: How should organisations govern AI system instructions across deployments?
A: Treat system instructions as controlled policy artefacts, not ad hoc configuration.
Q: What fails when approval is treated as governance for AI systems?
A: Approval fails because it freezes risk at a single moment while the AI system keeps changing through new data, tools and use cases.
Practitioner guidance
- Define oversight separation for AI systems Split objective-setting, independent monitoring and intervention authority across different teams so no single group owns the full control loop.
- Reclassify approval as a starting control Treat sign-off as the point where operational governance begins, then reassess behaviour whenever data, tools or use cases change.
- Map AI runtime authority to identity controls Inventory which AI systems can request actions, perform actions and report outcomes, then bound each authority with task-scoped access.
Bottom line: AI systems can collapse request, approval, execution and review into one runtime path, which makes traditional segregation of duties a poor fit.
Glossary terms: Toxic Super-User, Segregation of Duties, Segregation of Oversight, Governance Theatre
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Approval-centric governance is no longer a sufficient control model for AI. The article correctly identifies a structural mismatch between static approval and dynamic runtime behaviour. Once AI systems learn, adapt and act across workflows, a signed-off use case can drift far from the risk context that was originally reviewed. Practitioners should treat approval as a governance input, not as a control outcome.
A few things that frame the scale:
- 54% of organisations are actively deploying AI agents across workflows, yet only 21% report a mature governance model for agentic AI.
A question worth separating out:
Q: What is the difference between an approval gate and real governance for AI agents?
A: An approval gate asks a person to click yes or no, while real governance shapes which actions reach a person, how they are framed, and how often they appear. Governance should include policy tiers, exception routing, logging, and review of approval behavior over time. Without those elements, the gate may exist on paper but fail under operational pressure.
👉 Read our full editorial: Approval-centric governance fails when AI becomes a toxic super-user