> ## Documentation Index
> Fetch the complete documentation index at: https://docs.remyx.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Interpret evaluation results

> Understand what a validation can and cannot establish.

Read a validation result by connecting the question, measured criteria, and evidence.

## 1. Start with the question

Identify what the test was designed to measure. Check whether it compares branches, tests a capability, or uses a reference threshold.

## 2. Read the measured values

Compare each metric with its stated criterion. A diagnostic metric provides context but does not determine the verdict unless required by the spec.

| Measure | Measured value | Required criterion | Scope of evidence |
| - | - | - | - |
| Explained variance | TopK 0.9666, AbsTopK 0.9677 | AbsTopK no more than 0.02 worse | Single-seed CPU run |
| Negative selected latents | TopK 0%, AbsTopK 49.2% | AbsTopK at least 1% | Single-seed CPU run |

[Read the PR result](https://github.com/salma-remyx/SAELens/pull/5)

## 3. Check the evidence

Open the executed notebook and inspect the data, seed, compute tier, and any limitations recorded by the run.

[Open the executed notebook](https://github.com/salma-remyx/SAELens/blob/6989234239f49130fd1e77412f04a0513268fc87/.remyx/validations/abstopk-vs-topk-tinystories.ipynb)

## 4. Decide what remains unknown

A passing offline evaluation does not establish downstream production impact. An inconclusive or no-signal result means the chosen test did not establish a reliable answer.

## Next steps

[Results and evidence](https://docs.remyx.ai/platform/agents/validate-results.md) · [Validation spec](https://docs.remyx.ai/platform/agents/validate-spec.md) · [Compute and limits](https://docs.remyx.ai/platform/agents/validate-limits.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.