Crusbro logoCrusbro

Home / Products / Business Automation Agent (OPC agent)

Business Automation Agent Platform (OPC agent) · Enterprise Business Automation

AGENT-OS · AGENT STUDIO · MULTI-ROLE · HITL · WORKROOT · NOTIFY-IDEMPOTENT

Business Automation Agent platform (OPC agent) — runtime foundation crusbro agent-OS (MIT-licensed kernel · 600,000+ hours of run-time data). JSON Schema declares roles / workflow / rules / permissions / data sources, compiled into a multi-role business cluster. crusbro agent studio provides a zero-code packaging path.

  • Manager decomposes intent; Auditor issues accept / reject on milestones and drives remediation
  • Tools authorized per role; high-risk actions trigger HITL
  • Evidence packs land in tenant WorkRoot; outbound deduplicated by idempotency key
  • Live instance: crusbro-media-agent

Visit OPC platform Live demo · instance crusbro-media-agent

Product positioning

Make enterprise business run automatically. Structured work runs through collaborating agents; critical checkpoints are gated by Manager / Auditor + HITL.

Three foundational capabilities:

  • Structured execution — Agents execute; high-risk actions go freeze → preview → approve; audit target for unapproved outbound is zero
  • Manager / Auditor loop — Intent decomposition · milestone decisions · remediation; anomalies auto-enter the human queue
  • Idempotency & auditability — Outbound deduplicated by idempotency keys; evidence packs archived per business order ID

Live instance: crusbro-media-agent.

Foundation: agent-OS × agent studio × OPC platform

The OPC platform runs on agent-OS. agent studio provides zero-code packaging. All three layers share the same evidence-pack semantics and acceptance language.

LayerArtifactResponsibility and dependency
Business layer · OPC platform (this page)Business automation agent cluster · per-business bundle templates · agent.crusbro.com live instance
  • Business expression: roles / workflow / rules / permissions / data sources
  • Runtime foundation: agent-OS
  • Packaging tool: agent studio
Packaging tool · crusbro agent studioZero-code dual-pane · online at studio.crusbro.com · three artifact shapes for Agent / Cluster
  • Configure Agent / Cluster in the browser, download a deployable package bundling agent-OS
  • Studio is one packaging path
Runtime layer · crusbro agent-OSMIT-licensed open-source kernel · GitHub · 600,000+ hours of run-time dataOPC cluster runtime: Agent / Cluster runtime loop, gates / freeze / replay / evidence packs; keeps the cluster stable and errors traceable.

Responsibility split: OPC platform expresses the business; agent-OS runs and governs; agent studio is the packaging tool.

OPC platform · agent studio · agent-OS three-layer relationship agent studio generates OPC platform code (code generation). The OPC platform runtime is built on agent-OS (runtime dependency). agent-OS provides Harness capabilities. All three share the same acceptance language and evidence-pack semantics. OPC platform · Business Automation Agent bundle · roles · workflow · gates · evidence packs Live instance: crusbro-media-agent (content operations) Also: freight · cross-border support · e-commerce · consulting… Code generation Runtime foundation crusbro agent studio · zero-code packaging Packaging tool · browser-configured crusbro agent-OS · embeddable kernel Runtime · Agent loop · Cluster notify Provides Harness Harness · gates · freeze · replay · evidence
Business Automation Agent (OPC agent): Manager, Auditor, virtual roles, HITL and WorkRoot A user or channel triggers a Run; Manager coordinates configurable virtual roles via @mention; roles go through the Tool layer; high-risk actions enter HITL; Manager submits Evidence Pack to Auditor; Auditor's accept or reject drives the remediation loop. All text drawn on top to avoid being hidden by shapes. OPC agent runtime: multi-role collaboration role_key · Skills · Tools injected from templates and tenant config Trigger: User · API · Channel bot Manager Intent · Decomposition · Room coordination @mention dispatch Virtual role A role configurable Virtual role B role configurable Virtual role C role configurable Virtual role … add/remove on demand Tool · Skill · LLM routing per-role authorization · risk tag · trace_id HITL High-risk actions · Allow / Deny / Allow-once Auditor Gate · Evidence Pack accept / reject · finding_id Read-only review · no outbound execution Evidence reject → remediation loop WorkRoot · tenant-isolated workspace deliverables / artifacts · auditable hashes · run_events

Live instance: crusbro-media-agent

crusbro-media-agent is the live running instance of the OPC platform — independently operates a media brand, hot-topic ingest → topic picking → article/video → multi-platform publishing with outbound review, fully closed-loop automated. Same foundation as any OPC cluster.

The instance is assembled from three bundles:

  • default_opc_agents — Manager + Auditor + Worker default skeleton; provides “daily heartbeat” and task routing for all OPC tenants.
  • hot_topic_v1 — Ingest → topic pick → brief → copy/script → article/video → publish; includes finalize_when_idle and approval_gate_before_packaged quality gates.
  • value_led_hotspot_v1 — Value-led image-text variant; only the “content persona + product info” need to be reconfigured to switch domains — no framework change required.

The “hot-topic → publish” closed loop:

StageImplementationGate
Hot-topic ingestionMulti-source crawl and dedup → Worker editorSame-topic aggregation · cross-source consistency gate
Topic pickingworker_topic_ranker scores and ranksPopularity × persona fit gate
Brief and copyworker_brief_generator / worker_script_writerStyle and product-tone consistency gate
Article / videoworker_article_generator / worker_video_composerPersona-specified https images · word-count minimum
Publishworker_publish_specialist dispatches multi-platform APIsHITL mandatory approval · idempotency key prevents resend

crusbro-media-agent is an independently operated brand-agent instance. On the same foundation, launch any business cluster: independent-site, support triage, e-commerce, freight, consulting.

See the live instance agent-OS source Studio source

Business scenarios

The same foundation fits any business driven by email / form / API events and gated by frozen outbound + evidence packs. Validated scenarios:

ScenarioDescriptionExternal parties
Content operations / media accountsHot-topic ingest → pick topic → article / script / video → multi-platform publishMedia open platforms · CRM
Ocean freight / customsEmail merge → booking / customs draft → frozen outboundBooking portal · fleet · customers
Cross-border support / pre-salesMulti-channel message merge → multilingual reply → human gate then sendEmail · IM · e-commerce platforms
Independent site / D2C e-commerceInventory threshold alerts · first-draft support · shipment reconciliationShopify · WMS · logistics APIs
Inquiry → quote outboundReceive email → project merge → CRM update → quote draft → frozen outboundIMAP · price book · customers
Project delivery / light-asset servicesMilestone split · progress email · reconciliation statementsCustomers · finance · suppliers
Consulting / outsourced deliveryRequirement decomposition · first-draft generation · client review gateNotion / Confluence · client email
Procurement / daily reconciliationRFQ and comparison · purchase-order draft · bank-flow reconciliationERP · bank APIs · suppliers

One mechanism, every scenario: structured task → role cluster → gate · freeze · evidence pack. To switch business, swap the bundle and Skills.

Launch your OPC business Open agent studio

Core mechanisms

  • Run and trace_id — Every production task carries a trace_id; tool calls, Room messages, HITL decisions and exports are all linkable and replayable. Deliverables and evidence packs are archived against the business order ID.
  • Manager / Auditor and HITL double gate — HITL decides “may this tool / outbound action execute”. Auditor reviews the “stage Evidence Pack”. Outbound must pass both checks before release.
  • Skill / Tool governance — Skill is injected before the LLM call. Tool is authorized by role and can be risk-tagged to trigger HITL. Configuration release revision is bound to the running Run; disputes settle against config_version.
  • Freeze and evidence pack — Pre-outbound attachments are SHA-256-hashed and strictly match the frozen copy. Evidence packs are archived per business order and are independently auditable.
  • Notify idempotency — Cluster state changes are deduplicated by idempotency keys. Repeated delivery of the same event triggers effect only once; duplicate pushes never trigger duplicate outbound.
  • Multi-tenant isolation — WorkRoot data-plane isolation. Each OPC tenant maps to an independent cluster instance; the same foundation can run multiple business types with mutually invisible evidence.

Key indicators (acceptance examples)

Session replayTool sequence and timeline indexable and retrievable (typical deployment < 400 ms)
Freeze / GatePre-outbound attachment SHA-256 matches the frozen copy; HITL decisions bind to tool_call_id
Notify idempotencySame event arriving repeatedly takes effect only once; outbound queue runs as a separate process with idempotency-key dedup
Mandatory rolesPublished configuration contains exactly one manager and one auditor (release verification)
One-click launchDownload an OPC package from studio.crusbro.com and deploy — granularity starts at “a few hours”; live instance crusbro-media-agent is the acceptance reference.

Feature list and specifications

CapabilityDescription
Console (standalone deploy)Account, LLM credentials, per-business email / API credentials, Agent start/stop etc. are provided by the OPC runtime — outside the scope of this website repo.
Operations interventionManual takeover, session suspension, single-step replay; roll back to any config_version.
Open APIInternal REST docs ship with versions; sample requests can be imported into a Postman collection.
DeploymentLinux cluster / K8s; message and vector stores can be self-hosted; ships with the same agent-OS foundation package.
Extend with a business bundleTo add a new business type, just add manifest.json + Agent JSON under bundles/<business_id>/ — no framework change.

Data and security

Credentials reside in customer-controlled KMS; progress and streaming output never echo secret plaintext; audit exports contain no private keys. OPC shares the same security model with agent-OS and agent studio: WorkRoot isolation · outbound freeze · gate decisions replayable.

Next steps

  • See it live — agent.crusbro.com: crusbro-media-agent running · business expression · gate decisions · evidence pack delivery and replay
  • Zero-code packaging — studio.crusbro.com: configure Agent / Cluster · download a deployable package with agent-OS bundled
  • Read the source — agent-OS · agent studio · MIT open-source
  • Talk to deployment — business model · workflow construction · agent cluster design · implementation acceptance · One-Person Company solution

Visit OPC platform One-Person Company solution Open agent studio Book a demo