Process Event Model

Executive Summary

The Process Event Model defines how Business Processes are triggered, advanced, monitored, escalated, and completed through events. Events allow AIOS to coordinate work without taking ownership of Domain facts.

Why This Exists

Procurement work is deadline-driven and state-driven. Tender matches, document expiries, approval requests, bid tasks, contract milestones, supplier responses, funding statuses, learning gaps, and billing events must trigger repeatable operating responses.

Owner

The owner is the Chief Product Officer and Enterprise Architect. Domains own Domain events. Practices own process events and SOP responses. AIOS orchestrates event-driven execution.

Business Value

Event-driven processes reduce missed work, improve response time, enable automation, and make execution traceable.

Event Flow

flowchart LR
    Source[Domain or Process Source]
    Event[Event]
    AIOS[AIOS Event Orchestration]
    Policy[Process Event Policy]
    Process[Business Process]
    Professional[Digital Professional]
    Approval[Approval Gate]
    Outcome[Process Outcome]
    Audit[Audit Trail]

    Source --> Event
    Event --> AIOS
    AIOS --> Policy
    Policy --> Process
    Process --> Professional
    Process --> Approval
    Professional --> Outcome
    Approval --> Outcome
    Outcome --> Audit

Event Types

Event Type	Description
Trigger event	Starts a process instance.
State event	Advances or changes a process state.
Deadline event	Indicates approaching or missed deadline.
Approval event	Requests, grants, rejects, or expires approval.
Exception event	Indicates process deviation or blocked work.
Completion event	Indicates process outcome has been reached.
Metric event	Captures KPI-relevant process data.
Memory event	Indicates potential organizational learning.

Standard Process Events

Event	Meaning
ProcessStarted	A process instance has begun.
ProcessTaskAssigned	A task has been assigned to a human or Digital Professional.
ProcessTaskCompleted	A task has been completed.
ProcessApprovalRequested	Human approval is required.
ProcessApprovalGranted	Approval was granted.
ProcessApprovalRejected	Approval was rejected.
ProcessExceptionRaised	Execution deviated from expected path.
ProcessEscalated	Work was escalated to Ari, a Practice owner, governance, or human approver.
ProcessCompleted	Process outcome was reached.
ProcessCancelled	Process was stopped before outcome.
ProcessFailed	Process could not complete.

Event Rules

• Events must be meaningful business signals.
• Events must include source, timestamp, tenant, correlation ID, and process instance ID where applicable.
• Process events must not duplicate Domain events.
• AIOS may react to events but must preserve source ownership.
• Events that trigger high-impact steps must route through approval gates.
• Event handling failures must be auditable and escalated when material.