The Platform / Convergence Engine
A declared Outcome does not trigger a workflow. First, XOPS converges on the current Position, applicable policy, dependencies, and active transitions. The Convergence Engine then compiles the valid runbook from a library of autonomous operational building blocks and executes it deterministically.
Every decision is logged. Every state mutation is compensable. Every Outcome is auditable, replayable, and recoverable.
XOPS does not execute first and reconcile later.
No silent drift. No ungoverned execution. No undocumented behavior.
Where the Convergence Engine fits
Cortex exposes operational truth. Arbiter resolves competing events and changing state. The Convergence Engine turns the declared Outcome and converged Position into the one valid execution plan.
The result is not a generic workflow. It is a runbook compiled for the current state, current policy, and intended Outcome.
Declared Outcome
Current Position + policy + dependencies
Convergence and arbitration
Compiled runbook
Deterministic execution
Verified Outcome
How it works
Every Outcome flows through the same five stages. Each stage has a contract. Each transition is logged. No state-changing action executes outside the compiled plan, governing policy, and required approvals.
1 · Declare
A policy, event, operator, or agent declares the Outcome: what must become true. The Outcome is interpreted against the governing policy and affected entity.
2 · Converge
XOPS reconciles the current Position across the relevant systems, applies policy, evaluates dependencies, and accounts for active or competing transitions. Execution does not begin until the platform has a sufficiently confirmed operating reality.
If the current state cannot be confirmed, execution pauses rather than guessing.
3 · Compile
The Convergence Engine composes the valid runbook from the autonomous work-function library: the required actions, ordering, decision points, exception paths, approvals, and compensations.
4 · Execute
The compiled runbook executes deterministically across the affected systems. The same declared Outcome, converged Position, and policy produce the same plan and result.
5 · Verify
XOPS observes the resulting state and confirms the declared Outcome is now true across every affected system. If not, the Outcome remains open and the platform reconciles the exception.
Across every stage: every decision is logged, every mutation is compensable, and every Outcome is replayable.
Outcome is the intent. Runbook is the plan. AWFs are the executable building blocks.
Outcome
The state the organization has declared must become true.
Runbook
The deterministic execution plan compiled for a declared Outcome. It groups the required autonomous work functions, decision points, exception paths, approvals, sequencing, and compensations into one governed plan.
Atomic Work Function
The smallest autonomous unit of execution. One bounded action against one system. Idempotent, logged, policy-governed, and compensable where state changes.
Decades of operational practice, converted into autonomous building blocks
Enterprise IT has spent decades formalizing operational work through ITIL. XOPS has converted those practices into a reusable library of autonomous work functions that can be composed into governed runbooks.
~300
Atomic Work Functions, seven domains
create identity · assign entitlement · reserve device · revoke access · update cost center · reclaim license · activate mobile plan · retire asset
~60
Runbooks, shipped pre-built
Not static scripts. Plans assembled from the platform’s execution library for the current state, current policy, and intended Outcome.
Policy inheritance with scoped overrides
Global policy establishes the default. Regional, business-unit, team, persona, device-class, and entity-level rules refine it where required. The engine compiles the runbook using the most specific approved policy that applies.
Standardized by default. Specific where necessary. Fully traceable.
One Outcome, start to finish
Declared Outcome
Replace an employee’s laptop without interrupting their ability to work.
Converged Position
The platform confirms:
Compiled runbook
The Convergence Engine assembles:
Deterministic execution
The same Outcome, Position, and policy compile to the same governed plan.
Verification
The Outcome remains open until the employee can work on the replacement device and the old device has entered the approved recovery path.
Determinism as trust
Audit can reconstruct why the plan was selected.
Operators can simulate the plan before execution.
The platform can replay the Outcome using the same state and policy.
Exceptions are visible rather than hidden in human judgment.
AI agents cannot invent their own execution paths.
The same governing contract applies regardless of whether the request came from an operator, workflow, API, or agent.
Deterministic does not mean reality stands still
The Convergence Engine compiles and executes the valid plan. Arbiter protects that plan when the operating state changes, events collide, or another transition affects the same entity.
The engine does not blindly continue against stale assumptions. The current Position is re-evaluated, the collision is resolved, and the Outcome is either continued, revised, paused, or recovered under policy.
Deterministic execution, dynamic operating reality.
Compensating recovery
Every state mutation includes its defined compensation or recovery action. If execution is interrupted or the operating reality changes, the engine returns the estate to a known governed state.
Also known internally as saga-based recovery.
Reversibility does not mean pretending every action can be undone. It means every state-changing action has a defined compensation, recovery path, or governed exception.
Governance
The execution log isn’t a side effect. It’s the same data the engine uses to recover. Every audit query, every postmortem, every “what happened on Tuesday at 4:14am” resolves to a deterministic, replayable trace.
You can replay an Outcome from any point. Simulate the next one before it fires. Prove what happened. SOX, SOC2, ISO27001, ISO42001: the audit trail isn’t a feature, it’s the runtime.
# execution_trace.log
10:42:01 outcome=EMP-R-001 entity=person:sarah.chen
10:42:01 position.employee=confirmed version=18422
10:42:01 policy=contractor.onboarding.v3.2
10:42:01 dependency_check=passed
10:42:01 collision_check=none
10:42:02 compile runbook=contractor.onboarding variant=emea.remote
10:42:02 plan_hash=7f19b3
10:42:02 awf=workday.set_end_date ok comp=clear_end_date
10:42:03 awf=okta.create_identity ok comp=disable_identity
10:42:04 awf=okta.assign_groups ok comp=remove_groups
10:42:05 awf=intune.push_profile ok comp=remove_profile
10:42:06 awf=servicenow.order_dev ok comp=cancel_order
10:42:07 awf=slack.invite_channels ok comp=remove_channels
10:42:09 verify intended_state=true
10:42:09 outcome.complete duration=8.2s
# every step compensable. every transition logged. every Outcome replayable.
How execution is carried out
Observe · DataOps
DataOps capabilities continuously maintain the operational signals required for convergence.
Coordinate · Service
Service execution coordinates the compiled runbook across systems, teams, approvals, and dependencies.
Act · Platform
Platform execution invokes the individual Atomic Work Functions against each system.
Where humans stay in control
Automation with checkpoints, not a black box.
Truth gate
If the current Position is unresolved, contradictory, or below the required confidence threshold, execution does not begin.
Approvals
Configurable gates: auto, manager, director, named approvers.
Overrides
Override any decision before commit. Logged with reason and scope.
Pauses
Pause an Outcome, runbook, or whole domain. Resume cleanly.
Audit review
Replay any decision with the data the engine saw at commit.
Policy governance
Policy changes flow through review with diffs and approvers.
The Convergence Engine turns every declared Outcome into a governed runbook that can be inspected, simulated, executed, verified, replayed, and recovered.
Deterministic execution is how the math comes back to IT, and so does the trust.
