Crusbro logoCrusbro

Home / Products / Business Agent

Business Agent · multi-role platform

MULTI-ROLE · MANAGER / AUDITOR · HITL · WORKROOT · plant-floor UA

The One‑Person Company (OPC) Agent is not a single agent—it is a configurable “agent company” platform. With a JSON Schema, you define roles, workflows, rules, permissions and data sources, then assemble them into runnable multi‑role collaboration. LLMs execute tasks, while critical steps can enforce HITL and Gate controls for stable, reliable, low‑error and verifiable delivery.

Each tenant maps to one agent‑cluster instance: Manager decomposes intent and coordinates virtual roles; Auditor gates milestones with accept / reject and drives remediation loops; Skills/Tools are authorized per role and risk tags can force HITL; deliverables and evidence live in WorkRoot for data‑plane isolation. The diagrams below show in‑cluster traffic and external mail flows.

Try now Business Agent platform demo & trial environment

Product overview

Platform capabilities: OPC life-cycle management; role/Tool/Skill/HITL configuration; full-chain observability and audit export via trace_id; integration with enterprise account and subscription systems.

Field delivery: On PLC/SCADA / MES we add UA subscriptions and guarded writes. In freight, mail_monitor fans inbound mail into booking, documentation and manifest workers; every outbound email goes through the freeze snapshot + human approval double gate, keeping ownership clear and results verifiable.

Business Agent: Manager, Auditor, Virtual Role, HITL and WorkRoot A user or channel starts a Run; the Manager coordinates virtual roles via @mention; roles invoke Tools; high-risk actions enter HITL; the Manager submits an Evidence Pack to the Auditor, who accepts or rejects to close the loop. Bottom layer: shapes and connections (all text is placed behind to avoid being blocked) Virtual role (generalization: not bound to specific industry role_key) Top level: all visible text Business Agent runtime: multi-role collaboration Decoupled from specific industries; role_key, skills, and tools are injected from templates and tenant configurations Trigger: User · API · Channel Bot Manager Intent · Teardown · Coordination within Room @mention dispatch Virtual character A role configurable Virtual character B role configurable Virtual character C role configurable virtual character… Can be added or deleted Tool · Skill · LLM Routing Authorization by role · Risk label · trace_id HITL High Risk Actions · Allow / Deny / Allow-once Auditor Gate · Evidence Pack accept / reject · finding_id Read-only review · Do not execute outgoing Tools Evidence reject → rectify loop WorkRoot · Tenant isolation workspace deliverables/artifacts · auditable hashes · run_events

Freight forwarding case: email interaction with external parties

Take ocean freight forwarding and customs as an example: inside the cluster, the Manager coordinates logistics, customs, doc and other roles; externally the work still appears as mail flows between customers, booking portals, fleets and hub services. Booking and customs outbound emails are released only after HITL and Auditor double checks. The diagram below shows external parties only; in-cluster collaboration is shown above.

Details Try now

Ocean freight forwarding email interaction: customers, booking portals, fleets and agents The flow of mail among the four parties: customers and fleets send it to the agent; the agent and the booking portal exchange bookings and provisioning; the agent sends manifests and VGMs to customers. Email interaction (four-party role) With the intelligent agent as the hub: receiving mail classification → project merging → freezing outgoing Agent cluster IMAP · Category · Project Warehouse · Freeze client booking gate fleet Entrustment and entrustment Manifest·VGM Booking application Provisioning postback Box seal number list

Core mechanisms

  • Run and trace: every production task carries a trace_id; tool calls, Room messages, HITL decisions and exports are all linkable and replayable.
  • Auditor and HITL double gate: HITL decides whether a tool or outbound action may execute; the Auditor reviews stage Evidence Packs—outbound sends are released only after both checks.
  • Skill/Tool Governance: Skill is injected before LLM call; Tool is authorized by role and can trigger HITL with risk tag; configuration release revision is bound to running Run.
  • Multi-tenancy and mailbox isolation: WorkRoot data plane isolation; customer/booking port/fleet binning and type identification drive sub-process (consistent with mail_monitor implementation).

Key indicators (example of acceptance criteria)

Session replayTool sequence and timeline indexable retrieval (typical deployment < 400 ms level)
Freeze/GateAttachments before outgoingSHA-256Consistent with frozen copies; HITL decisions are consistent withtool_call_idBindable instructions
mandatory roleThere is only one manager and one auditor each in the published configuration (release verification)
OPC UA (onsite)Configurable subscription and read-write cycles, and versioned mapping tables

Feature list and specifications

abilityillustrate
Console (standalone deployment)account,LLM,mailIMAP/SMTP, booking hatch mailbox, Agent start and stop, etc. are provided by the freight/OPC operating environment and are not within the scope of this official website warehouse.
Operation and maintenance interventionManual takeover, session suspension, single-step replay
open interfaceinternallyRESTDocuments are released with versions, and sample requests can be imported.Postmangather
deployLinux cluster /K8s;Message and vector libraries can be privatized

Data and security

Sensitive routes and credentials reside in customer-controlled key management; progress/streaming output never echoes key plaintext; audit exports contain no private keys. The outbound mail queue runs as an independent process, isolated from the generation service, and outbound actions are deduplicated with idempotency keys so the same content is never sent twice.

View freight forwarding agents in smart logistics solutions white paper Book a demo