nomue (earlier version) · Archived
nomue documentation (earlier version)
These guides documented nomue, Licklider’s earlier product: its public verifier, its local MCP release candidate, when an agent should call it, and how to interpret the returned evidence. nomue’s verification capabilities are now part of SciGround.
Archived reference: these guides apply only to the named nomue releases and packages and do not describe SciGround. For current verification, see the SciGround documentation or connect SciGround.
Released (September 2026)
Local verification of Release 1 Records
The public @licklider/nomue-verifier package (0.2.1-rc.1) let anyone 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 recomputed the covered numerical quantities and returned a machine-readable report of the scoped checks without calling a nomue server after installation.
Release 1 published source code together with public fixtures, a signed source archive, checksums, a snapshot manifest, detached signatures, and the public release key.
Guides by task
Run
Verifying a nomue Record
@licklider/nomue-verifier 0.2.1-rc.1 was published on npm for the independent two-group continuous outcomes profile under the two-sided Welch two-sample t procedure.
Connect
The local MCP release candidate
@licklider/nomue-verifier-mcp@0.2.0-rc.1 was published on npm and in the official MCP Registry. It exposed only verify_nomue_record over local stdio, limited to Release 1 Welch Record verification, with no account, API key, or Licklider-hosted service.
Call
When an agent should verify
When-to-use rules, stop triggers, decision vocabulary, and machine-readable examples. A statistical method name is not a verification contract. A useful guarantee also depends on the comparison family, error criterion, assumptions, sidedness, balance conditions, and exact procedure variant.
Interpret
Understanding the returned result
Pass, fail, clarification, refusal, unsupported scope, and operational failure were kept distinct.
Limited Release 1: Approved recipients could submit data and required scientific declarations for a supported Welch calculation, or a claimed result with structured evidence for checking, through authenticated MCP and HTTP. Public self-registration was not offered, and hosted results were not emitted as public Records for local replay. Limited-release announcement
Protocol proposals (Releases 2–5): A paired-t candidate (Release 2) and public discussions on independent groups and multiple comparisons (Release 3, earliest decision date October 9, 2026), two-factor experiments (Release 4, October 9, 2026, and October 18, 2026 for its amendment) and shared design and timing evidence (Release 5, October 17, 2026). No decision has been published, and the public nomue Protocol repository records no change after September 28, 2026. Release 1 is unchanged. nomue’s verification work now continues in SciGround.
Release 3 scope · Release 4 scope · Release 5 scope · Archived nomue roadmap
Documentation
What a verification call is (nomue, earlier version)
Archived nomue guide: the shared model nomue used for asking a separate capability to check one bounded part of AI-assisted research.
Archived nomue guide (earlier version) — conceptual guide for selecting a verification capability
Verify a Release 1 nomue Record (earlier version)
Archived nomue guide: when and how the public local verifier was used for the exact Release 1 Public Draft support target.
Archived (earlier version) — public npm release candidate @licklider/nomue-verifier 0.2.1-rc.1
Use nomue Record verification over MCP (earlier version)
Archived nomue guide: the public local stdio server, when its method-neutral Record tool applied, and how a Release 1 Welch result was replayed with the independent verifier.
Archived (earlier version) — public local MCP release candidate @licklider/nomue-verifier-mcp 0.2.0-rc.1
nomue CLI reference (earlier version)
Archived nomue reference: the exact public command surface shipped by @licklider/nomue-verifier 0.2.1-rc.1, including its help and version behavior.
Archived CLI reference (earlier version) — release candidate 0.2.1-rc.1
Decision vocabulary (nomue, earlier version)
Archived nomue guide: how nomue kept execution, clarification, unsupported scope, refusal, failed checks, and unasserted scientific validity separate.
Archived explanatory vocabulary (earlier version) — upstream Protocol semantics remain authoritative
nomue examples for agents and implementers (earlier version)
Archived nomue examples: verifier commands and selection examples showing execute, clarify, unsupported, and bounded interpretation behavior.
Archived examples (earlier version) — executable examples used the Release 1 verifier fixtures
nomue capability and boundaries (earlier version)
Archived nomue capability map: what nomue released, what it planned, and how to interpret a successful result, as last updated on September 17, 2026.
Archived capability map (earlier version) — last updated September 17, 2026
For agents
Every nomue documentation page has a clean Markdown version, and normalized examples are available as JSON. They describe the earlier version only; use the SciGround documentation for current capabilities.