Repository navigation
feat(evaluators): add extensions/metadata for additional fields that we want to pass as context to execution of evaluator - #276
Merged
namrataghadi-galileo merged 10 commits intoOct 1, 2026
Conversation
… context to execution of evaluator
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
…ature/SAO-17620-pass-scorer-context-to-galileo-evaluators
Contributor
Author
|
Tested in devstack: |
josjeon
approved these changes
Oct 1, 2026
…ature/SAO-17620-pass-scorer-context-to-galileo-evaluators
wrisa
approved these changes
Oct 1, 2026
namrataghadi-galileo
deleted the
feature/SAO-17620-pass-scorer-context-to-galileo-evaluators
branch
October 1, 2026 18:55
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.
Summary
Pass the authenticated execution context through Agent Control to Galileo evaluators so scorer invocation can receive the Orbit-authorized organization, caller, project, and target information.
Principal.extensionsmetadata.extensionsclaim to newly minted runtime JWTs. Existing claims, expiration behavior, and tokens without extensions remain compatible.execution_context. For the current Orbit contract,caller_idis the authenticated user ID. Alog_streamtarget's authenticated target ID becomesrun_id.Scope
extensionsclaim; no named Galileo fields are added to generic principal or JWT models.Trust and Compatibility
Execution metadata comes only from the verified runtime principal. Evaluator step payloads are not used to construct it, and user-supplied tenant identity is not trusted. No scorer grant is acquired or cached, and the application
GALILEO_API_KEYis not sent to Runners. Legacy runtime tokens without extensions and evaluators that do not override the extension hook remain supported.Testing and Coverage
make checkpassed in PR CI; Codecov patch check passed.make lintandmake typecheckpassed locally.