Skip to main content
Cadenza gives you three complementary ways to improve a project after you’ve run it.

env finetune: export VLA training data

Convert a run log into (prompt, action, reward) records for your own vision-language-action SFT or offline-RL pipeline.
Prompts are rendered with the project’s vla_finetune.prompt_template (see the schema).

env train: rewrite the system prompt

Runs a Groq LLM-as-Judge over the project’s cached runs and rewrites the project’s SYSTEM_PROMPT to fix the failure modes it finds.
Requires a GROQ_API_KEY (Configuration). No key, no training.

env lora: fine-tune and govern the action head

Fine-tunes the cadenza-lab LoRA action head for a project (on the project’s own base/VLA if it ships a lora_encoder.py), then governs it with a scorecard. Once trained, drive a mission with it via env run --policy lora.
Requires the lora extra: pip install -e ".[lora]" (installs torch).

Example

Governance scorecard

env lora eval (and finetune --gate) score the adapter on fidelity, safety, coverage, stability, and regression, producing a verdict with next-step guidance: The verdict is computed server-side by the Cadenza API, which is why env lora eval/finetune --gate require sign-in. The full gate model — shared by residual, distillation, and VLA — is in Governance & scorecards.

Beyond the action head

LoRA fine-tuning adapts the action head inside a mission. Two related stages go further:

Residual RL & distillation

Learn a tiny residual on the frozen base, then distill it into a base-free student that runs onboard.

VLA mode & GRD

Adapt a standalone VLA’s LoRA adapter with one governed fine-tune + RL loop — no env.json, no prompts.