Claims

Certified, or refused.

“I changed only auth.rs.” You can trust the sentence, or you can check it. The Claim Ledger checks it — against git, the build, the tests. Never against a model.

$ omnis-key claims verify --files-changed a.js --json

"code": "CLAIMS_EVALUATED"
"certified_count": 1
"any_refuted": false

Proved against the working tree. Not asserted.

The verifier states its own bound.

"kind_name": "files_changed"
"reason":     "compares git worktree+untracked
               (not ignored) against declared set;
               does not …"

Every certification carries the reason it was reachable — including what it does not cover. A verifier that declares its scope can be argued with. One that only says certified cannot.

Then the ones nobody can check.

⊘ REFUSED_NO_VERIFIER   "this is faster"
·  UNGROUNDED           "more idiomatic"

Speed was not measured, so it is not claimed. “Idiomatic” is not falsifiable, so it is not asserted. Two different findings, and the ledger keeps them apart.

Stage-3 verification never calls a model. A language model deciding whether a language model told the truth is not verification — it is the same claim, twice.