Documentation

Everything to build
on CAVS Hub.

Per-SDK guides, the one canonical API contract every client implements, authentication with service accounts, the architecture, and what's coming next. The full docs live in the repository's docs/ folder.

Reference

Deep docs in the repo.

DocumentWhat it covers
CONTRACT.mdThe canonical API: auth, endpoints, upload/download choreography, idempotency, telemetry, errors, cavs://.
docs/ARCHITECTURE.mdHow the SDKs relate to the Hub and the CLI; the content-addressed data plane.
docs/authentication.mdService accounts, cavs_sk_ keys, scopes, token resolution and security do's & don'ts.
docs/python.mdThe full Python guide (17-point structure).
docs/typescript.mdThe full TypeScript guide (17-point structure).
docs/github-action.mdThe full GitHub Action guide.
docs/ROADMAP.mdUpcoming SDKs and integrations.
Roadmap

What's next.

Two SDKs and a GitHub Action ship today. These build on the same canonical contract.

MLflow planned

mlflow-cavs — a custom artifact repository so mlflow.log_artifact writes to CAVS, mapping the MLflow run to a CAVS run.

Orchestrators planned

Kubeflow components (cavs-kfp) and an Airflow provider (apache-airflow-providers-cavs).

More SDKs planned

Go (cavs-go) and .NET (CAVS.SDK) — the latter powering the Unity and Unreal integrations.