evidence evaluate command reference

Evaluate one bundle-owned fixture without source or credential access.

Contract status

This page is generated from the public Clap command tree for Registry Stack source version 0.38.0 and catalog SHA-256 cd13c658f65af295f9df3c6db86dc045ac06e9e040afc1f5f5b27c3184ab653d. Hidden implementation commands are omitted.

Usage

evidence evaluate [OPTIONS] --runtime-config <FILE> --fixture <FIXTURE>

Constraints

Condition	Requirement
--explain-format <EXPLAIN_FORMAT> is present	--explain is required.

Options

Option	Always required	Default	Values	Environment	Description
--runtime-config <FILE>	Yes	n/a	n/a	n/a	The closed operator runtime file that binds the governed bundle
--fixture <FIXTURE>	Yes	n/a	n/a	n/a	Bundle-relative fixture path referenced by exactly one requirement
--case <CASE>	No	n/a	n/a	n/a	Evaluate only the case with this exact identifier
--explain	No	n/a	n/a	n/a	Print the per-stage trace of what each case actually did. A failure names the contract that broke and nothing else, which says that a case failed but never why. The trace says how far each case got, what shape the response and facts had, and which declared concept the output gate was checking. It reports shapes, counts, and identifiers, never document values, and it never changes an outcome, an exit code, or a message.
--explain-format <EXPLAIN_FORMAT>	No	n/a	text, json	n/a	Render the --explain trace for a machine reader instead of a person. The JSON form is the whole of standard output, so the summary line’s verdict and evaluated-case count move inside the document rather than trailing it
-h, --help	No	n/a	n/a	n/a	Print help (see a summary with ‘-h’)

Generation contract

Run npm run generate from docs/site after changing a public command, argument, option, default, environment binding, or help description.