domains / families / devops / paidf-orchestration-write-dag

paidf-orchestration-write-dag

separate

Use when a user describes a custom PAIDF Orchestration pipeline — a specific ordered combination of stages such as augmentation only, auto-labeling only, detection+captioning only, or image attribute augmentation without full auto-labeling — that no existing DAG in airflow/dags/workflows/ covers, and asks for a new Kubernetes DAG. Also use to check that a generated or existing DAG's model/container/prompt choices match an external spec document (e.g. a PAIDF `launchable.md`).

When to use

• custom PAIDF Orchestration pipeline
• specific ordered combination of stages
• augmentation only
• auto-labeling only
• detection+captioning only
• image attribute augmentation without full auto-labeling
• new Kubernetes DAG
• check DAG model/container/prompt choices against external spec

When not to use

• NVCF backend
• OSMO backend
• inventing new task-group logic
• permanent artifacts in run-skill DAG-ID tables

Skill page

Source