Apache-2.0 governed runtime — self-host with @loop-engine/sdk or adopt Boss Cloud on Better Data.
See Commerce Chain Optimization →Loading
Runtime ecosystem
Boss governs how AI executes against your systems, so you can scale operational execution while keeping accountability, governance, traceability, and control.
Boss is operational decision control infrastructure — the coordination layer between AI and real-world operations. Boss governs transitions between intelligence, human coordination, and operational systems — with deterministic guards, structured evidence, and human oversight on every material state change.
This is a runtime ecosystem — not an integration marketplace. Workflows define paths; loops govern whether transitions commit.
How the runtime composes
Providers generate intelligence. Boss governs operational transitions. Channels coordinate human decisions. Integrations execute against systems of record. Evidence + learning explain and improve operations — not reconstructed chat logs.
↓ intelligence in
Providers
Generate analysis and recommendations — they do not commit operational state.
↓ governance
Loops + Guards
Authorize transitions — who may move state, under which policy, with what evidence.
↓ human coordination
Channels
Coordinate people — request approvals, surface decisions, escalate operators.
↓ operational execution
Integrations
Execute operational actions and persist business state after governance passes.
↓ audit + learning
Evidence + Learning
Explain why each transition occurred; feed operational learning loops.
Intelligence systems
Generate analysis and recommendations — they do not commit operational state.
Typical actions
Analyze · Recommend · Classify · Predict · Draft
Examples
OpenAI, Anthropic, Gemini, Perplexity Sonar
Providers are not workflow engines, channels, or systems of record.
Human coordination surfaces
Coordinate people — request approvals, surface decisions, escalate operators.
Typical actions
Notify · Approve · Reject · Escalate · Comment
Examples
Slack, Microsoft Teams, Email, Docs comments, OpenClaw routing
Channels are not integrations — humans decide here; systems execute elsewhere.
Systems of record
Execute operational actions and persist business state after governance passes.
Typical actions
Persist · Trigger · Update · Apply · Sync
Examples
Salesforce, PagerDuty, Jira, Google Workspace, HTTP APIs, Postgres
Integrations are not governance and not human coordination.
Providers
Providers analyze, recommend, classify, predict, and draft — they do not approve in Slack, write to CRM, or bypass guards. Operational intelligence enters the loop; governance decides whether it may advance.
Typical actions: classify · reason · recommend · generate
Operational intelligence — classification, reasoning, and recommendations as governed AI actors with confidence gates and evidence.
@loop-engine/adapter-anthropic
GPT-4o and o-series models as governed actors — recommend, classify, and draft inside loop policy boundaries.
@loop-engine/adapter-openai
Grok 3 as a governed actor via xAI's OpenAI-compatible API.
@loop-engine/adapter-grok
Gemini models for governed generation and analysis — intelligence enters the loop, not CRM.
@loop-engine/adapter-gemini
Grounded retrieval with citations — research-heavy Provider steps for compliance workflows that need verifiable outputs.
@loop-engine/adapter-perplexity
pnpm add @loop-engine/adapter-perplexity
Channels
Channels request approvals, surface decisions, and escalate operators. Slack, Teams, and Docs comments are not integrations — humans decide here; systems execute elsewhere after governance passes.
Typical actions: notify · approve · reject · escalate · comment
Messenger Channel routing for PENDING_HUMAN_APPROVAL — WhatsApp, Telegram, Slack, and Discord with platform-resolved human identity.
@loop-engine/adapter-openclaw
Human coordination surface — approvals, escalations, and operational review. Dual-surface patterns pair Slack decisions with Docs or Sheets work surfaces.
Enterprise Channel for approval loops and operator escalation — not a system of record.
Work surface for AI-drafted proposals and inline review — governance stays in loops; Docs holds context, not policy.
Integrations
Integrations persist business state, trigger workflows, and apply operational side effects — after guards pass. They are not governance and not human chat UIs.
Typical actions: persist · trigger · update · apply · sync
Operational execution — incident triggers, on-call routing, and escalation after governed classification passes.
@loop-engine/adapter-pagerduty
LoopStore persistence — operational state and evidence timelines for production runtimes.
@loop-engine/adapter-postgres
System-of-record updates after approval — opportunity stages, lead qualification, and governed CRM writes (via your connectors or Cloud).
Sheets staging, Docs apply paths, and operational artifacts — Integration executes after Channel approval.
Generic Integration surface for ERP, MAP, and internal APIs — side effects only after guards pass.
Operational patterns
ABM, RevOps, and incident workflows share one spine: Provider → Loop + Guards → Channel → Integration → Evidence. Each pattern reinforces dual-surface operations, deterministic guard boundaries, and evidence at commit time.
More patterns: Examples catalog →
Runtime governance
AI can now act across enterprise systems — APIs and MCP expose operational surfaces where a wrong transition has real business impact. Governance is mandatory: Boss evaluates guards, captures evidence, and routes human escalation before Integrations commit state.
Ecosystem expansion
Platforms and modules that extend the governed runtime — co-marketing, early roadmap access, and production deployments alongside Boss.
Supply chain and demand chain modules on Boss — SCM/DCM loops, participant manifests, and the CCO platform.
Compose streaming AI responses with Boss governance — Providers stay inside loop boundaries.
Partner program
For companies shipping Providers, Channels, or Integrations that participate in Boss Loops in production — not generic marketplace listings.