Keep your systems.
Connect their decisions.

Records, coordination, and participation.

Systems of record own business transactions. World Runtime maintains the state and decision context needed to coordinate across them. Domain applications, services, and agents contribute evidence and proposals.

An implementation defines what to read, how to map identities and relationships, and which actions may be written back. Existing workflows can carry out parts of an approved response.

Events preserve what happened; projections reconstruct the current view. A graph makes entities and relationships explicit, while simulation branches represent alternatives.

A branch stays separate from committed state. Its assumptions and results can inform a proposal without silently changing the operational record.

An AI model can interpret evidence and propose a response. That proposal does not give it authority to change the operational record.

In i5 World-Runtime, policy checks and approval boundaries govern whether a proposed action can proceed. Keep the evidence, alternatives, checks, and authorization with the decision so people can inspect how it was made.

The architecture keeps these responsibilities independent of a particular model provider, cloud, or agent framework. The public contracts define the supported ways to connect them.