BPM PROCESS MODEL
governance · audit · exception routing · KPIs · task assignment
PATTERN 1 — AGENT AS WORKER
AGENT
takes the task entirely
NO FORM
OUTPUT + AUDIT LOG
exception routing returns to model
HUMAN ROLE
Supervises throughput
via control tower / dashboard
intervenes on exceptions only
oversight
Design effort shifts from task form
to dashboards, control towers, handoff surfaces
PATTERN 2 — AI-INSIDE
TASK FORM ✓ PERSISTS
HUMAN
AUTHORS JUDGMENT
irreplaceable
AI CO-WORKER
· instance history
· policy version
· peer-task state
· semantic lineage
· external context
ABSORBS CORRELATION
OUTPUT + AUDIT LOG
AOP ASPECT SUBSTRATE
goal context · preference weights · policy version · prior-case outcomes
injected as aspects — AI brings the world to the form
HUMAN STAYS IN THE SEAT
human's intellect = binding constraint, not bottleneck
Both patterns sit inside the same BPM process frame.
The process model assigns, governs, and routes exceptions. Neither pattern changes any layer above the worker.