Published Updated

nomue Protocol Release 1 Public Draft is now available

The first public draft of the nomue Protocol is available with a machine-readable Record specification, local verification, public fixtures, and signed release artifacts.

What is available

nomue Protocol Release 1is now publicly available. It defines public structures and verification rules for nomue Records—machine-readable evidence objects that connect scientific-analysis declarations, analytical decisions, inputs, results, and other finalized evidence so that supported properties can be checked independently.

Release 1 includes the public specification, schemas, registries, conformance materials, a bundled reference verifier, and signed release artifacts. The separately packaged nomue verifieris also pinned to the published Release 1 identities.

View Release 1 on GitHubor run the nomue verifier.

What anyone can check

After its dependencies are installed, the verifier runs locally and does not need a Licklider server to verify a Record. For the exact Release 1 support target, it can check Record structure and content integrity, whether the declared research design falls inside the supported profile, whether the Welch calculation is computable, and whether stored Welch results match a fresh calculation under the registered rules.

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 verifier source repository also carries a valid public fixture and an intentionally mismatched fixture for inspecting both result paths.

Release 1 scope

Release 1 is an experimental Public Draft, not a Stable 1.0 compatibility promise. Its sole public Record interpretation support target is urn:nomue:bundle:itgc-guarantee:0.2.1-draft.1.

That target covers independent two-group continuous outcomes using the two-sided Welch two-sample t procedure, including the unstandardized arithmetic mean difference, standard error, and two-sided 95% Welch-Satterthwaite confidence interval. Other statistical procedures are outside the Release 1 public support boundary.

Signed release artifacts

The Release 1 pageincludes a separately attached signed source archive, release checksums, a Protocol snapshot manifest, detached signatures, and the public release key. These artifacts make the published release evidence independently inspectable.

GitHub’s automatically generated Source code archives are not the signed Release 1 source artifact. Signature verification should use the separately attached source-archive.tar.gz and its accompanying release files.

What this release does not establish

A passing verification result does not prove that:

  • the research project or its scientific conclusions are correct;
  • input data or researcher declarations are true;
  • cause-and-effect claims are justified;
  • a paper will be accepted for publication;
  • complete regulatory compliance has been established; or
  • methods outside the explicitly supported Release 1 procedure are valid.

The verifier reports results for explicit checks and scopes rather than returning a single overall VERIFIED label. This Layer 1 release also does not, by itself, mean that the nomue application has shipped Release 1-backed product support.