Jobs Escalate To Review

Summary

Jobs should not pause for a human. When a job reaches uncertainty that requires judgment, it should create review state and exit cleanly.

Problem

Batch and scheduled jobs are poor places for interactive decisions. They lack operator context, can hold locks too long, and make failures hard to resume.

Principle

Automated execution does the work it can prove, records what it cannot prove, and escalates to a UI/API-backed review surface.

Platform Shape

Job layout guidance keeps entrypoints thin. POA and precon job services create or advance cases, review tasks, issues, and processing tasks. The review surface then records the human decision that allows a later job or action to continue.

Source Evidence

• docs/reference/job-layout.md
• services/poa/jobs
• services/precon/jobs
• services/workflow/reviews

Related Reading

• docs/engineering/reference/thin-jobs-fat-services.md
• docs/engineering/concepts/workflow-resumption.md