Event Model

ASBOS is modeled as an orchestration layer above existing systems of record. Each business event receives:

• Unique identifier
• Timestamp
• Source system or agent
• Confidence level
• Data classification
• Audit history

Example event types

The orchestration service may receive events such as:

• Shift created or updated
• Clock-in missed
• Credential expiring
• Report overdue
• Incident opened
• Invoice due

Design principles

• Agents do not directly overwrite authoritative payroll, licensing, or client records without policy checks.
• Agent actions are idempotent where possible so replayed events do not create duplicate shifts, invoices, or messages.
• A shared event schema supports interoperability without giving every agent unrestricted access to every dataset.
• Parent-event lineage supports traceability and failure analysis.

Simulator note

The prototype repository implements a subset of event types for a no-show coverage cascade using synthetic data. This scaffold supports protocol design and baseline comparison — not field evidence.