docs(TEXT scores): add documentation for the new TEXT score type#2769
Draft
docs(TEXT scores): add documentation for the new TEXT score type#2769
TEXT scores): add documentation for the new TEXT score type#2769Conversation
Add documentation for the new TEXT score type across all score-related pages. Consolidate score concepts (types, use cases, scores vs tags, comments) into a central Scores section in core-concepts.mdx and slim down the FAQ to a redirect. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Move data-model.mdx from experiments/ to evaluation-methods/ as the last nav item. Add redirect for the old path and update all 17 internal references across content, components, and agent config. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
wochinge
commented
Apr 2, 2026
|
|
||
| # What Are Scores and When Should I Use Them? | ||
|
|
||
| Scores are Langfuse's universal data object for storing **evaluation results**. Any time you want to assign a quality judgment to an LLM output, whether by a human, an LLM judge, a programmatic check, or end-user feedback, the result is stored as a score. |
Author
There was a problem hiding this comment.
In my opinion this FAQ was too hidden for the users - moved most of it to the concepts page.
wochinge
commented
Apr 2, 2026
Author
There was a problem hiding this comment.
I think top level would be even better than having it under evaluation-methods but if we prioritize having a consistent docs structure then this is good enough.
I'd definitely not keep it under experiments because scores are not tied to experiments at all. Marlies is currently also breaking up datasets vs experiments as well which emphasizes the change even more
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed Changes