Fusion Claw Meets SCM: When Agentic AI Starts Doing the Work

A lot has been said about AI agents in enterprise applications. They can answer questions, summarise information, recommend an action and increasingly help us navigate complicated business processes.

But I think the much more interesting question is: what happens when we want AI to go beyond helping someone do the work and actually coordinate the work itself? That is where Oracle’s new Fusion Claw starts to get interesting, particularly when you look at what Oracle is planning for Supply Chain Management.

I recently attended an Oracle session on Fusion Claw for Product Readiness and Risk Management, and for me it helped put some practical substance behind the announcements from AI World. This isn’t simply another AI agent. It is an attempt to tackle something much harder: how do you allow agentic AI to execute complex enterprise processes without losing the controls, policies, permissions and accountability that organisations already rely upon?

Oracle describes the change as moving from systems that predominantly record information and automate tasks towards systems that can monitor, plan, analyse, coordinate, decide and act. I actually think a better way of looking at it is this: Fusion Applications remain the system of record. Agentic Applications increasingly become the system of outcomes.

Fusion still contains the authoritative enterprise data, business objects, policies, approvals, permissions, processes, context and history. Agentic Applications sit above that foundation and coordinate work towards an outcome. That distinction matters.

One of my concerns whenever we talk about autonomous AI in enterprise applications is that we can make it sound as though we are simply handing an LLM access to ERP or SCM and telling it to get on with things. That clearly isn’t going to work.

Enterprise processes have approvals, segregation of duties, business rules, tolerances and exceptions for a reason. An AI model being confident about an answer doesn’t give it the authority to perform a transaction. And that is really the problem Fusion Claw appears designed to solve.

Fusion Claw is a governed agentic execution runtime and an execution engine for complex, high-value work. The principle is that AI handles the parts of a problem where reasoning is valuable, while the execution layer handles the things that need to be precise and governed.

In practice, there are three important elements working together. Planning uses AI reasoning to understand an objective, analyse the situation, evaluate alternatives and create a plan. Computation handles things such as reconciliation, simulation, optimisation, calculations and business rules deterministically and at scale. Execution then performs authorised actions and transactions within the controls of the enterprise application.

And there is one line in Oracle’s material that I think is probably more important than anything else: “The model can plan and recommend but never grants itself authority to act.” That, for me, is the difference between an interesting AI demonstration and something organisations could realistically contemplate putting into production.

Supply Chain is almost the perfect environment in which to demonstrate this. Think about a relatively straightforward question such as: Is this product actually ready to go into production?

The answer might depend upon information spread across Product Lifecycle Management and the BOM, suppliers and sourcing, regulatory declarations, quality records and financial information including pricing, tariffs and currency exposure.

Traditionally, people have to assemble that evidence, reconcile what it means and then coordinate whatever happens next. This isn’t necessarily because the underlying systems cannot store the information. The challenge is bringing the information together in context, understanding its significance and deciding what should happen next. That is where the Product Readiness use case starts to show the potential of an Agentic Application.

To resolve this, Oracle have introduced the BOM Design Risk and Grading Analyser, part of the Product Readiness Workspace. Its objective is to identify BOM risk earlier and establish a mitigation path before design freeze. The Analyzer can grade design risk, explain blockers, compare mitigation scenarios and prepare a governed readiness decision, with the intended outcome of getting to launch decisions faster while reducing late blockers. What I like about this example is that it isn’t really an AI chatbot use case.

What I like about this example is that it isn’t really an AI chatbot use case. The process connects the business and product records sitting within Fusion Applications with agent capabilities and tools from AI Agent Studio, the Product Readiness Agentic Application and, importantly, the people, policies, objectives and approval authorities that govern the business. Fusion Claw then provides the governed execution layer that brings those elements together.

That combination matters because an agent isn’t simply being asked“what do you think?” It is being asked to investigate a business outcome against actual enterprise evidence and policy.

Oracle breaks this down into three broad stages, but I think they are better understood as a continuous process rather than three separate capabilities. It starts by investigating. AI can understand the required BOM outcome, trace the available evidence, compare the available options and help plan recovery activity. The process then moves into assessment, where defined policy becomes critical. Evidence scope can be validated, scores and grades calculated and mandatory gates applied. Finally, it can follow through, comparing possible recovery options, preparing permitted work and tracking the evidence and resolution. Throughout that process, authority still governs what the system is actually allowed to do.

I think that’s an important pattern for enterprise AI because it acknowledges something we occasionally lose sight of when talking about generative AI: not everything should be probabilistic.

We might be perfectly comfortable asking an AI model to reason about possible ways of solving a problem. We are probably much less comfortable asking that same model to arbitrarily decide whether a mandatory compliance condition has been met. Fusion Claw appears to separate those responsibilities.

The Product Readiness component assesses risk across five dimensions, but what makes this interesting is how those dimensions come together rather than the fact that there are five of them. Lifecycle considers whether an item remains viable for the required horizon, taking into account things such as market status, end-of-life information, support and successor qualification. Sourcing looks at whether supply can actually meet the product’s requirements through areas such as qualified sources, supplier concentration, coverage and lead time. Compliance examines whether regulatory evidence genuinely covers the relevant part and revision, while Quality looks at unresolved conditions, qualification tests and gates. Cost then adds another perspective by considering exposure from price variation, tariffs and currency movement.

None of those questions is particularly unusual in its own right. Organisations already answer them today. What’s different is the possibility of evaluating them together as part of one continuously orchestrated business outcome, rather than somebody manually moving between different records, spreadsheets, reports, emails and application screens.

And this is where the value starts to become much clearer to me. The really clever bit: policy still belongs to you. Another element I particularly like is that Oracle isn’t suggesting that AI should decide what constitutes an acceptable risk. The customer defines that.

An organisation can configure its SOPs, evidence requirements, qualification rules, business rules, risk priorities and tolerances. Policy assessment can then combine evidence and scope with thresholds, weights, profiles, grade bands and mandatory gates to apply those criteria consistently. Crucially, Oracle also shows the policy version being retained so that the result remains traceable. That’s a subtle but really important distinction.

AI can help investigate the situation and develop a plan. The enterprise remains responsible for determining the rules of the game. And for organisations considering how they govern agentic AI, I think that model is more compelling than the idea of simply giving increasingly capable models more access.

That’s a completely different level of AI. And this is where it becomes agentic. Identifying the problem is useful. Resolving it is where the business value lives. We’re talking about a system that can help coordinate an outcome.

And importantly, that does not mean uncontrolled autonomy Depending on the authority provided, Fusion Claw can execute within that authority, recognise when approval is required or escalate when necessary, while maintaining audit and monitoring around the process.

The SCM roadmap shown during the webinar covered Agentic Apps and workspaces across a significant proportion of supply chain. Alongside Product Readiness and Design-to-Source there are planned use cases around Maintenance Operations, Batch Process Manufacturing, Logistics Execution, Sourcing, Shipment Load Planning, Supply Planning Allocation, Procurement Spend, Warehouse Operations, Sales Orders, Cost Accounting Close, Inventory Planning, Supplier Qualification, Production Readiness, Kanban Administration, Business Growth Planning, Product Genealogy, Quality Assurance, Cost Management, Warehouse Execution and Pricing.

That’s quite a list. And it starts to reveal the bigger strategy. Fusion Claw isn’t the Agentic Application. It is the common governed execution runtime underneath them. That distinction is going to be important as we start to see these capabilities appearing across Fusion.

For the last couple of years, enterprise AI has largely been about making existing work easier: summarise this, generate that, answer my question or recommend what I should do next.

Useful? Absolutely. Transformational? Sometimes. But the Fusion Claw and Agentic Applications story points towards something different. The shift is from AI helping a user perform a process towards AI helping orchestrate the process around an outcome, while humans retain control of the objectives, policies and authority. For SCM in particular, that’s potentially significant.

Supply chains involve huge datasets, constantly changing conditions and numerous interconnected policies and controls. A decision in one area can quickly create consequences somewhere else. Product readiness is a great example because lifecycle, sourcing, compliance, quality and cost risk don’t exist independently.

If Agentic Applications can genuinely reason across those dimensions, apply deterministic policies where required, coordinate the resulting work and maintain the underlying governance and audit trail, we’re getting much closer to what enterprise agentic AI needs to look like.

Not autonomous AI doing whatever it thinks is best. Governed autonomy working towards an outcome the business has defined. For me, that distinction is what makes Fusion Claw one of the more interesting announcements to come out of Oracle AI World this year. And if Product Readiness is an indication of what Oracle intends to do across the rest of SCM, I’ll definitely be watching what comes next.

Please note all screenshots are the property of Oracle and are used according to their Copyright Guidelines.

Fusion Claw: Stop Looking for AI Use Cases. Start Looking for Work.

One of the questions I hear most when talking about AI in Oracle Fusion is: “What are the use cases?” It’s a perfectly reasonable question. But I’m increasingly convinced it’s also slightly the wrong one. We have spent the last couple of years looking for places where we can add AI to a business process. Where can we summarise something? Where can we generate something? Where can we make an interaction more conversational?

With Fusion Claw, I think we need to turn that thinking around. Don’t start by looking for an AI use case. Start by looking for work. Specifically, look for the work that people are still stitching together manually across Oracle Fusion. The things that involve checking multiple sources, applying judgement, producing an output, chasing exceptions and deciding what needs to happen next. That distinction matters because Fusion Claw isn’t designed simply to answer another question or perform another transaction.

Oracle describes a Fusion Claw use case as“a business result that someone owns and wants handed over.”  I think that is probably one of the most useful ways of thinking about agentic AI that I’ve seen.

Imagine someone in Finance asks: “What is the balance for account 3210?” That isn’t really a Fusion Claw use case. There is a question. Oracle already knows the answer. We just need the quickest and most appropriate way of retrieving it. Now compare that with: “Get us ready for month-end close and show me anything that could prevent us closing.” That is very different.

To achieve that outcome, somebody might need to check the ledger and subledgers, compare information against close policy, identify variances, investigate exceptions, work out which ones actually matter, escalate anything unresolved and produce evidence explaining what they found. There isn’t one answer. There is work to be done. And that, to me, is where Fusion Claw starts to get interesting.

Oracle’s guidance suggests a useful rule of thumb: if a knowledgeable person would normally spend 30 minutes to several hours researching, comparing information, producing something or chasing follow-ups across systems, it may be worth considering Fusion Claw. That immediately gives us a much more practical way of finding opportunities.

Forget brainstorming futuristic AI scenarios for a moment. Go and talk to the people actually using Fusion and listen for sentences like: “Every Friday I pull together…”; “I download this into Excel and then…”; “It takes me half a day to…” etc. Oracle highlights very similar phrases in its guidance because they often reveal processes involving research, judgement, multiple steps and exceptions. Those are potential Claw conversations. And they are much more interesting than asking a room full of people,“What could we do with AI?”

So what might those use cases actually look like? Once you start looking at Fusion through that lens, there are opportunities everywhere.

Finance: “Tell me if we’re actually ready to close.” Don’t just show the close tasks. Review the position across the ledger and relevant subledgers, check it against policy, identify unusual balances or incomplete activity, investigate exceptions and give the Finance team an evidence-backed view of what’s stopping them being close-ready. The outcome isn’t another dashboard. It is confidence about whether you can close.

Procurement: “Find the things we should be worried about.” Imagine regularly reviewing purchase orders, suppliers, invoices and relevant policies to identify unusual activity. Which transactions deserve attention? Which exceptions can be explained by the available information? Which need a human to investigate? And importantly, can you provide the evidence alongside the recommendation? That is considerably more useful than simply producing a list of transactions which meet a predefined query.

HR: “What needs my attention today?” A manager doesn’t necessarily want to navigate five different parts of HCM to understand what is happening across their team. They want to know: What do I actually need to deal with? That could mean looking across outstanding approvals, absence, recruitment activity, upcoming talent actions and other relevant signals, then identifying what matters and why. The deliverable isn’t the individual pieces of data. It’s the prioritised brief.

Projects: “Tell me where this project is going off track.” Imagine analysing project costs, commitments, milestones and relevant operational information, then investigating significant exceptions rather than simply flagging every variance. The value isn’t telling a project manager something is red. It’s doing some of the work required to understand why it is red.

Oracle identifies seven characteristics that indicate a job may suit Fusion Claw:

  1. Multi-step: the work needs to be planned and carried out in stages.
  2. Long-running: it can take minutes or hours rather than requiring an instant response.
  3. Research-heavy: somebody needs to examine multiple records, documents or policies.
  4. Cross-functional: the outcome spans several objects, agents or business areas.
  5. Exception-heavy: investigating what went wrong is part of the job.
  6. Produces something: the outcome might be a report, spreadsheet, plan or evidence pack.
  7. Governed action: the process may ultimately make changes, but only through controlled and approved capabilities.

Not every use case needs all seven. But if you’re ticking several of them, it’s probably worth investigating. I would add an eighth question of my own: Would somebody be genuinely pleased not to have to do this anymore? Because that’s often where the real value is hiding.

Not everything needs Claw. This may actually be the most important part. One of the risks whenever a new technology arrives is that we immediately try to apply it to everything. That would be a mistake.

If somebody simply needs to ask “How many open requisitions do I have?”, a conversational experience such as Ask Oracle may be more appropriate. If the requirement is “Route every new requisition through the same approval steps”, that’s a workflow. If someone has already made a decision and simply needs to execute a transaction, the existing Fusion action may already be the right answer.

Oracle explicitly makes this distinction: lookups, quick status questions, fixed workflows and straightforward transactions don’t suddenly become better because we put a more autonomous agent in front of them. Use the simplest technology that solves the problem. Agentic doesn’t automatically mean better.

There’s another idea in Oracle’s guidance that I particularly like. Good Fusion Claw opportunities may actually be two use cases rather than one. The first researches. The second acts. For example: Research: Review the available information, investigate the exceptions, apply the appropriate policy and recommend what should happen. Then Action: Once that recommendation has been reviewed, carry out the approved next step.

Oracle describes this as starting in Research mode, reviewing the evidence and recommendations, and gradually handing over actions as confidence develops. For enterprise AI, that feels like a much more sensible adoption model than jumping straight to full autonomy.

Trust is earned. Let the agent demonstrate that it can research the problem properly. Let people inspect the evidence. Let them challenge the recommendation. Then decide what you’re comfortable allowing it to do.

My advice: don’t start with your biggest process. I’d be tempted to start somewhere much more boring. Find something that happens every week. Something with a clear owner. Something that currently takes an experienced person an hour or two. Something involving enough research and judgement to be annoying, but not something so business-critical that everyone becomes terrified of changing it.

Run it in Research. Compare what Fusion Claw produces with what the person would have produced. Understand where it gets stuck. Understand where your data, policies or processes aren’t quite as clear as you thought they were. Then improve it.

A weekly process may teach you far more about agentic working than attempting to automate an enormous quarterly process on day one. Oracle makes a similar recommendation: start with a recurring use case that can be proven in Research mode.

For a long time, enterprise AI conversations have started with: “Where can we use AI?” With Fusion Claw, I’d change the question. Ask your Finance team: “What takes you half a day every week?” Ask HR: “What information do you have to pull together before you can make a decision?” Ask Procurement: “What exceptions do your experienced people spend their time investigating?” Ask managers: “What do you repeatedly have to check before you’re comfortable taking an action?” And perhaps most importantly: “What work are our people doing today where the value is in the outcome, not in them personally clicking through every step required to get there?”

That’s where I’d start looking for Fusion Claw. Because the interesting thing about agentic AI isn’t another clever way of interacting with Oracle Fusion. It’s the possibility that, increasingly, we can give Fusion an objective and let it help get the work done. And that feels like a much bigger change.

Please note all screenshots are the property of Oracle and are used according to their Copyright Guidelines.

Oracle AI World Day 1: From Helping People Work to Getting Work Done

I wasn’t in Las Vegas for Oracle AI World this year. Like many Oracle customers and partners around the world, I followed the event remotely using Oracle’s free On Air pass, catching up with the keynotes from the UK rather than from the conference floor. While watching remotely means missing some of the atmosphere and conversations that happen between sessions, it does give you the opportunity to focus entirely on the messages being delivered.

Having watched both Mike Sicilia’s opening keynote and Chris Leone’s product keynote, one theme stood out above everything else. Oracle is no longer talking about helping people work faster. Oracle is talking about getting the work done. At first glance, that might sound like a subtle distinction. I don’t think it is. In fact, I think it represents one of the biggest shifts we’ve seen in enterprise applications for years.

For the last couple of years, most AI conversations have been centred around productivity. How can AI draft content faster? How can AI summarise meetings? How can AI help employees find information more quickly? All of those things matter. They deliver value. But fundamentally, the human remains responsible for completing the task.

What struck me during the Day 1 session was how little time Oracle spent talking about AI as an assistant and how much time it spent talking about AI as an executor. Across both keynotes, the discussion repeatedly returned to outcomes. Not generating insights. Not producing recommendations. Delivering results. That feels like an important evolution in enterprise AI.

One of the things I liked most about Mike Sicilia’s keynote was that the focus wasn’t really technology. It was people. The message wasn’t that AI should replace people. It was that organisations should be able to remove the repetitive, burdensome activities that consume time and energy, allowing people to focus on higher-value work.

For years we’ve accepted certain activities as simply being part of work. Reconciling data. Chasing approvals. Managing exceptions. Navigating complex processes. Collecting information from multiple systems. What if those activities become the responsibility of software instead? That was the question I kept coming back to throughout the keynote. The vision wasn’t more intelligent software. It was more capable organisations. That’s a subtle but important difference.

If Mike Sicilia explained the vision, Chris Leone demonstrated how Oracle intends to deliver it. The progression shown during the keynote was fascinating. We have already seen Oracle introduce embedded AI capabilities across Fusion. We have seen AI agents emerge. Now Oracle is talking about agent teams, workflow agents, agentic applications and autonomous execution.

The key message was that AI is evolving from supporting processes to actively participating in them. That shift matters. Historically, enterprise software has recorded work. Increasingly, Oracle appears to be building software that performs work. Not without governance. Not without controls. But certainly with a higher degree of autonomy than most organisations are accustomed to today.

There were plenty of announcements during the keynote, but Fusion Claw was the one that immediately stood out to me. Not because it was the most futuristic. Actually, quite the opposite. What interested me was the emphasis on governance.

Most organisations are no longer questioning whether AI can generate content, identify patterns or make recommendations. The real question is whether AI can be trusted to execute business processes. That is where many current AI discussions begin to stall. The answer is rarely a technology problem. It is a governance problem.

Throughout the demonstrations, Oracle repeatedly emphasised operating boundaries, permissions, policies, approvals and organisational controls. In other words, autonomy with accountability. That feels much more relevant to enterprise customers than unrestricted AI experimentation. The organisations I speak to rarely say, “We need AI to make decisions independently.” What they actually say is, “We need AI to help us achieve outcomes without introducing risk.” Fusion Claw feels like Oracle’s response to that challenge.

Another concept that caught my attention was Oracle’s discussion around systems of outcomes. For decades, enterprise applications have been systems of record. They store information. Track transactions. Enforce processes. Maintain business truth. Those capabilities remain essential.

Oracle’s argument is that organisations increasingly need something more. A layer focused on achieving business outcomes rather than simply recording business activity. The more I think about it, the more significant that feels. After all, organisations don’t exist to process invoices. They don’t exist to approve purchase orders. They don’t exist to complete workflow transactions. Those activities support the real objectives. Better customer experiences. Stronger financial performance. Improved workforce productivity. Increased organisational agility. More resilient supply chains. Those are the outcomes that matter. If AI can continuously coordinate activity towards those outcomes, then we are moving into genuinely new territory.

Fusion Claw will probably attract most of the headlines. However, I suspect Fusion Companion could prove just as important over time. As enterprise landscapes become increasingly complex, users don’t think in terms of applications anymore. They think in terms of work. They move between systems, channels, data sources and processes. The value increasingly comes from connecting those experiences together.

The vision Oracle presented for Fusion Companion suggests a future where intelligence follows the user rather than remaining confined within individual applications. If delivered successfully, that could become one of the most practical and impactful developments announced during the keynote.

Anyone who has read my recent blogs will know I’ve already posted about Fusion Setup and Configuration Registry (FSCR). Seeing it formally announced during the keynote only reinforced my belief that this could become one of the most important long-term developments for the Oracle ecosystem.

For years, implementation partners have built methodologies, accelerators, templates and frameworks to help customers configure Fusion applications. FSCR has the potential to fundamentally change that model. If Oracle can successfully connect requirements, process design, configuration and AI-driven implementation, then the way organisations deploy Fusion could look very different in the future. It is still early days. But of all the announcements made on Day 1, FSCR may ultimately have one of the biggest impacts on how Oracle projects are delivered.

When I finished watching the keynotes, I kept coming back to one simple thought. For the last two years, the industry has largely been asking: “How can AI help people do their jobs faster?” Oracle now seems to be asking: “How can AI help organisations achieve outcomes with less human effort?” That is a much bigger question. And potentially a much more transformative one.

Whether discussing agentic applications, Fusion Claw, Fusion Companion or FSCR, the underlying message felt remarkably consistent. The goal is no longer simply helping people work. The goal is getting the work done. That doesn’t mean removing people from the process. It means allowing people to spend less time managing the mechanics of work and more time focusing on the decisions, creativity, relationships and innovation that humans are uniquely positioned to provide.

Watching remotely, that was my overwhelming impression of Oracle AI World Day 1. The conversation has moved beyond AI assistance. Oracle is now focusing on AI execution. And that feels like the start of a very different chapter for enterprise applications.

Please note all screenshots are the property of Oracle and are used according to their Copyright Guidelines.

Fusion Claw: Is This Oracle’s Most Important AI Announcement Yet?

Over the past couple of years, we’ve seen Oracle steadily evolve its AI story. It began with AI capabilities embedded within Fusion Applications. Then came AI Agents, followed by AI Agent Studio, giving customers the ability to build, extend and govern their own AI-powered processes. Oracle has unveiled the next piece of the puzzle: Fusion Claw.

I’ll admit that when I first heard the name, I wasn’t entirely sure what to make of it. Another AI agent? A new orchestration framework? Perhaps just another acronym to add to the ever-growing AI dictionary? Having sat through the recent webinar, I came away thinking this may actually be one of the most significant Oracle AI announcements we’ve seen so far.

Not because it introduces more AI. But because Oracle appears to be addressing one of the biggest challenges organisations face today: how do you move from AI recommendations to AI-driven outcomes whilst maintaining governance, accountability and human oversight?

Most enterprise AI today is still fundamentally assistive. Whether it’s generating content, summarising information, analysing data or helping users complete transactions, AI is primarily helping people do their jobs more efficiently. Even many AI agents stop at recommendations. They identify an issue, gather information, analyse options and suggest a course of action. A human then reviews the output and decides what happens next. Fusion Claw appears to be Oracle’s answer to that gap.

Oracle positions Fusion Claw as a governed execution runtime that sits between AI planning and enterprise execution. People define objectives, policies and desired outcomes. Agentic Applications orchestrate business processes. Fusion Claw plans and executes activities. Fusion Applications remain the system of record. That distinction is important.

Oracle is not proposing a future where AI operates outside enterprise controls or invents its own ways of working. Instead, Fusion Claw operates against the same business objects, security model and governance framework that organisations already trust. In simple terms, Oracle is creating a mechanism for translating business outcomes into governed action.

Fusion Claw is designed for complex, high-value work rather than simple transactional activities. Its core capabilities are Analyse; Reconcile; Simulate; Optimise; Predict; and Execute. Those first five capabilities are becoming increasingly common across enterprise AI platforms. The sixth is what makes Fusion Claw different. Execution has traditionally been the point where AI recommendations hand off to humans. Oracle is now seeking to close that gap.

Imagine an organisation identifying a workforce issue, supply chain disruption, financial variance or operational risk. A traditional AI capability might identify the problem. An AI agent might recommend a solution. Fusion Claw is designed to take things further by evaluating multiple options, simulating outcomes, optimising the approach and, where authorised, executing approved actions. That feels like a notable evolution in Oracle’s AI strategy.

The focus is no longer: “How can AI help me complete this task?” Instead, the question becomes: “How can AI help achieve this business outcome?”

One of the most interesting concepts introduced during the session was the distinction between two the operational models Deep Research vs Full Auto. In Deep Research mode, Fusion Claw investigates, analyses and simulates. It evaluates scenarios, compares potential outcomes, surfaces recommendations and presents options for human review.

Importantly, the human remains responsible for making the decision. For many organisations, particularly those operating in highly regulated environments, this will likely be the most comfortable starting point. The value comes from faster analysis and better decision support, whilst maintaining a clear human approval process.

Full Auto mode is where things become significantly more transformative. In this model, Fusion Claw can plan and execute authorised activities automatically in pursuit of a defined business outcome. That naturally raises questions. Who controls it? Who is accountable? What prevents unintended actions?

Anyone who has read my blogs over the past year will know that governance is often the first question that I and customers ask. The technology itself is rarely the challenge. Trust is. The encouraging aspect of Fusion Claw is that governance appears to have been designed into the platform from the outset rather than added afterwards.

Fusion Claw operates inside a private runtime container within the customer’s Fusion environment and works directly with authoritative Fusion business data. Perhaps most importantly, Fusion Claw does not grant itself authority. Organisations decide what actions can be taken, under which circumstances and with what level of oversight. Human accountability remains in place. For customers concerned about explainability, risk and compliance, that message will be every bit as important as the AI capabilities themselves.

One feature that particularly caught my attention was the concept of an Outcome Receipt. Every execution performed by Fusion Claw generates a detailed record that explains: What happened? Why it happened? What information was used? Which controls were applied? Which actions were executed?

At first glance, this sounds like an audit feature. In reality, it could become one of the most important capabilities in the platform. As AI becomes responsible for increasingly valuable business activities, organisations will need evidence. They’ll need to demonstrate how decisions were reached, what data was considered and who authorised the action. For public sector organisations, financial institutions and heavily regulated industries, this level of transparency could prove essential. Many organisations are no longer asking whether AI can make decisions. They’re asking whether they can prove how those decisions were made.

Most enterprise systems operate on a transaction basis. Users initiate activity, the system responds and the process ends. Fusion Claw appears designed to work differently. It is runtime that continuously monitors conditions, reassesses plans and adjusts activities in pursuit of an outcome. Execution can be triggered by user requests; scheduled activities or configured triggers. Rather than waiting for users to notice and react, Fusion Claw is designed to continuously work towards a defined objective. That’s a subtle but potentially significant shift in how we think about enterprise applications.

One other key point of note is Fusion Claw’s ability to work across business functions. Rather than being constrained to a single process or module, it is intended to support end-to-end activities spanning multiple Fusion pillars. This cross-functional capability is important because real business outcomes rarely exist within the boundaries of a single application module.

Most organisational challenges span departments, processes and data sources. Fusion Claw appears designed with that reality in mind. It should also be noted that whilst Fusion Claw is firmly rooted within Fusion Applications, it can interact with external services and other agents where appropriate access has been configured.

A practical concern for many customers will be whether existing investments become obsolete. Fortunately, Oracle’s answer appears to be no. They have confirmed that existing agents can be reused and enhanced rather than rebuilt from scratch. Given that many organisations are only just beginning their AI Agent Studio journey, that will be welcome news.

For those already thinking ahead to roadmap planning, there are a few key details you should know. Fusion Claw is currently targeted for the 26D timeframe. If you have already purchased the licence for the Agentic Applications, you will automatically be able to use Fusion Claw.

By the time you receive 26D, Oracle will have provided 75 Agentic Applications out of the box, of which 25 will be Fusion Claw-powered applications focused on more complex enterprise activities. You won’t be limited to just these 25 Fusion Claw applications, as with all AI Agents and Agentic Applications, you can build your own. This can be via the No Code methods in AI Agent Studio or the Low Code options using CLI.

So, Is This Oracle’s Most Important AI Announcement Yet? Maybe. It’s certainly one of the most ambitious. AI Assist features help users work faster. AI Agents help users make better decisions. Fusion Claw appears to be aiming for something larger: helping organisations achieve business outcomes through governed AI execution. Whether customers are ready to embrace that level of autonomy remains to be seen.

Some organisations will begin with Deep Research, keeping humans firmly in the decision-making loop. Others will be attracted by the possibility of allowing approved activities to execute automatically within carefully defined guardrails. Either way, the conversation is changing. We’re moving beyond asking how AI can assist users and starting to explore how AI can help organisations achieve measurable outcomes. For me, that’s the real significance of Fusion Claw.

The technology itself is impressive, but the bigger story is what it represents: Oracle’s vision for moving from AI that advises, to AI that acts, whilst still maintaining the governance, security and accountability that enterprises demand. And that may ultimately make Fusion Claw one of the most important steps yet in Oracle’s AI journey.

Please note all screenshots are the property of Oracle and are used according to their Copyright Guidelines.