TauGrid object model
How repository, project, workspace, target, run, workload, and experiment relate
Full definitions for these terms live in the glossary. This page only explains how they relate and who owns what.
| Concept | Owns |
|---|---|
| Repository | Code and history in one Git worktree |
| Project | One or more targets and a workspace connection |
| Workspace | Destination policy: cluster, namespace, queue, priority, output root, identity |
| Target | One checked-in runnable config |
| Run | One execution plus its lifecycle handle |
| Workload | Rendered Job or RayJob execution intent |
| Service | Online RayService or Deployment lifecycle target |
| Experiment | A comparison set over runs, metrics, and artifacts |
The ownership split is deliberate:
- Projects own code, images, runtime dependencies, resource intent, datasets, and artifacts.
- Workspaces own destination policy and shared platform defaults; projects keep owning their own code and workload shape. The TauWorkspace Kubernetes resource backs this policy, while platform teams provision the underlying Azure resources.
- TauGrid owns deterministic resolution and lifecycle handoff.