Consume Verifiers eval process protocol#760
Draft
xeophon wants to merge 12 commits into
Draft
Conversation
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.
Overview
Keeps Typer as the Prime command router while handing native V1 eval parsing and execution to Verifiers through its versioned process contract.
Native V1 flow
-sshuffle flag is forwarded unchanged; only explicit--save-resultsselects the V0 compatibility path.verifiers_bridge.pycommand bridge rather than adding a separate process module.Artifact consumption
Prime push and Lab read the existing resolved
config.tomland Traceresults.jsonlartifacts through the shared evaluation utilities. Local run identity comes from the output directory name; no additional sidecar is required. Trace projection tolerates additive MessageNode fields and uses provider token usage when token IDs are unavailable.Prime-owned options
V0 upload options remain scoped to the explicit V0 path. Native V1 runs can be uploaded separately with
prime eval push, and hosted evaluation options remain Prime-owned.Dependency
Verifiers protocol implementation: PrimeIntellect-ai/verifiers#1857