# Concepts

Source: https://redcrown.ai/docs/concepts/

The objects RedCrown works with, and what "prove" means.

## Prove, not deploy

RedCrown fans one task across many models and configurations, scores the outputs against your own ground truth on cost, quality, and latency, and names the cheapest configuration that clears your quality bar. The verb is prove.

## The object model

- **Experiment** , a task definition: the objective, the quality metric and bar, the candidate models, and the dataset.
- **Run** , one execution of an experiment that produces a ranked report.
- **Report** , the ranked result: per-candidate cost, quality, latency percentiles, and the winner.
- **Receipts** , per-item evidence (the input, each candidate's output, the score) behind the ranking.
- **Provenance** , who ran it, when, the dataset hash, the model versions, and the methodology version.
- **Proof link** , a no-login page that shares a run's report and receipts.
- **Attestation** , a downloadable, cryptographically signed, tamper-evident version of the proof (see [Signed attestation](../guides/signed-attestation/)).

## How the surfaces relate

The same objects are reachable from the app UI, the `redcrown` CLI, and the MCP tools. See the [CLI](../reference/cli/), [MCP](../reference/mcp/), and [UI](../reference/ui/) reference for the full mapping.

Last verified 2026-07-02.