Architecture patterns for governed enterprise AI.

The application invokes a governed Business Capability rather than calling the model directly. The Runtime determines the permitted participant, applicable controls and context supplied for that activity. Model participation therefore occurs inside the declared execution boundary rather than defining that boundary itself.

Organize governed activity around enterprise responsibilities and capabilities rather than around individual model endpoints. A Runtime represents something the business does and is accountable for — which means it survives a change of model, a change of provider and a change of application, because none of those were what defined it.

A Primary Runtime coordinates work that crosses organizational boundaries. A Connected Runtime retains authority over what it exposes and how its published capability is fulfilled — it publishes a contract, not its internals. The coordinator depends on the declared capability, never on the other side's implementation, which is what lets each side change independently.

Where Human Approval governs an activity, authority is part of execution state — not a notification sent after the operation has already happened. The authorized person determines whether the governed operation may continue. A request to proceed is not permission to proceed.

Where a step can be deterministic, keep it deterministic. Lookup, calculation, routing, validation and formatting do not need a model, and putting one there converts a reliable step into a probabilistic one for no gain. Use AI where interpretation or generation is genuinely required — and make the operating environment around it deterministic wherever objective conditions permit.

MergeOn does not require CRM, ERP, finance, HR, identity or operational systems to surrender their authority so that AI can participate. Those systems keep owning what they own. The governed activity is granted bounded participation under declared conditions, which is a much easier thing to approve — and a much easier thing to withdraw.

Design the activity so the organization can establish what was requested, which Runtime and published release governed it, what knowledge and controls participated, whether human authority was required, which permitted participant executed and what outcome followed. MergeOn connects those facts to the governed operation as it happens rather than treating a model transcript as the record of the business event.