autonomy policy verify¶
Verify a policy bundle against a declared input model (offline, read-only)
Synopsis¶
Pre-deployment policy verification, using the SAME evaluation engine as the
runtime — a verdict here is the verdict the edge would produce for the same
input and bundle.
Modes:
run seeded Monte Carlo over a scenario's input model
scenario mine an empirical scenario from recorded telemetry (--from-wal)
replay re-evaluate exported failure fixtures
compare behavioural diff of two bundle revisions
cases run a curated suite of fixed (scene → expected) cases
Randomized verification increases coverage within a declared input model; it
does NOT prove correctness or safety.
Options inherited from parent commands¶
--require-signed-manifest Refuse to start if the SHA256SUMS release manifest or its cosign signature is missing/invalid (Tier 2 binary-integrity check; default: build-time compile-in via -ldflags -X, build-hardened artifacts=true, all others=false)
Subcommands¶
autonomy policy verify cases— Run fixed (scene → expected) cases, or replay recorded scenes (–from-wal) against a bundleautonomy policy verify compare— Diff two bundle revisions over one seeded case stream and report changed verdictsautonomy policy verify replay— Re-evaluate exported fixtures, or faithfully replay captured production decisions (–from-wal)autonomy policy verify run— Sample a scenario’s input model against a bundle and report the decision distributionautonomy policy verify scenario— Mine an empirical scenario.yaml from recorded scene-state telemetry (#1312)
See also¶
autonomy policy— Manage policy bundles