THE ORCHESTRATED ENTERPRISE
DM’S OPEN

TECHNOLOGY / WORLD RUNTIME

Build around the world your business actually operates in.

A supplier delay, a city incident, a team of AI agents: each can set off decisions beyond one team or system. With i5 World-Runtime, your developers can model the situation, replay how it changed, and compare responses before committing to one.

WORLD RUNTIME / IN PRACTICE

Explore a decision.

Decision explorer Synthetic data

Port expansion / THE DECISION

More capacity. Which tradeoff?

Compare terminal expansion plans against cost, environmental constraints, and the authority to commit.

Horizon
5 years
Alternatives
3
Decision owner
Infrastructure team
Operating contextSHARED STATE
TerminalCapacity under pressure
EnvironmentMitigation required
CommunityJobs & local impact
RegulatorPermit review pending
One decision contextEvidence · alternatives · authority

Capacity gains only make sense alongside the conditions needed to deliver them.

Event history
  1. Demand forecast updated

    A higher cargo forecast triggers a capacity review.

  2. Community feedback added

    Local employment and construction impacts join the decision context.

  3. Permitting risk flagged

    The alternate site conflicts with the example environmental constraint.

  4. Mitigation plan added

    The current-site plan includes an emissions reduction package.

  5. Alternatives compared

    Three fixed projections are ready for human review.

Compare alternativesEXAMPLE PROJECTIONS

Expand current site

Human review required

Capacity
+24%
Investment
$1.3B
Emissions
−8%
Suggested option
Why this result?

The largest capacity gain comes with medium permitting risk. Funding and permit approval are still required.

Phase the expansion

Within example policy

Capacity
+16%
Investment
$850M
Emissions
−15%
Why this result?

Lower investment and a larger projected emissions reduction, with less new capacity. It remains an alternative for the infrastructure team.

Move to another site

Blocked by example policy

Capacity
+18%
Investment
$1.1B
Impact
High
Why this result?

High environmental impact breaches this example’s site constraint. Additional capacity does not override the restriction.

THE NEXT DECISION

Recommend current-site expansion

Take the capacity case and mitigation plan to the infrastructure team. A recommendation does not release funding or grant a permit.

Authority: infrastructure team · Approval pending
Evidence & assumptions

Illustrative data adapted from supplied workbench designs. Values, event sequences and policy outcomes are fixed examples, not a recorded runtime run or measured results. The linked runtime source explains the underlying pattern; it does not verify these figures.

  • Capacity and emissions changes are relative to the current terminal baseline.
  • Costs are illustrative capital estimates; mitigation is assumed to work as modeled.

Supply network / THE DECISION

A delayed vessel. Three ways forward.

Port congestion puts electronics deliveries at risk. Compare service, time, and the added cost of a reroute.

Disruption
48-hour delay
Production
2 lines at risk
Commitments
5 priority orders
Operating contextSHARED STATE
MV HorizonElectronics components
SingaporePort congestion
ProductionInventory running low
CustomersPriority deliveries
One decision contextEvidence · alternatives · authority

The same shipment connects port capacity, production plans, and customer commitments.

Event history
  1. Order confirmed

    Priority deliveries enter the shipment plan.

  2. Shipment departed

    Components are in transit to the receiving hub.

  3. Weather advisory issued

    Planners review exposure along the route.

  4. Congestion delays vessel

    The team compares reroutes before changing delivery commitments.

Compare alternativesEXAMPLE PROJECTIONS

Reroute via Jakarta

Human review required

Arrival delay
+2 days
Service level
92%
Added cost
+12%
Suggested option
Why this result?

The strongest service projection costs more. This example requires a transport planner to approve the added spend.

Reroute via Shanghai

Within example policy

Arrival delay
+5 days
Service level
85%
Added cost
+8%
Why this result?

A smaller cost increase leaves more priority orders exposed to delay.

Wait for original route

Blocked by example policy

Arrival delay
+6 days
Service level
64%
Added cost
0%
Why this result?

Avoiding added transport cost drops projected service below this example’s 80% floor.

THE NEXT DECISION

Recommend the Jakarta reroute

Protect service with the shortest projected delay, then obtain approval for the extra transport cost.

Authority: transport planner · Approval pending
Evidence & assumptions

Illustrative data adapted from supplied workbench designs. Values, event sequences and policy outcomes are fixed examples, not a recorded runtime run or measured results. The linked runtime source explains the underlying pattern; it does not verify these figures.

  • Delay is measured against the original delivery plan.
  • Service level means the projected share of commitments met. Alternate port capacity is assumed available.

City response / THE DECISION

One incident. Connected services.

An industrial fire affects roads, transit, and hospital access. Compare coordinated response plans.

Incident
Riverside fire
Transit
3 lines affected
Residents
120k in area
Operating contextSHARED STATE
RiversideIndustrial fire
Central StationReduced service
North GeneralAccess disrupted
Eastside HospitalAlternative access
One decision contextEvidence · alternatives · authority

Changing a route can protect hospital access while moving disruption elsewhere.

Event history
  1. Fire reported

    The incident establishes a common operating context.

  2. Road closures initiated

    The affected corridor is closed to through traffic.

  3. Air-quality advisory issued

    Responders consider wider resident exposure.

  4. Transit service reduced

    Three lines need alternative routing.

  5. Hospital access impact detected

    Access becomes a constraint on response plans.

  6. Response plans compared

    Alternatives balance access, disruption, and cost.

Compare alternativesEXAMPLE PROJECTIONS

Reroute transit & traffic

Within example policy

Hospital access
98%
Residents affected
12k
Response cost
$0.8M
Suggested option
Why this result?

Alternative routes preserve the highest projected hospital access with the smallest resident impact.

Close affected corridor

Human review required

Hospital access
76%
Residents affected
68k
Response cost
$0.4M
Why this result?

The wider disruption crosses this example’s resident-impact threshold and requires incident-command approval.

Keep current routing

Blocked by example policy

Hospital access
62%
Residents affected
42k
Response cost
$0.1M
Why this result?

Projected access falls below this example’s minimum. Low response cost cannot justify the access loss.

THE NEXT DECISION

Recommend coordinated rerouting

Bring transit and emergency services together around the access plan before routes change.

Authority: incident command · Coordination pending
Evidence & assumptions

Illustrative data adapted from supplied workbench designs. Values, event sequences and policy outcomes are fixed examples, not a recorded runtime run or measured results. The linked runtime source explains the underlying pattern; it does not verify these figures.

  • Hospital access is an illustrative share of trips maintaining access, not a clinical measure.
  • Example thresholds: access at least 70%; impacts above 50,000 residents require review. These are not operational safety standards.

Agent coordination / THE DECISION

A campaign goal. Explicit authority.

Agents propose campaign changes. Compare potential reach with budget and publishing permissions.

Goal
Product launch
Proposals
3
Conflict
CMS write access
Operating contextSHARED STATE
Research agentMarket evidence
Content agentCampaign assets
Channel agentDistribution proposal
Review leadPublishing authority
One decision contextEvidence · alternatives · authority

A promising proposal still has to fit the permissions granted to the agents.

Event history
  1. Research updated

    Market evidence joins the campaign context.

  2. Launch proposal drafted

    Content and channel choices are proposed within the current scope.

  3. Targeting alternative added

    An agent proposes a smaller adjustment to the existing campaign.

  4. Policy conflict flagged

    A proposed expansion would need additional CMS permissions.

  5. Write-access request held

    The review lead can inspect alternatives; no publishing occurs.

Compare alternativesEXAMPLE PROJECTIONS

Launch on approved channels

Human review required

Expected reach
+42%
Budget
$250k
Risk
Low
Suggested option
Why this result?

The plan fits the example budget ceiling and approved channels, but publication still needs human sign-off.

Expand CMS access

Blocked by example policy

Expected reach
+68%
Budget
$400k
Risk
High
Why this result?

The largest projected reach requests unapproved CMS write access and exceeds the $250k budget authority.

Adjust current targeting

Within example policy

Expected reach
+28%
Budget
$120k
Risk
Medium
Why this result?

A smaller adjustment stays within current permissions. Any later publication remains a separate approved action.

THE NEXT DECISION

Review the launch proposal

Keep the reach projection, budget, and permission checks together for the human reviewer. Hold the expanded-access proposal.

Authority: campaign review lead · Sign-off pending
Evidence & assumptions

Illustrative data adapted from supplied workbench designs. Values, event sequences and policy outcomes are fixed examples, not a recorded runtime run or measured results. The linked runtime source explains the underlying pattern; it does not verify these figures.

  • Reach changes are illustrative projections against the existing campaign.
  • The agents have read access to customer data. New write permissions and publication require human authorization.

01 / Supply networks

Compare reroutes before changing the plan.

A delayed shipment affects inventory, production, and delivery promises. Your team could build a planning service that connects those dependencies and compares reroutes against the same disruption.

The public supply-network scenario rebuilds state from events and compares reroute alternatives, keeping cost and loss tradeoffs visible alongside a simulation-backed recommendation.

Your team would connect its own ERP, transport, and partner data, then validate the model before using it for operational decisions.

Inspect the supply-network example

02 / City operations

Coordinate around one incident.

A major incident can affect transit, utilities, and hospital access at once. Your team could build a shared incident model that lets participating agencies compare response plans and see which decisions need approval.

In the public city-operations scenario, policy blocks plans that lose hospital access, warns about long transit detours, and requires approval for large resident impacts.

This uses scenario data. Agency connections, data-sharing agreements, and public-safety controls would need to be developed and validated with the participating organizations.

Inspect the city-operations example

03 / Multi-agent AI

Keep delegated work within agreed bounds.

Several agents can pursue different objectives while acting on the same work. Your team could build a review service that records their proposals, compares alternative plans, and checks delegated authority before actions proceed.

The public multi-agent scenario blocks unreviewed expansion of write access, flags conflicting objectives, and sends larger delegations for approval.

Your team chooses and connects the models, agent frameworks, and tools. The example demonstrates coordination and review; it does not establish that an agent’s answer is correct.

Inspect the multi-agent example

04 / Start with one decision

These are implemented examples in the repo. Start with the example closest to your problem, model your own domain, and test its decisions against familiar situations.

Build through documented interfaces such as the Public API, Python SDK, and extension contracts.

Existing systems retain their authority over business records. Your team defines the connections, policies, and people responsible for action.

Plan your first implementation

Open the developer quickstart

LET’S TALK

What could work better?

A stubborn problem. A promising idea. Start wherever you are.

DM’S OPEN