OpenEvalDocumentation
GitHub
RUN & INSPECT

Read the evidence

Follow a score back to the work that earned it.

On this page

Open a run, then its judgment

  1. Select an eval
  2. Open a model run
  3. Read Session / Judge
  4. Follow a citation
SQL rubric decisions and evidence links in the judge inspector
Illustrative SQL evaluation: two decisions from the same recorded answer.Open full size
CitationWhat it points to
responseThe final user-facing answer
messageA recorded session message
toolA recorded tool call and its result
eventAn event in the execution recording
artifactA file from the initial or final workspace

Revise a rubric without losing evidence

terminal
bunx --bun @hona/openeval rejudge ./results/RUN_ID EVAL_RUN_ID
bunx --bun @hona/openeval snapshot ./results/RUN_ID before-rubric-update

Finalized eval runs and judge runs are immutable. A completed rejudge updates the active selection; the original recording and earlier judgments remain available.

Calibrate the judge

ControlWhat to establish
PositiveA valid response passes through an equivalent workflow
NegativeA real failure is detected
BorderlineA partial answer, correction, or omission is handled deliberately
Unavailable evidenceThe judge returns unknown rather than inventing an observation
SDK exports for author-owned controls
import { recordEvidence, judgeEvidence } from "@hona/openeval";

// recordEvidence: create a recording from supplied text and tool records.
// judgeEvidence: grade retained evidence in a separate audit directory.

Keep calibration examples outside candidate workspaces. Use expected labels you have reviewed, and inspect disagreements before changing a rubric.

Find in documentation