Skip to main content
The catalog is two artifacts that stay in sync:
  • src/worldflux/curated.py — the Python source the CLI reads at worldflux init --recipe <id> and worldflux curated * time.
  • web/lib/catalog-data.ts — the TypeScript copy the dashboard’s Catalog tab renders.
Both files describe the same adapter set. Keep them aligned when changing the catalog; the Python source is the CLI source of truth and the TS copy is what the dashboard renders.

Entry shape

Field notes:

What ships today

Templates and deploy targets

Serving templates live under src/worldflux/templates/ for the adapters that support BYOK deploy or dry-run demo flows:
  • cosmos_predict25/
  • openpi/
  • openvla_libero_pro/
  • vjepa2_vitl/
These templates power BYOK deploy/run-remote flows:
For local installed adapters, use worldflux use <id> followed by the env tree:

Browsing

inspect prints the full record, including known issues. The dashboard’s Catalog tab renders the same data with search and runtime/tier filters.

Adding an adapter

1

Add to curated.py

Append a CuratedAdapter(...) entry to src/worldflux/curated_registry.py through the src/worldflux/curated.py compatibility facade. Fill every field; the dashboard treats null as “unknown” and renders accordingly.
2

Update the dashboard copy

Mirror the user-facing fields in web/lib/catalog-data.ts so the Catalog tab stays in sync with the CLI source.
3

Run it once

The cutoff for tier: active is one passing CI run plus a documented benchmark id. Until then, set tier: "historical" and evalBenchId: null.
4

Drop a template (optional)

If the adapter has a non-trivial run.py, add it under src/worldflux/templates/<id>/. The init command picks it up automatically.