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

# Use your results

> Keep your measured self-check result with each release, and fix and rerun what failed.

Keep proof that each release of your integration behaves correctly. A finished
[sandbox self-check](/providers/test-evidence) gives you a run ID, the ruleset version and a result
for every rule. Store those three with the release they measured. Nothing is sent to trdrs: the
result lives on the sandbox, and you read it there.

Use this page after a run finishes, whether it passed or failed.

## When a rule fails

The result says what was seen for each rule that failed. Fix your client, close the run and open a
new one. The failure stays in its original run, so the history of what you fixed remains on record.

## The rule you confirm yourself

A `null` money field must show as **unknown** on your screen, never as zero. No HTTP traffic can
show how your screen draws a number, so check it with your own interface test and record that you
did.

## What a pass does and doesn't do

A pass shows how your client handled the API during that run. It doesn't move your venue into
production and doesn't make you [Listed](/guides/get-listed) in Connect. Brand review and production
onboarding are separate steps with your trdrs contact, and the self-check itself stays free.

## Next steps

<CardGroup cols={2}>
  <Card title="Run a self-check" icon="flask" href="/providers/test-evidence">
    Open a new run after a fix.
  </Card>

  <Card title="Get listed" icon="store" href="/guides/get-listed">
    See what getting Listed in Connect takes.
  </Card>
</CardGroup>