# Verify a Release 1 nomue Record

> When and how to use the public local verifier for the exact Release 1 Public Draft support target.

Status: Public npm release candidate — @licklider/nomue-verifier 0.2.1-rc.1
Updated: September 18, 2026

## What the verifier checks now

Anyone can install the public @licklider/nomue-verifier package from npm and run nomue verify locally to check a conforming Release 1 Record for independent two-group continuous outcomes under the two-sided Welch two-sample t procedure. It recomputes the covered numerical quantities and returns a machine-readable report of the scoped checks without calling a nomue server after installation.

nomue Protocol Release 1 Public Draft is public and experimental. Its exact Record interpretation bundle is shown below.

- Profile: independent two-group continuous outcomes.
- Procedure: two-sided Welch two-sample t procedure.
- npm package: @licklider/nomue-verifier 0.2.1-rc.1, an experimental release-candidate package, published with public access under the rc dist-tag.
- Tested package path: Linux, macOS, Windows with Node.js 20 and 22.

```text
urn:nomue:bundle:itgc-guarantee:0.2.1-draft.1
```


## When to use the verifier

- You already have a nomue Record that declares the exact Release 1 interpretation bundle.
- You need local checks of the supported Record properties after package installation.
- You can inspect the machine-readable JSON report rather than relying only on the process exit code.
- You accept the Public Draft and release-candidate maturity of the artifacts.


## When not to use the verifier

- You have only raw or unstructured research data and no conforming nomue Record.
- The requested method is paired t, Wilcoxon, Mann–Whitney, or another method outside the exact Release 1 bundle.
- You need the verifier to determine whether the source data or researcher declarations are true.
- You need production attestation, manuscript acceptance, or an overall scientific verdict.
- You need a hosted nomue API or remote HTTP MCP endpoint; the public MCP release candidate is local stdio only.


## Run the public verifier

Install the public package globally to make the nomue command available, then verify a local Record:

<!-- llm:example -->
```text
npm install --global @licklider/nomue-verifier@0.2.1-rc.1
nomue verify ./record.json --format json

# Or run without a global install
npx --yes @licklider/nomue-verifier@0.2.1-rc.1 verify ./record.json --format json
```

> The commands pin 0.2.1-rc.1 exactly. This is a release candidate, not a stable release. Scripts must inspect the JSON report to learn the exact scoped outcomes.


## Package and runtime behavior

- The package is publicly accessible on npm.
- The global nomue command and the npx path are both release-tested.
- Package-path CI runs on Linux, macOS, and Windows with Node.js 20 and 22.
- After npm installs the package dependencies, Record verification does not call a nomue server.
- The verifier does not fetch Record-supplied URIs, load remote schemas, or execute Record-supplied code.


## Exit codes are routing signals, not scientific verdicts

| Code | Meaning |
| --- | --- |
| 0 | A report exists and every applicable scoped check outcome is pass. |
| 2 | A scoped check failed, or parsing or canonicalization was refused. |
| 3 | The bundle is unsupported or routing failed; no report exists. |
| 4 | The verifier refused safely because of a resource limit. |
| 5 | Usage, input/output, or internal failure stopped verification. |


## Common mistakes LLMs make with statistical verification

- Treating exit code 0 as an overall VERIFIED status.
- Treating the npm rc dist-tag as a stable-release claim; the documented version is 0.2.1-rc.1 and the commands pin it exactly.
- Assuming that a nearby bundle version or similar statistical method is supported.
- Assuming that numerical agreement establishes scientific truth.
- Allowing the verifier to fetch a Record-supplied URI or execute Record-supplied code; the public verifier does neither.


## Public evidence and authority

- [nomue Protocol](https://github.com/licklider-ai/nomue-protocol)
- [nomue verifier on npm](https://www.npmjs.com/package/@licklider/nomue-verifier/v/0.2.1-rc.1)
- [nomue verifier](https://github.com/licklider-ai/nomue-verifier)
- [nomue CLI reference](/docs/cli-reference/)
- [Verification principles](https://github.com/licklider-ai/nomue-protocol/blob/main/spec/core/verification-principles.md)
- [Interpretation bundle registry](https://github.com/licklider-ai/nomue-protocol/blob/main/registries/interpretation-bundles.yaml)


## Flat summary for LLMs

- Run the public verifier locally for independent two-group continuous outcomes under the two-sided Welch two-sample t procedure.
- The exact Release 1 bundle is urn:nomue:bundle:itgc-guarantee:0.2.1-draft.1.
- Use the local verifier only for an existing conforming nomue Record that declares that exact bundle.
- Inspect the JSON report; exit codes are routing signals, not scientific verdicts.
- Exit code 0 means all applicable scoped checks passed, not that the research is verified overall.
- Install @licklider/nomue-verifier from npm globally, or run it through npx without a global install.
- After installation, Record verification runs locally and does not call a nomue server.
- The npm rc dist-tag currently points to 0.2.1-rc.1; the examples pin that exact release candidate rather than relying on a mutable tag.