S Shortlisted
Home / AI Agents / Fusion Claw Architecture
Architecture · announced 29 Sep 2026

Fusion Claw architecture: how Oracle's governed agent runtime works.

Fusion Claw is the execution runtime under Oracle's newest Fusion Agentic Applications. It splits every job in two: a frontier AI model thinks (plans, reasons, re-plans), and deterministic enterprise computation does (calculations, rules, optimisation, transactions). Around both sit three governance layers that decide what a run may touch and record what it did. This page shows each part on one diagram, in plain words. New to the topic? Start with Fusion Claw explained simply.

Oracle Fusion Claw architecture A business goal enters the Enterprise Operating Envelope. Inside it, the Outcome Trust Harness scopes one run. Within the run, a frontier model plans and re-plans while deterministic computation executes, both limited to permitted Fusion data and actions. The automation level decides where humans review. Every run ends with an Outcome Receipt. 1 · BUSINESS GOAL "Reconcile this period and explain exceptions" 2 · ENTERPRISE OPERATING ENVELOPE (set before any run) objectives · SOPs · policies · constraints · permissions · risk thresholds · decision rights · approvals · escalation 3 · OUTCOME TRUST HARNESS (applied to each run) scopes identity, capabilities, data and actions · isolated workspace per job (reported) REASON Frontier model Gemini or OpenAI at launch plans · reasons · learns re-plans when things change EXECUTE Deterministic computation calculations · business rules optimisation · simulation transaction processing plan results Fusion data, tools and transactions only what the harness allows for this run 4 · AUTOMATION LEVEL YOU CHOOSE, PER PROCESS quick assistance → people review the plan → governed full auto within delegated authority 5 · Outcome Receipt authority applied · evidence used · decisions made transactions executed · result
Component names are Oracle's. The per-job isolated workspace comes from launch coverage, not the announcement. Layout and plain-words labels are ours.

The five parts, one at a time

1. The business goal

Every run starts with an outcome, not a prompt for a chat. Oracle frames Claw work as "Claw Outcomes": reconcile the ledger, build the staffing plan, consolidate shipments, set territories. The goal is what the run is judged against.

2. Enterprise Operating Envelope

The envelope is the company's rulebook for the run, written before anything executes. Oracle lists what it holds: objectives, standard operating procedures, policies, constraints, permissions, risk thresholds, decision rights, approval requirements and escalation boundaries. Think of it as a job description plus a delegation-of-authority matrix. Launch coverage reports that AI can help turn company documents into the executable rules the envelope enforces.

3. Outcome Trust Harness

The harness applies the envelope to one specific run. Oracle says it governs identity, capabilities, data and actions for that run. Trade press adds that each job runs in a dedicated, isolated workspace that only the requesting application can open, has no independent internet access, and is removed when the job finishes. SiliconANGLE reports that the model has no direct access to business objects: it works through the runtime.

Inside the run: reason and execute

This split is the core design decision. The frontier model (Gemini or OpenAI at launch) handles what needs judgement: understanding the goal, planning the steps, interpreting surprising results, and re-planning. Deterministic computation handles what needs precision and volume: calculations, business rules, optimisation, simulation and transaction processing. Oracle's argument is that this makes complex work economical, because expensive AI inference is used only where intelligence is needed, and exact results come from code rather than from a model's guess.

Oracle also describes continuous re-planning: when an input changes mid-run, the model revises the plan and the runtime executes the new one. SiliconANGLE gives the staffing example of a plan being reopened automatically when an employee calls in sick.

4. Automation level

Customers choose, per process, how much authority to delegate. Oracle describes the range as "quick assistance to governed full auto execution within explicitly delegated authority". Coverage describes two practical modes: a research mode where Claw models, simulates and optimises and a person reviews before anything is implemented, and an autonomous mode within granted permission.

5. Outcome Receipt

Each completed run produces an auditable receipt: the authority applied, the evidence used, the decisions made, the actions and transactions executed, and the result. This goes further than a technical log. It is written for a process owner, governance committee or auditor to review.

Where Claw sits in the Fusion AI stack

LayerWhat it isWho mainly works with it
Fusion Agentic ApplicationsReady-made AI applications and workspaces by business area. 75 in total after the Claw launch.Business users and managers
Fusion ClawThe governed execution runtime that powers 25 of those applications, the ones built for complex, long-running workProcess owners, consultants, security and audit
AI Agent StudioThe toolkit to build and extend agents. Futurum Group reports Claw ties into Agent Studio for no-code and pro-code extension.Consultants and developers
Models and infrastructureGemini and OpenAI frontier models, running on Oracle Cloud InfrastructureOracle-managed

Earlier Agentic Applications, such as those on our Agentic Applications page, mostly watch an area, prioritise exceptions and recommend actions. Claw-powered applications are aimed at the next step: completing large jobs within delegated authority.

The 25 launch applications

Oracle's announcement highlights four Claw-powered applications, one per pillar:

The other 21 were not named in the announcement or the coverage we checked. We will add them when Oracle publishes the list. Check Oracle's documentation for what is enabled in your environment.

What a consultant designs for a Claw rollout

Claw executes the process you define, so the design work moves from screens to authority. For each process, agree and document:

  1. The outcome and its success measure. For example, "all reconciling items explained, with fewer than X open exceptions above Y value".
  2. The envelope. Which policies and SOPs apply, which constraints are hard, and what the risk thresholds are in money, volume or count.
  3. Decision rights and approvals. What Claw may post on its own, what needs a human approval, and who that human is.
  4. Escalation. When Claw must stop and hand back, and to whom.
  5. Data readiness. Master data quality, open interfaces and known data gaps. Analysts flag fragmented data as the main brake on value.
  6. Receipt review. Who reads Outcome Receipts, how often, and what triggers a change to the envelope.
  7. Cost tracking. AI unit consumption per run against the time saved. Info-Tech Research Group notes that costs vary with actions, model choice, testing and human review, and that unused pooled units can expire.

Begin with a person reviewing every plan, and widen the delegated authority only when the receipts show consistent, correct decisions. Our Build Readiness Checklist covers the security, data and testing blocks.

Cost model, as reported

SiliconANGLE and TechTarget report that Claw is included at no additional charge with the Fusion Agentic Applications offering, which is sold separately from standard Fusion subscriptions, and that usage is paid in Oracle AI units as work completes. The Letter Two reports that AI units are consumed by the model's planning work, while the deterministic execution consumes none, and that the runtime reuses successful solution paths from earlier jobs. These points come from reporting, not from the announcement, so confirm them against your contract.

Checked Component names, the four named applications, model providers, the 25 and 75 counts, and OCI hosting come from Oracle's announcement, Oracle Extends Fusion Agentic Applications with Introduction of Fusion Claw (29 Sep 2026). Isolation, modes, pricing and Agent Studio details come from The Letter Two, SiliconANGLE, TechTarget, CIO and Futurum Group. Verified 1 Oct 2026. The runtime is new; behaviour, availability and licensing can change, so verify in your own environment.

Fusion Claw architecture: questions consultants are asking

What are the main components of Oracle Fusion Claw?

A frontier model for reasoning and planning, deterministic enterprise computation for execution, the Enterprise Operating Envelope (the rules), the Outcome Trust Harness (which applies those rules to each run), and the Outcome Receipt (the auditable record of each run).

Why does Claw separate reasoning from execution?

To make complex work precise and economical. The model is used only where judgement is needed; calculations, rules and transactions run as deterministic code, so results are exact and AI inference costs stay lower.

How is Fusion Claw different from AI Agent Studio?

Agent Studio is the toolkit for building and extending agents. Fusion Claw is the governed runtime that powers 25 of Oracle's Fusion Agentic Applications for long-running, complex work. Analyst coverage reports that the two connect for no-code and pro-code extension.

Does Fusion Claw keep an audit trail?

Yes. Every completed run produces an Outcome Receipt recording the authority applied, evidence used, decisions made, transactions executed and the result.

Where to next

The plain-words version, and the rest of the agent stack: