Repository navigation
docs: align clip and rubric examples with their commands - #19
Merged
Merged
Conversation
Route option-bearing reconstruction examples through iterate and numerical rubric examples through judge:rubric. Describe re-asking as opt-in, preserving the historical observation. Co-authored-by: Codex <noreply@openai.com>
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.
The documented clip and judge invocations used options accepted by different commands, and the re-ask description was unconditional. Route the reconstruction example through
iterate, the numeric rubric example throughjudge:rubric, and describe--reaskas opt-in with three default samples. Retain the historical observation and all other content.Validation: the exact three-replacement diff was independently checked against package.json, iterate, judge-rubric, clip and judge-video at the pinned source. Published source was read back exactly; comparison contains one commit and README.md only. No project command, model request or UI workflow was executed; this does not certify runtime behavior or current quality scores.