LeituraPesquisaRadarFramework de investimento
Entrar / Cadastrar
← Voltar para a leitura
NotíciasTópico · OracleMaterial3 min de leituraEditorial DisconfirmAI

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."

Entrar / Cadastrar
LeituraPesquisaRadarFramework de investimento

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.

Fontes

  • diginomica.comdiginomica↗
Tópico

Oracle

【背景】Oracle行业应用执行副总裁Simon de Montfort Walker指出,智能体AI的风险重心已从系统设计转移至运行时,强调组织结构和团队模式需随之调整。2026年10月,Oracle发布了面向行业应用的AI Agent …

3 etapas2 peçasAtualizado 2026-11-08 00:18

Como chegamos aqui

  1. 2026-10-21Oracle宣布推出AI Agent Studio for Industry Applications,这是一个无代码和低代码平台,允许客户和合作伙伴创建、测试、部署和管理针对特定业务流程的AI代理。oracle.com ↗
  2. 2026-10-27在AI World 2026上,Oracle高管Simon de Montfort Walker表示,模型不再是智能体架构的核心,企业逻辑和运行时治理成为关键瓶颈,建议采用“旅队系统”重构团队结构。diginomica.com ↗
  3. 2026-10-28Oracle在投资者日公布了长期财务指引,目标是在FY30实现超过2250亿美元的总营收,并承诺将FY27-FY30期间的额外资本市场融资控制在200亿美元以内。prnewswire.com ↗

O que ainda está indefinido

  • Oracle提出的“旅队系统”具体如何改变传统IT团队的协作方式?
  • 限制额外融资至200亿美元是否足以支撑Oracle在AI基础设施上的持续投入?

Também nesta thread

  • Oracle Sets FY30 Revenue Target Above $225 Billion, Caps Additional Capital Raises at $20 Billion2026-10-29
Ler o tópico completo →
Continuar pesquisando →