POA Workflow State Machine
Summary
POA is a repairable procurement acknowledgement workflow. Its state machine is the reason document interpretation does not directly become external sync.
Reader Question
Where does POA pause between source intake, interpretation, matching, validation, operator repair, command dispatch, and external sync?
State Machine
Source Captured records the document or source reference. Interpreted extracts structured evidence. Matched proposes operational context such as job, purchase order, invoice, packing slip, or confirmation. Validated applies POA policy before any external command becomes eligible.
When evidence is ambiguous, the workflow enters Needs Repair. Operators inspect artifacts, diagnostics, and candidate matches, then make actor-scoped corrections. Accepted state becomes Command Eligible, then Sync Pending, then Synced or Sync Failed.
The important transition is from automation to review. A mismatch is not a parser exception; it is a stateful issue. A provider failure is not hidden inside a job; it becomes sync state with retry and audit context.
Visual
The diagram highlights the validation gate before outbound commands and the repair loop around matching, validation, and sync.