System Design

Event-driven architecture

A central orchestrator coordinates specialized agents communicating through typed events with parent-event lineage and explicit human escalation paths. 

flowchart LR
  O[Event Orchestrator]
  S[Scheduling Agent]
  V[Voice Coverage Agent]
  P[Payroll Agent]
  R[Reporting Agent]
  C[Compliance Agent]
  B[Billing/CRM Agent]
  H[Human Escalation]

  O --> S
  O --> V
  O --> P
  O --> R
  O --> C
  O --> B
  C --> H
  V --> H
  S --> O
  V --> O
  P --> O
  R --> O
  B --> O

Multi-agent domain coverage

Architecture comparison across six operational domains defined in the manuscript.

ASBOS Multi-Agent
Monolithic Agent
Rule-Based

Scheduling

Orchestration

Shift management, conflict detection, and replacement ranking.

Voice Coverage

Communication

Sequential outreach to ranked replacement guards with acceptance scoring.

Compliance Filtering

Safety

Credential checks and auditable rejection before any assignment.

Payroll Integration

Operations

Verified schedule changes converted to payroll-ready events.

Report Generation

Auditability

Incident summaries and client reports with event provenance.

Billing & CRM

Revenue

Verified service delivery linked to client billing and notifications.

Core pattern

ASBOS models a security company as an event-driven system of specialized agents. Each agent owns a bounded operational domain and communicates through typed events rather than direct hidden state mutation.

The central idea is not simply to add a chatbot to an existing application, but to represent the operational lifecycle as typed events processed by specialized agents with bounded responsibility and explicit escalation thresholds.

Event Orchestrator

Routes typed events between agents, maintains parent-event lineage, and triggers escalation when thresholds are exceeded.

JSON Schemas

Five typed event schemas validate clock events, coverage gaps, confirmations, credential expiry, and human escalation.

Human Escalation

Compliance and voice agents route to human escalation when no eligible guards remain or no candidate accepts coverage.

Revised research question

Can a security-specific, event-driven multi-agent layer coordinate workforce functions autonomously, preserve auditability, escalate risk appropriately, and demonstrate better outcomes in a controlled field study?

Integrated platforms such as Trackforce, Belfry, and Celayix already automate many individual and connected workflows. ASBOS is evaluated as an auditable orchestration layer with explicit human control — not as a claim that integrated software does not exist.

View agents Baseline comparison

Synthetic simulator benchmark

Scaffold results from 1,000 synthetic scenarios — not field pilot evidence.