ReadingResearchRadarInvestment framework
Sign in / Sign up
← Back to reading
NewsTopic · OracleMaterial3 min readDisconfirmAI Editorial

Oracle Industry Applications Executive: Agentic AI Risk Has Shifted from Design to Runtime, Requiring Team Structure Changes

Simon de Montfort Walker, Executive Vice President of Industry Applications at Oracle, stated at AI World 2026 that models are no longer the center of agentic architecture; enterprise logic within applications is. The true bottleneck is not technical but organizational: as building becomes cheap, who is responsible for architecture, hardening, and security? He outlined specific practices of a 'brigade system' and cited a cautionary lesson from the APEX low-code platform.

2026-10-26 23:27 GMT+8

At Oracle AI World last year, Simon de Montfort Walker was discussing how frontier models could only cover 60% of industry application needs, with the remaining 40% being a technical challenge. This year, sitting at the same event, his focus had shifted. De Montfort Walker, Executive Vice President of Industry Applications at Oracle, argued that the model is no longer the center of gravity in this ecosystem; the application is. Applications contain vast amounts of enterprise-level logic—authority matrices, usage rights, and deterministic input/output processes. Generic models reach 100% effectiveness on use cases precisely because they become users of this application logic, rather than replacements for it.

Consequently, Oracle is placing greater emphasis on its application business. Over the past year, the work has focused less on the models themselves and more on their runtime environment: what is running, where, who is running it, and within what boundaries it operates.

From Design to Runtime: Where the Risk Shifts

De Montfort Walker used a financial regulatory analogy to explain this shift. At a financial services summit in London last week, he described traditional compliance assurance:

"Regulator, here is how our system will work. Here is the input, here is the output, and here is why you should feel comfortable."

Sign in / Sign up
ReadingResearchRadarInvestment framework

However, in living, breathing systems, while design time is important, runtime is the moment when certainty is truly required. If the runtime is not designed appropriately, the system may behave differently each time. Telemetry data, guardrails, and the collaboration of deterministic and probabilistic components are needed to ensure outcomes align with expectations.

The practical implication is that the bottleneck in enterprise AI governance is shifting from what the system looks like to who monitors it once it is running.

The Brigade System: When Building Becomes Cheap

De Montfort Walker noted that many functionalities have suddenly become inexpensive, making production applications easier to create and allowing smaller teams to be highly efficient. However, previous working methods are no longer effective; the process weight has shifted to non-development activities: How do we package this properly? How do we industrialize it?

He cited designers as a prime example. Previously, Oracle had excellent design teams focused on user interaction, but they had to package designs for others to code. Now, designers act as full-stack engineers—pairing with design partners, industry experts, and large token volumes to produce near-working applications. These are then handed off to another team responsible for architecture, hardening, and running through all security toolchains. This is the "brigade system": one team generates, while another handles architecture, hardening, and security.

Lessons from APEX

De Montfort Walker also acknowledged the risks. Oracle witnessed this scenario on its own low-code platform, APEX: when people who had never built applications suddenly could, "all of a sudden you had 30 applications that no one was using." When building is cheap, the business case and a common platform become significantly more important.

His Advice

His advice to customers is direct: If you simply hand these tools over to IT as just another project similar to past initiatives, progress will be limited. What is truly needed is to select a specific initiative, pull a few people out of their organizations, give them permission to break things and fail a few times, and determine what the new brigade system should look like.

Boundaries

It is important to note that this is an executive’s description of Oracle’s internal path. The narrative of moving from 60% to 100% serves Oracle’s product positioning by implying that its application-layer logic bridges the gap. The brigade system is based on Oracle’s internal experience; de Montfort Walker provided no quantitative data on efficiency changes before and after restructuring, nor did he discuss the extent to which this model relies on Oracle’s existing platform ecosystem. However, the mechanism he identified—that as generation costs drop, the bottleneck shifts from creation to post-runtime responsibility—is an organizational logic independent of any specific vendor.

Sources

  • diginomica.comdiginomica↗
Topic

Oracle

【背景】美国软件巨头Oracle正在重新定义企业级AI智能体的落地路径。其核心观点是:随着模型能力的普及,风险与瓶颈已从“设计阶段”转移至“运行时”。

3 steps1 piecesUpdated 2026-10-27 03:03

How it got here

  1. 2026-09-29Oracle宣布推出Fusion Claw,一种受治理的智能体执行运行时,支持25个新的Claw驱动的Fusion Agentic Applications,实现从AI辅助到自主执行的跨越。oracle.com ↗
  2. 2026-10-21Oracle发布AI Agent Studio for Industry Applications,提供无代码/低代码平台,帮助客户和行业伙伴创建、部署和管理针对特定业务流程的AI智能体。oracle.com ↗
  3. 2026-10-27Oracle高管Simon de Montfort Walker在AI World 2026会议上阐述观点,认为智能体AI的风险重心已从设计转移到运行时,呼吁企业调整组织结构以适应这一变化。diginomica.com ↗

What is still unsettled

  • 其他主要ERP或云厂商是否也在推动类似的‘运行时治理’标准,还是仍聚焦于模型能力的提升?
  • 企业在采用Fusion Claw等工具时,实际遇到的组织阻力有多大?是否有公开的案例研究显示‘旅队系统’的具体成效?
  • 监管机构对于由AI智能体在运行时做出的自动化决策(如金融交易、医疗建议)持何种态度?现有的合规框架是否足以覆盖‘运行时’的不确定性?
Read the full topic →
Continue researching →