Published Updated

nomue verifier Release 1 candidate is available on npm

The public @licklider/nomue-verifier package provides a direct local command for checking supported nomue Release 1 Records.

What is available

@licklider/nomue-verifier is publicly available on npm at version 0.2.1-rc.1. It exposes the nomue command for checking a local Record under the exact nomue Protocol Release 1 support target.

The package turns the public verifier from a source checkout into a direct tool path: install the command globally, or invoke the same package through npx when a global install is not wanted. Source and release evidence remain available in the public GitHub repository.

September 18 update: release candidate 0.2.1-rc.1preserves small Student-t probability differences at one degree of freedom and is available through npm's rc channel. The commands below pin the exact corrected version. See the implementation note for the numerical failure, repair boundary, and regression evidence.

Install and run

npm install --global @licklider/nomue-verifier@0.2.1-rc.1
nomue verify ./record.json --format json

Or run the package without installing a global command:

npx --yes @licklider/nomue-verifier@0.2.1-rc.1 verify ./record.json --format json

Replace ./record.json with the path to a conforming nomue Record and inspect the returned JSON report for the individual scoped outcomes.

Tested package path

The package path has passed CI on Linux, macOS, and Windows with Node.js 20 and 22. Release checks exercise global installation, nomue verify, and the npm-exec-equivalent npx path rather than testing only the repository's internal source layout.

Local verification boundary

npm must first obtain the package and its dependencies. After installation, Record verification runs on the local machine and does not call a nomue server. The verifier also does not fetch Record-supplied URIs, load remote schemas, or execute Record-supplied code.

This makes the public package an independently runnable verification surface. It is not an announcement of a hosted nomue API or remote HTTP MCP endpoint. A separate local stdio adapter is now available as @licklider/nomue-verifier-mcp@0.2.0-rc.1.

Release status and exact scope

npm's rc dist-tag currently points to 0.2.1-rc.1. The package is a release candidate, not a stable release. The unqualified npm latest tag remains on the preceding release candidate, so the documented commands use an exact version.

The sole Release 1 bundle supported by this package is urn:nomue:bundle:itgc-guarantee:0.2.1-draft.1. It covers independent two-group continuous outcomes under the two-sided Welch two-sample t procedure. Other procedures and nearby bundle versions are not implied by installation or by the npm dist-tag.

A clean report means that the named checks passed under that exact scope. It does not establish that the source data or researcher declarations are true, that the study is scientifically valid overall, or that a scientific conclusion is true. See the nomue Protocol for the authoritative Record and verification semantics.