Repository navigation
Conversation
The rows come from what the verifier recorded (reward, agent_steps, skills_loaded) instead of a jq walk over the trajectory, and the pain points come from harbor analyze judging each trial by the task's rubric.toml. The one prompt left in the workflow is the claude -p comparison with main's run of the same leg, which a single trial cannot see. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Y9FLtiiMxVhhkvZjd9SQp4
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Y9FLtiiMxVhhkvZjd9SQp4
Member
Author
|
This is superseded by LightconeResearch/lightcone-evals#5. The eval workflow now lives in lightcone-evals, beside the task it runs. This PR's changes are folded in there, along with Francois's simplifications:
I'm closing this PR. #255 becomes the caller. Generated by Claude Code |
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
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.
What
This PR is stacked on #255 and pairs with LightconeResearch/lightcone-evals#3. The report job no longer needs to know what a trajectory looks like or what to ask about it; the task now owns both.
result.json:reward,agent_stepsandskills_loaded. The jq walk over the ATIF trajectory is gone.require_skillsstill gates, now onskills_loaded.harbor analyze, which judges each trial by the task'srubric.toml, or by Harbor's default rubric if a task has none. That replaces the inline pain-point prompt. The PR comment shows each criterion as ✅ / ❌ / ➖ with its explanation, under the analyzer's summary.claude -pover this run's trajectory,main's trajectory, the rubric analysis and the change under test. It only runs when amainrun of that leg is on record. It stays in CI because a single trial can't see another run.harbor analyzeruns an analyzer container per leg.Size
eval.ymlstays at about the same length. What changes is what it needs to know:Order
tasks_ref: mainserves the old task:agent_steps, so the step gate has nothing to compare. It isn't active yet anyway: it needs threemainruns on record.skills_loadedis unknown, which counts as "not loaded" underrequire_skills. That would fail agent-skills#56. Nothing fails here, becauserequire_skillsis off by default.harbor analyzefalls back to its default rubric.Verified
skills_loaded: 0adds "no skill was loaded" underrequire_skills;analysis.jsonrenders as a summary plus ✅ / ❌ / ➖ checks.harbor analyzeitself, because this sandbox's proxy blocks the image pull. The eval run on this PR is its first real test.🤖 Generated with Claude Code
https://claude.ai/code/session_01Y9FLtiiMxVhhkvZjd9SQp4