Coding Work Order Lifecycle

Coding Work Order Lifecycle A lifecycle diagram generated by Archify. 01 / CodingStatus rail 02 / Bounded correction + Holds and cancellation 03 / Outcomes AWAITING_APPROVAL · draft or correction · CodingStatus rail · human gate 01 AWAITING_APPROVAL draft or correction human gate READY · stage may dispatch · CodingStatus rail 02 READY stage may dispatch Attempt running · claim + lease + evidence · CodingStatus rail 03 Attempt running claim + lease + evidence AWAITING_ACCEPTANCE · validation passed · CodingStatus rail · human gate 04 AWAITING_ACCEPTANCE validation passed human gate SUCCEEDED · projection COMPLETED · CodingStatus rail · terminal 05 SUCCEEDED projection COMPLETED terminal Correction pending · within maxCorrections · Bounded correction · bounded Correction pending within maxCorrections bounded HELD · limit, changed input, UNKNOWN · Holds and cancellation · recoverable HELD limit, changed input, UNKNOWN recoverable CANCEL_PENDING · CLOSED after resolution · Holds and cancellation · request only CANCEL_PENDING CLOSED after resolution request only validation failed corrective task (reapproval if required) limit, changed input or UNKNOWN human resume cancel request (no kill) Legend start active state waiting decision terminal success failure / exit neutral

Five Statuses

  • • AWAITING_APPROVAL, READY, AWAITING_ACCEPTANCE, HELD and SUCCEEDED are the only CodingStatus values
  • • READY still requires control, ownership, approval, input and resource checks before dispatch

Pause and Correction

  • • controlPause blocks new admissions (projection SUSPENDED); evidence stays available for settlement
  • • A failed validation creates a bounded corrective task, reapproved when reapproveCorrections is set

Holds and Cancellation

  • • A restart advances the epoch; step() returns RECOVERY_REQUIRED until a human resumes
  • • UNKNOWN outcomes are never retried automatically