Run and workload lifecycle
Independent transitions from repository resolution to useful progress
A TauGrid run crosses independent control planes:
- Resolution: TauGrid finds the project, workspace, and target.
- Rendering: TauGrid validates intent and builds a Job or RayJob.
- Admission: Kueue reserves quota and admits the workload.
- Scheduling: Kubernetes places pods on matching nodes and devices.
- Runtime: Ray or the Job controller starts the application.
- Progress: The model or data process advances and writes evidence.
- Completion: Results, checkpoints, metrics, and terminal state remain inspectable.
These states are not equivalent:
- Admitted does not mean scheduled.
- Scheduled does not mean the GPU is healthy.
- Running does not mean the model is progressing.
- Completed does not prove required artifacts were preserved.
Use the layered troubleshooting guide to find the first failed transition.