| name | eval-author-inspect-trace |
| description | Use when eval-author has routed to this sub-flow for one Intake trace. Do not use for instrumenting agents, ingesting telemetry, importing a trace store, verifying ingest, or querying Intake outside Eval Author; those belong to nemo-intake. |
| triggers | ["eval-author routed to inspect-trace","inspect the intake trace eval-author named","continue eval-author intake trace inspection"] |
| not-for | ["eval-author (use for the standard, the boundaries, and to pick a sub-flow)","eval-author-discover (use to establish whether a repository's Harbor suite is runnable)","eval-author-audit (use to validate an existing finite audit.md coverage denominator)","nemo-intake (use to instrument agents, ingest telemetry, or query Intake outside Eval Author)","nemo-experimentalist (use for an optimization experiment across many trials)"] |
| compatibility | A working nemo CLI invocation, an explicit workspace, and read access to Intake on a configured local or remote NeMo Platform instance. |
| maturity | alpha |
| license | Apache-2.0 |
| user-invocable | false |
| allowed-tools | ["Bash","Read","Write","Grep","Glob"] |
Eval Author: inspect an Intake trace
Read one Intake trace, explain its trajectory, and save an evidence-backed
report. Start this sub-flow only after eval-author selects it. For
instrumentation, ingest, or a general Intake query, use nemo-intake. Read
eval-author for the shared standard and boundaries.
Requirements
Use a working nemo CLI invocation with an explicit workspace and read access to
Intake. The configured NeMo Platform instance can be local or remote. Use the
active context, a caller-supplied context, or NMP_BASE_URL and
NMP_ACCESS_TOKEN.
Resolve the CLI invocation
Resolve the CLI invocation once before the first Intake read. If the caller
provides an invocation, verify that caller-supplied invocation first. For a
caller-supplied uv run nemo invocation, add --no-sync.
Otherwise, probe these candidates in order with the --version flag:
- Use
nemo when command -v nemo succeeds.
- Use
.venv/bin/nemo when that executable exists in the source checkout.
- Use
uv run --no-sync nemo when uv and the prepared environment provide
the CLI.
Continue after a launcher error while another candidate remains. If no
candidate works, quote the launcher errors and stop.
Use the resolved invocation for every command. The examples use nemo as the
logical prefix; replace only that prefix. In the report, record each expanded
command instead of the logical example.
Don't install the CLI, authenticate, change contexts, start services, or repair
the platform. Don't run uv sync, use uvx, or activate an environment. Don't
print, copy, or save credentials. The first Intake read validates access. If it
exits nonzero, quote the CLI error and stop.
Select the trace
Accept a bare Intake trace ID or intake://traces/TRACE_ID. Reject every other
URI scheme. If no trace is named, list recent candidates:
nemo intake traces list --output-format=json --workspace="WORKSPACE" --mode=preview --sort=-started_at --page-size=20
If the request names an agent, list recent traces that contain its spans:
nemo intake spans groups list --output-format=json --workspace= --by=trace_id --filter.agent-name= --=-started_at --page-size=20
