Skip to main content
Do not ship a policy that has not cleared this checklist. The gates below exist because each one has caught a real production-blocking issue at least once.

​
Preconditions

  • Zenoh control plane reachable for your deployment topology.
  • Robot config selected and safety profile defined.
  • Dataset collected with the same robot contract version.

​
Required gates

1

Collect

A collect run exists and the dataset inputs are persisted under .rfx/runs/.
2

Validate

A validate report passes — timestamp, alignment, schema, and missing data checks all green.
3

Train

train produced a policy artifact manifest with compatibility metadata.
4

Eval

An eval report passes for the same artifact.
5

Shadow (recommended)

A shadow report passes. Optional, but recommended for any deploy that touches hardware.
6

Deploy preflight

rfx deploy preflight allowed the release.

​
Commands

rfx runs show surfaces the run record, including lineage metadata (inputs, outputs, artifact manifest, robot config hash) written by each workflow stage.

​
Blockers

Deploy must be blocked when any of the following is true:
  • Artifact manifest missing or schema incompatible
  • No successful eval report for the artifact
  • Shadow is required but no passing shadow report exists
  • Robot config hash mismatch
  • Safety profile mismatch

​
Incident readiness

  • Keep the run_id for rollback and audits.
  • Verify .rfx/runs/, .rfx/reports/, and .rfx/artifacts/ are persisted.
  • Use rfx runs show <run_id> to inspect exact replay prerequisites (inputs, config, artifact lineage).