Skip to main content
Every action in Business Operations is a governed capability with authorization, scope, and a receipt. Capabilities are invoked by humans, Twin, or agents and write back to source systems. Read capabilities:
  • bizops.process.read: retrieve process definitions, steps, and SLA thresholds.
  • bizops.workflow.read: access workflow state, history, and linked approvals.
  • bizops.vendor.read: view vendor profile, contracts, spend, and risk data.
  • bizops.policy.read: fetch current policy text, version, and attestation status.
  • bizops.okr.read: retrieve objectives, key results, progress, and confidence.
Write capabilities:
  • bizops.approval.update: approve, reject, or request changes on a pending approval.
  • bizops.vendor.create: add a new vendor record with due-diligence evidence.
  • bizops.policy.attest: record a policy attestation with signer and timestamp.
  • bizops.okr.progress.update: post a progress value and commentary to a key result.
  • bizops.workflow.transition: move a workflow to a new state with reason and attachment.
Communication capabilities:
  • bizops.comment.add: post a comment on a record with mention and threaded reply.
  • bizops.notification.send: push an alert to a practitioner based on SLA or event.
Workflow capabilities:
  • bizops.workflow.initiate: start a new workflow instance from a process template.
  • bizops.approval.route: send an approval request to the designated stakeholder queue.
  • bizops.task.delegate: assign a task to an analyst with context and due date.
Each capability resolves authorization against the user’s role and record scope before execution. On success, a receipt is emitted and the source system is updated. Related