Unreleased documentation. These pages follow the main branch and can change before the next release. For supported guidance, use v0.46.0.
Evidence adopter tooling: keys, source authoring, fixture runs.
Contract status
Section titled “Contract status”This page is generated from the public Clap command tree for Registry Stack source version 0.46.1 and catalog SHA-256 61bebbb88fe15e4da92e2b0adbca0cd5b1a47b8eac38f4b91a15095011368a43. Hidden implementation commands are omitted.
evidencectl [OPTIONS] <COMMAND>Commands
Section titled “Commands”| Command | Description |
|---|---|
api | Send one raw HTTP request to a configured or ready local Evidence service |
init | Create a new editable Evidence project |
types | Generate typed project outputs and Requirement URI names |
check | Check a normalized project and, when selected, deployment closure, or one tooling file, offline |
explain | Explain the authored inventory and optional target-owned governance |
test | Run the project’s synthetic Evidence fixtures |
package | Compile an editable project into a reviewed deployment candidate |
generate | Generate configuration documents for other tools from this product’s configuration |
access | Manage target access profiles and local caller clients |
keygen | Generate Registry Evidence deployment key material as owner-only files |
jwks | Assemble a public JWKS document from public JWK files |
jwk | Convert public key material into a public JWK |
fixtures | Drive the evidence binary across a project’s bundle fixtures |
doctor | Check one runtime configuration and its startup dependencies |
artifact | Inspect deployment artifact custody |
dev | Run the private local issuer and Registry Evidence pair |
oid4vci | Operate the optional Evidence wallet-delivery service |
audit | Inspect stopped local audit history |
connection | Manage named Evidence API connections |
client | Configure progressive relying-party clients and fetch contract candidates |
source | Work with a project’s sources, starting from their own API documents |
target | Create and inspect complete deployment targets |
request | Prepare a closed request for the active local project |
verify | Verify one retained Registry Evidence response offline |
tooling | Advanced: editor and tooling integration surfaces |
runtime | Run the matching Evidence runtime with unchanged arguments and streams; use runtime -- --help for its native command tree |
Options
Section titled “Options”| Option | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
--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 |
-V, --version | No | n/a | n/a | n/a | Print version |
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.
Cookies on Registry Stack
We use optional cookies to understand how you use the main Registry Stack website and this documentation. If you contact us, we may link this activity to your enquiry. You can change your choice at any time. Read the privacy policy.
Your browser asks sites not to track you, so optional tracking stays off.
We could not use or save that choice. Optional tracking remains off.