# Examples for agents and implementers

> Runnable verifier examples and selection examples showing execute, clarify, unsupported, and bounded interpretation behavior.

Status: Public examples — executable examples use the Release 1 verifier fixtures
Updated: September 2, 2026

## Machine-readable examples

The normalized example set is available as JSON. Each entry identifies whether it is executable today or only demonstrates a call-selection boundary.

- [Examples JSON](/docs/examples.json)


## Example 1: verify a valid Release 1 Record

Use the public verifier because the input is already a conforming Record for the exact supported bundle.

<!-- llm:example -->
```text
npm exec -- nomue verify records/valid.json --format json
```

> Expected routing result: exit 0 and a JSON report with applicable scoped checks passing. Do not summarize this as “the research is verified.”


## Example 2: keep a declared-result mismatch as a failed check

<!-- llm:example -->
```text
npm exec -- nomue verify records/invalid-result-mismatch.json --format json
```

> Expected routing result: exit 2 and a JSON report containing the failed scoped check. The mismatch is not an overall scientific conclusion.


## Example 3: verify the same Record through local MCP

Configure @licklider/nomue-verifier-mcp@0.2.0-rc.1, then call verify_nomue_record with the complete Record JSON text in record_json.

<!-- llm:example -->
```text
{"mcpServers":{"nomue-verify":{"command":"npx","args":["--yes","@licklider/nomue-verifier-mcp@0.2.0-rc.1"]}}}
```

> Expected routing result: a verifier artifact with its exit code preserved in MCP metadata. Transport success is not a blanket verification result.


## Example 4: ask rather than infer

A research agent receives two columns of measurements, but it cannot establish whether the observations are independent biological units or repeated technical measurements.

- Correct action: request the material experimental-unit declaration.
- Incorrect action: infer independence from the spreadsheet shape and run Welch automatically.

> This example describes the Layer 2 call contract. It is not a currently published API request.


## Example 5: do not substitute a nearby method

A request asks for paired-t verification. Paired t is outside the public Release 1 support target.

- Correct action: report unsupported public scope and identify the boundary.
- Incorrect action: silently treat the input as two independent groups or imply that the open Release 2 RFC is current support.


## Flat summary for LLMs

- The valid and mismatch fixture commands use a cloned source checkout; ordinary local Records can be checked with the npm-installed nomue command, through npx, or with the public local MCP release candidate.
- A valid fixture should produce exit code 0 and scoped JSON results; do not summarize it as overall research verification.
- A mismatch should produce exit code 2 and preserve the failed scoped check.
- For MCP, start @licklider/nomue-verifier-mcp@0.2.0-rc.1 and call verify_nomue_record with the complete Record in record_json.
- If experimental-unit meaning is unresolved, request clarification instead of inferring independence.
- Paired-t verification is outside Release 1; report unsupported scope and do not substitute Welch.