Architecture
How TauGrid connects repository intent to Kubernetes execution
TauGrid is a CLI, renderer, and local observer. Kueue, KubeRay, and the Kubernetes scheduler continue to own quota admission, Ray orchestration, and pod scheduling.
| Layer | Responsibility |
|---|---|
| Research repository | Entrypoint, image, dependencies, resource intent, data, and outputs |
| TauGrid | Resolve, validate, render, submit, observe, and preserve workflow evidence |
| Workspace/platform | Cluster access, namespace, queue, priority, output root, identity, and shared policy |
| Kueue | Quota reservation, admission, priority, and preemption |
| Kubernetes/KubeRay | Pod scheduling and Job/Ray lifecycle |
| Project process | Training, evaluation, inference, and model-specific behavior |
Code boundaries
cli/cmd: thin Cobra command wiring for thetaubinary.cli/internal: reusable capability packages behindtau.core: the shared library module both binaries link.portal: a separate module and binary,taugrid-portal, that hosts experiment tracking (Stellar) and the observability portal.sdk/python: optional Python authoring APIs that delegate execution to the Go CLI.controllers/tau-core: the separately deployed controller. One manager runs three reconcilers –TauCluster,TauWorkspace, andTauQuotaRequest.
The visual architecture guide maps the main packages and extension points.