The verdict
Each governed command measures the artifact locally, sends the raw metrics to the Cadenza API, and the API returns one of three verdicts:Verdicts are computed server-side. The client only measures — it never
decides. That’s why the governed commands (
lora eval, lora finetune --gate,
residual train/eval/bench, distill eval, vla grd/eval) require
sign-in: the API needs to authenticate the run and
attribute the baseline to your account.What gets scored
The scorecard dimensions depend on the artifact, but the shape is the same — a mix of fidelity, safety, coverage, stability, and regression:Promotion, rollback & baselines
Governance is stateful. Each project keeps a promoted baseline per artifact kind. When a new artifact earnsDEPLOY, it replaces the baseline and the old one
is snapshotted. When a candidate earns BLOCK, the gate restores the previous
baseline automatically — so a bad run can never leave you worse off than before.
--gate(onenv lora finetune) runs the scorecard inline and promotes or rolls back automatically as part of the training command.--promote(on theevalcommands) deploys the candidate only if it earnsDEPLOY; aBLOCKis refused and rolled back.
Steering the next round
For the closed-loop stages (env residual train, env vla grd), the API does
more than judge — it steers. Each round it returns the hyperparameters and
dials for the next round (the residual’s PPO schedule; GRD’s λ / RL-budget /
change-cap), so the loop converges toward a deployable artifact under the gate
rather than just optimizing a raw objective.