Skip to content
Registry StackDocsDevelopment (unreleased)

evidencectl target new command reference

View as Markdown

Create target files from explicit settings or a project-local baseline.

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

evidencectl target new [OPTIONS] <DIRECTORY>
ConditionRequirement
--project <PROJECT> is present--local is required.
ArgumentAlways requiredDefaultValuesEnvironmentDescription
<DIRECTORY>Yesn/an/an/aNew target directory to create
OptionAlways requiredDefaultValuesEnvironmentDescription
--settings <SETTINGS>Non/an/an/aClosed settings document with native governance, runtime, and public keys. This command checks target-file shape, logical secret references, and public-key identity. Project-specific bundle and runtime semantics are checked by target explain, fixtures run --target, build --target, and doctor.
--project <PROJECT>Non/an/an/aEvidence project directory; defaults to the current directory with —local. This command needs an editable project with local signing keys when using —local. Its paths fill only omitted local filesystem settings.
--localNon/an/an/aUse project-local development paths; requires local assurance governance
--signing-public-key <SIGNING_PUBLIC_KEY>Non/an/an/aPublic signing JWK whose RFC 7638 thumbprint names activePublicJwkFile
--format <output_format>Nohumanhuman, jsonn/aSelect human-readable or machine-readable output
-h, --helpNon/an/an/aPrint help (see a summary with ‘-h’)

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