Direct answer
That an evaluation protocol is expected to record the test sets, the metrics and the tools used, so that the evaluation can be examined afterwards.
Answer contract
Apply the protocol lens only to the exact inspected source scope; do not infer authority from adjacent topics.
Evidence and exact locators
Inspected source 1 — MEASURE 2.1 — test sets, metrics and TEVV tooling are documented.. Supports: The bounded scope recorded in the reviewed specification.
What the evidence does not establish
A specification is not a route, a release, or a public page.
Rights and reuse
Rights basis recorded in the reviewed specification; link and bounded original paraphrase only.
Dependencies and related concepts
applies-to: urn:maha:concept:evidence:evaluation-protocol
governed-by: urn:maha:concept:governance
evidence-for: urn:maha:concept:evidence
Questions this page can answer
What does NIST AI Risk Management Framework (AI RMF 1.0), NIST AI 100-1 state about evaluation-protocol?
That an evaluation protocol is expected to record the test sets, the metrics and the tools used, so that the evaluation can be examined afterwards.
Which exact locator in that source supports the claim on this page?
Inspected source 1, MEASURE 2.1 — test sets, metrics and TEVV tooling are documented.
What does this source explicitly not establish about evaluation-protocol?
A specification is not a route, a release, or a public page.
Which canonical definition does this route depend on, and where is it owned?
applies-to: urn:maha:concept:evidence:evaluation-protocol governed-by: urn:maha:concept:governance evidence-for: urn:maha:concept:evidence
What would have to be inspected before this page could claim more than it does?
A source, locator, rights, scope, boundary, dependency, implementation, or release change requires a new exact-revision review.