evidencectl check command reference
Check a normalized project and, when selected, deployment closure, or one tooling file, offline.
Contract status
Section titled “Contract status”This page is generated from the public Clap command tree for Registry Stack source version 0.45.0 and catalog SHA-256 18546dbdf436972522108829ab0f8c804142a7474cfe3841e0b8ff10e061c842. Hidden implementation commands are omitted.
evidencectl check [OPTIONS] <PROJECT|--file <FILE>>Constraints
Section titled “Constraints”| Condition | Requirement |
|---|---|
| Command invocation | Exactly one of [PROJECT], --file <FILE> is required. |
--production is present | --target <TARGET> is required. |
| Command invocation | --file <FILE> and --production cannot be used together. |
| Command invocation | --file <FILE> and --target <TARGET> cannot be used together. |
| Command invocation | --file <FILE> and [PROJECT] cannot be used together. |
Arguments
Section titled “Arguments”| Argument | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
[PROJECT] | No | n/a | n/a | n/a | Editable Evidence project directory. Required unless —file is given |
Options
Section titled “Options”| Option | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
--file <FILE> | No | n/a | n/a | n/a | Check one tooling file on its own, offline: a client profile, reviewed contracts, development state, a source-import baseline or journal, a source resolution file, or a source export manifest |
--target <TARGET> | No | n/a | n/a | n/a | Explicit deployment target whose governance and runtime structure are checked |
--production | No | n/a | n/a | n/a | Require a production or evidence-grade target and complete deployment closure. Requires —target |
--deny-warnings | No | n/a | n/a | n/a | Exit 1 when a warning is reported |
--format <FORMAT> | No | human | human, json, junit | n/a | Emit the selected command’s report in this format. junit is accepted only by test and fixtures run |
-h, --help | No | n/a | n/a | n/a | Print help |
Generation contract
Section titled “Generation contract”After changing a public command, argument, option, default, environment binding, or help description, run cargo run --locked -p registry-cli-docs -- --write, commit crates/registry-cli-docs/catalog.json, then run npm run generate from docs/site.