Operator concepts
Intent, outcome, mandate, Operation Cells, settlement, and evidence.
Read guide →Resources
Understand the operating model.
Explore Operator concepts, reference architecture, interfaces, synthetic demonstrations, and the evidence model behind controlled enterprise action.
Documentation library
From concept to controlled operation.
Platform architecture
Control plane, outcome runtime, application edge, and assurance plane.
Read guide →Outcome Contracts
Define preconditions, policy, work, verification, recovery, and receipt requirements.
Read guide →Execution semantics
Durability, idempotency, unknown outcomes, compensation, and settlement.
Read guide →MCP and REST
Publish governed capabilities and submit outcomes from agents and applications.
Read guide →Operate Operator
Deployment, configuration, observability, intervention, retention, and continuity.
Read guide →Outcome API
Request a business outcome—not a sequence of raw calls.
Any authorized application can submit the same bounded outcome that Siba or another agent discovers through MCP.
Stable idempotency keyEnd-user delegationDeclared outcome and scopeTraceable response
POST /v1/outcomes
Authorization: Bearer eyJ...
Idempotency-Key: offboard-10482-2026-08-28
{
"operationCell": "workforce.offboard.v2",
"intent": {
"employeeId": "10482",
"effectiveAt": "2026-08-28T21:00:00Z",
"transferOwner": "10817"
},
"delegation": {
"subject": "user:amorgan@example.com"
}
}Reference demonstrations
See the behavior—including when things go wrong.
All reference demonstrations use synthetic organizations, identities, transactions, and application data.
Governed supplier onboarding
Siba gathers the request, Operator enforces approval, coordinates three systems, independently verifies supplier state, and issues a receipt.
12-minute walkthroughIndeterminate ERP response
An application times out after receiving a write. Operator freezes duplicate execution, reads back state, reconciles the late result, and settles safely.
8-minute walkthroughPartial workforce offboarding
Identity access closes but an application transfer fails. Operator contains the partial outcome, escalates residual work, and preserves evidence.
10-minute walkthroughOutcome Receipt anatomy
A portable explanation of enterprise action.
The receipt is an operational record—not an agent-generated narrative. Its statements derive from the contract, deterministic control decisions, recorded execution events, and independent observations.
1Intent
Requested business outcome and bounded scope
2Authority
Requestor, end-user delegation, mandate, and environment
3Policy
Evaluated controls, inputs, decision, and approvals
4Execution
Operations attempted, effects, retries, and provider references
5Verification
Independent observations and business-state assertions
6Recovery
Reconciliation, compensation, escalation, and residual state
7Settlement
Final outcome, completion time, and evidence integrity
Frequently asked questions
Operator, plainly explained.
Is Operator an AI agent?
No. Operator is the controlled execution platform used by AI agents and other authorized software. Siba is included as Sirvisetti's first-party agent.
Does Operator replace an iPaaS or workflow platform?
Not necessarily. Operator can use existing integrations and workflows. Its distinct responsibility is the authority, transaction safety, verification, recovery, and evidence boundary for software-initiated business outcomes.
Must agents use MCP?
No. MCP is one supported agent interface. Applications and workflows can request the same outcomes using REST, SDK, event, and approved enterprise interfaces.
Does Operator require direct application access?
Operator's application-facing workers require only the scoped capabilities needed by their Operation Cells. Credentials stay at the controlled application edge and are never handed to the requesting agent.
What happens when an application times out?
Operator can classify the operation as indeterminate, prevent unsafe retry, perform independent readback, reconcile late responses, and escalate if the business state cannot be established.
Can Operator run inside our network?
Yes. Customer-managed and hybrid deployment models place execution, application connectivity, and sensitive state within customer-controlled infrastructure.
Move from architecture to one working outcome.
Use the reference model to define a controlled operation across the applications you already run.
Contact sales