Repository navigation
fix: synchronize execution-model tiers - #27
Merged
Merged
Conversation
Expose the semantic tier in each execution-group detail alongside its rationale, and validate that it matches the group table. Release the preset as 0.2.1.
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
Execution-plan details now explicitly record each group's selected semantic model tier before its rationale.
The template and validation contract require that field to match the Execution Groups table.
Preset release metadata is updated to
0.2.1.Key Decisions
📋 Canonical Tier Projection
The Execution Groups table remains authoritative. Each detail now carries a validated
Model Tierprojection and a separate provider-neutral rationale, making the assigned tier explicit at the handoff point.🔄 Before & After
0.2.00.2.1