feat(engine): add layer-based scenario selection (evaluation.scenarios_per_layer)#7
Merged
regevguym merged 1 commit intomondaycom:mainfrom Mar 22, 2026
Conversation
…s_per_layer) - New SuiteDefinition.evaluation config with scenarios_per_layer - pickScenariosByLayer() function: respects per-layer counts, preserves YAML order - If no config → all scenarios run (backwards compatible) - If layer omitted → all scenarios for that layer included - Seeded PRNG for deterministic selection - Zod schema validation for evaluation config - 8 new tests covering all selection behaviors - Updated ARCHITECTURE.md with docs and examples
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
Adds
evaluation.scenarios_per_layerconfig to suite YAML schema, allowing suite authors to control how many scenarios are randomly selected per evaluation layer.Why
Previously, scenario selection was either "run all" or done externally by consumers (e.g. agentalent's blind
shuffle + slice). This led to unbalanced evaluations — potentially 3 execution scenarios and 0 reasoning.Suite authors should control the evaluation structure.
How
New YAML config
Rules
evaluationconfig → ALL scenarios run (backwards compatible)scenarios_per_layer→ all scenarios for that layer includedChanges
types.ts: NewEvaluationConfiginterface onSuiteDefinitionschema.ts: Zod validation forevaluation.scenarios_per_layerloader.ts: NewpickScenariosByLayer()function (exported)index.ts: ExportpickScenariosByLayer+EvaluationConfigSchemaARCHITECTURE.md: Docs section + YAML exampleTest results
Breaking changes
None. The
evaluationfield is optional with full backwards compatibility.