The keys the verification plugin's skills read. Each is set per user through the plugin's
userConfig option of the same name and per repository in docs/conventions/verification.yaml,
validated by schemas/verification.schema.json. No
~/.claude file, .claude/ file or personal override sets them. /verification:setup apply writes the
repository file after validating it; /verification:setup check validates it.
| Key | Values | Default | Reader | Level rule |
|---|---|---|---|---|
proof_level |
path, live, strict |
path |
/verification:confirm (Stage 2 step 1) |
stricter wins (path < live < strict); the repository value is read from the default branch |
live_workers |
a whole number, at least 1 |
1 |
/verification:confirm (Stage 2 step 1) |
per user (userConfig.live_workers) and per repository (docs/conventions/verification.yaml); the later layer wins: repository file over user option over default; the repository value is read from the default branch (Resolving live_workers) |
verification, verification_skills.<skill> |
off, light, standard, strict |
light |
/verification:confirm (Independence of the verdict), through lib/read-verification.sh |
repository file only, read from the default branch; no user option; a skill entry beats the plugin value (verification level) |
path: a live run is required only when a changed file matches a runtime-affecting path in/verification:confirm.live: any change with a runnable surface is driven in the live app when the app can be launched. When it cannot be launched, the change gets the non-UI check from the check-to-change table inskills/confirm/context/outcome.md(read the stored value back, replay a saved input, run the real command), and the report says the app could not be launched.strict: the three proof boxes (unit, live, performance) inskills/confirm/context/outcome.md, filled per plan phase, or per pull request when the plan has no phases. Each box holds evidence or a reasoned not-applicable line that the fresh-context verifier checks.
/verification:confirm resolves the level once per run, before Stage 2, and never asks the user.
Every case below ends in a value, so a pipeline lane that calls the skill unattended gets the same
result as a person.
- Default:
path. - User option:
${user_config.proof_level}, rendered into the skill. A literal, unexpanded placeholder means unset. A value other thanpath,liveorstrictis named with the option, the key and the value, and the layer is dropped. - Repository file:
proof_levelindocs/conventions/verification.yamlas committed on origin's default branch, never the working tree or the branch under verification. Root rule first: when the repository root (CLAUDE_PROJECT_DIR, elsegit rev-parse --show-toplevel) is not inside a git working tree, or is$HOMEor an ancestor of it, skip this layer and say so. Otherwise take the default branch name fromgit ls-remote --symref origin HEAD(the part afterrefs/heads/on itsref:line) and accept it only when it holds letters, digits,.,_,/and-, has no leading-and no..; any other name skips the layer, and the report quotes the name as data. Then rungit fetch origin <default>, and from the plugin rootnode skills/setup/scripts/setup-apply.mjs --check --ref origin/<default> --root "<root>". Its first line names the commit read; the report carries that commit. When the fetch fails, the last fetched copy is read and the report says it may be stale. The reader's result:- exit 0 with
INFO ... absent, or exit 0 or 1 withPASS proof_level: (unset): the layer is unset. - exit 0 or 1 with
PASS proof_level: <level>: the layer sets that level. - On exit 1 beside either
PASS proof_levelline, theWARNlines name another key, such aslive_workers=0 is not a whole number of at least 1, and say nothing againstproof_level: the layer is unset or sets the printed level, never invalid forproof_level. - exit 1 with no
PASS proof_levelline: the committedproof_levelor the whole committed file is invalid. EachWARNline names the file, the key and the value (an unlisted word, a capitalized level, an empty value, a list, a key set twice, an unknown key set twice or holding a map or list, a parse error, a committed symlink). The layer is invalid forproof_level. Any other unknown key is one WARN beside the PASS lines, so a validproof_levelfloor in the same file still counts. - exit 2 (no
origin/<default>, a ref that does not resolve) or node not installed: the layer cannot be read; skip it and say why.
- exit 0 with
Which value wins. The stricter of the user option and the repository value wins, so either
layer can raise the level and neither can lower the other. A skipped or unset layer takes no part.
An invalid layer is named with its file or option, the key and the value, dropped, and counts as
absent; the other layer still applies, and with neither valid the key resolves path. So an invalid
repository value never lowers a valid stricter user value. An invalid value never stops the run.
A branch cannot lower the level. A change that adds or edits
docs/conventions/verification.yaml on its own branch does not change the level it is verified
at. When the working tree's copy, read with setup-apply.mjs --check (no --ref), sets a
different level from the default branch's copy, the report names both and says which one applied.
Report line. One line before Stage 2 names the level and the layer that supplied it, for example
proof_level: strict (docs/conventions/verification.yaml at origin/main, commit <sha>),
proof_level: live (userConfig; docs/conventions/verification.yaml at origin/main says path) or
proof_level: path (default). A dropped or skipped layer is named on the same line with its reason.
Older releases. A verification release from before this key has no reader for
docs/conventions/verification.yaml, so on that machine a repository's live or strict silently
weakens to the path rule. Upgrade every member before setting a repository level; the report line
lets a reviewer see a run that lacks it.
live_workers is how many workers share the live drive Stage 2 step 1 runs, split by feature-map
entry point. It decides only how many workers run that drive; proof_level still decides whether a
live drive is required. /verification:confirm resolves it once per run, beside proof_level, and
never asks the user.
- Default:
1, a single drive. - User option:
${user_config.live_workers}, rendered into the skill. A literal, unexpanded placeholder means unset. - Repository file:
live_workersindocs/conventions/verification.yaml, read from origin's default branch by the samesetup-apply.mjs --check --ref origin/<default>call, root rule and branch-name check that readproof_level(Resolution above). That call printsPASS live_workers: <n>,PASS live_workers: (unset), or aWARNnaming the key and value and noPASS live_workersline; the value it prints comes through the plugin'slib/parse-concern-value.shcopy. Exit 2, node missing or a skipped layer leaves this layer unread, and the report says why.
Why the default branch. The worker count starts processes and app instances on the host, so it
follows the policy the repository has merged, not the branch under verification, and the one
--check --ref call already made for proof_level reads both keys. A working-tree value takes
effect once it is merged.
Which value wins. The ordinary later-layer rule, not the stricter-wins rule of proof_level: the
repository value wins over the user option, which wins over the default. A value in either layer
that is not a whole number of at least 1 (0, 2.5, -1, a quoted "2", a word) is named with
its file or option, the key and the value, and that layer is dropped: a valid higher layer still
wins, otherwise the key resolves 1. A lower layer's value is never used in its place, so an
invalid repository value resolves 1 even when the user option is valid (ADR 0064 Decision 7). An
invalid value never stops the run, and an invalid live_workers never changes proof_level: the
reader still prints PASS proof_level for a valid committed level.
Report line. The worker line names the count and the layer that supplied it, for example
live_workers: 3 (docs/conventions/verification.yaml at origin/main, commit <sha>) or
live_workers: 1 (default), with any dropped layer and its reason.
Older releases. A verification release from before this key ignores it and runs one worker. That is not a floor: nothing weakens, and the report's worker line shows which count ran.