Skip to content

docs: document score result shape#189

Open
Rul1an (Rul1an) wants to merge 3 commits into
braintrustdata:mainfrom
Rul1an:codex/document-score-result-surface
Open

docs: document score result shape#189
Rul1an (Rul1an) wants to merge 3 commits into
braintrustdata:mainfrom
Rul1an:codex/document-score-result-surface

Conversation

@Rul1an
Copy link
Copy Markdown

Summary

Documents the small Score result object returned by scorers in the README.

The new section calls out the public fields consumers should read when storing, comparing, or exporting evaluation results: name, score, metadata, and the deprecated error field. It also clarifies that inputs, expected values, prompts, and runtime context are kept separately from the returned Score.

Context

This follows the public-surface clarification from #187, where maintainers confirmed the returned Score object is the right minimal scorer-consumer boundary.

Validation

  • git diff --check

Copilot AI review requested due to automatic review settings May 18, 2026 18:15
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds README documentation defining the public Score result object returned by scorers, clarifying which fields external consumers should use and what context is intentionally kept outside the Score.

Changes:

  • Documented the Score result shape (name, score, metadata, and deprecated error) in the README.
  • Clarified that inputs/expected values/prompts/runtime context are not included in Score and should be stored separately.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread README.md Outdated
- `score`: a number between 0 and 1, or `None` / `null` when the evaluation is skipped
- `metadata`: optional scorer-specific details, such as rationale text or a
selected choice
- `error`: deprecated; errors are propagated to the caller in current versions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants