Notifications
Clear all
Topic starter
19/08/2026 3:25 pm
TL;DR: Andrew Ng's three-loop model still fits enterprise AI, but TruFoundry argues the outer feedback loop expands to include policy, identity, budgets, audit, and request-level evidence, while the inner coding loop and middle evaluation loop keep their original shape. For IAM and NHI teams, the key shift is that production AI needs governed identity and traceability around model and tool traffic, not just faster iteration.
NHIMG editorial — based on content published by TruFoundry: From Prototype to Enterprise Production: Extending Andrew Ng's Three Loops
By the numbers:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems, inappropriately sharing sensitive data, and revealing access credentials.
Questions worth separating out
Q: How should teams govern AI gateways that route model and tool traffic?
A: Teams should treat the gateway as the control boundary for identity, spend, logging, and policy enforcement.
Q: Why do AI systems need request-level logs instead of only dashboards?
A: Dashboards show volume and latency, but request-level logs show accountability.
Q: When should organisations use approval gates in AI workflows?
A: Use approval gates when the action is consequential, such as external side effects, sensitive data access, or budget-bearing operations.
Practitioner guidance
- Define the AI gateway as a governance boundary Map identity, policy, spend, and logging responsibilities to the gateway layer before the first production rollout.
- Attach request-level evidence to production AI Retain traces and logs that show who invoked the model, which tools were called, and what response or side effect followed.
- Separate approval checkpoints from routine routing Use human approval only for sensitive tool calls and consequential actions, and keep routine inference traffic policy-driven.
What's in the full article
TruFoundry's full article covers the operational detail this post intentionally leaves for the source:
- The documented AI Gateway architecture that shows where model traffic, MCP traffic, and policy enforcement intersect.
- The specific gateway capabilities for Agent Identity, budgets, traces, and request logs that support enterprise accountability.
- The staged rollout mechanics for evaluation, routing, and approval checkpoints in production AI workflows.
- The product-level limits and configuration notes that matter when you are implementing controls rather than analysing them.
👉 Read TruFoundry's full analysis of enterprise AI gateway governance →
AI gateway governance: what changes when the outer loop enters production?
Explore further
19/08/2026 4:10 pm
The outer loop is now an identity and accountability problem, not just a product feedback problem. Ng's three-loop model still explains the build process, but enterprise deployment adds policy, budget ownership, audit, and access control to the outer loop. That changes the governance burden around AI gateways because the system must now answer who acted, what they touched, and whether the action was authorised. For practitioners, the implication is that AI product graduation is an IAM and NHI design problem as much as an engineering milestone.
A few things that frame the scale:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems, inappropriately sharing sensitive data, and revealing access credentials, according to AI Agents: The New Attack Surface report.
- Only 52% of companies can track and audit the data their AI agents access, leaving 48% with a complete blind spot for compliance and breach investigation.
A question worth separating out:
Q: What is the difference between AI policy and AI governance?
A: AI policy states what the organization wants to allow, while AI governance enforces how those rules work in practice through ownership, access control, logging, and review. Without technical enforcement, policy becomes advisory text that cannot control machine identities or agent behaviour at scale.
👉 Read our full editorial: Enterprise AI gateway governance extends Ng's three loops
