DAG Primitives

Summary

DAGs compose jobs and child DAGs into ordered execution graphs with persisted run and task state.

Problem

Some workflows require more than one job. If ordering, dependency, and shared parameter flow live in ad hoc code, operators cannot inspect or repair the workflow consistently.

Principle

Use DAGs for execution ordering, not business logic. Jobs and services still own behavior; DAGs own graph structure and run progression.

Platform Shape

The DAG docs describe definitions, runs, task runs, schedules, dynamic barriers, and Cloud Tasks-backed advancement. API surfaces live under app/api/dags, runtime orchestration under services/execution/dags, and durable state under services/ops/execution_state/dags.

Source Evidence

• docs/domains/dags.md
• services/execution/dags
• services/ops/execution_state/dags
• app/api/dags

Related Reading

• docs/engineering/architecture/scheduler-model.md
• docs/engineering/concepts/job-run-state.md