autonomy policy verify compare¶
Diff two bundle revisions over one seeded case stream and report changed verdicts
Synopsis¶
Generates one seeded case stream from --scenario and evaluates each case
through the runtime engine against BOTH bundles, so the only variable in a
changed verdict is the bundle. Reports both decision distributions, the number
of changed verdicts, per-transition counts (e.g. "ALLOW -> DENY"), and the
changed cases.
Deterministic: the same (bundles, scenario, seed) yields the same diff. Pair
with --fail-on-changed to assert a revision is behaviour-preserving in CI.
autonomy policy verify compare --scenario scenario.yaml v1.tar.gz v2.tar.gz
Usage¶
autonomy policy verify compare --scenario <scenario.yaml> <old-bundle> <new-bundle> [flags]
Options¶
--fail-on-changed exit nonzero if any verdict changed between the bundles
--format string output format: "terminal" or "json" (JSON is the default when --output is set) (default "terminal")
--iterations int number of cases to sample (overrides the scenario's; 0 = use scenario)
--output string write the report to this file (default: stdout)
--scenario string path to the scenario YAML (input model) (required)
--seed int PRNG seed (overrides the scenario's seed)
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)
See also¶
autonomy policy verify— Verify a policy bundle against a declared input model (offline, read-only)