Uh oh!
There was an error while loading. Please reload this page.
Include consequences and review in enrich batch prompt - #451
Merged
Conversation
The enrich step asks the LLM to generate description and conflict_text for each lever, but the batch prompt only provided lever_id, name, and options. The consequences (what happens when the lever is pulled) and review (the documented primary trade-off) fields were loaded but never forwarded to the prompt, forcing the model to infer them from the name alone. This adds both fields to the per-lever details in the batch prompt so the LLM can produce grounded descriptions and conflict analysis. Identified by analysis/53_enrich_potential_levers synthesis (direction #1). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
neoneye
commented
Mar 29, 2026
MemberAuthor
Self-Improve Iteration Result: YES (keep)Experiment ran as analysis/54_enrich_potential_levers (runs 85–91, 7 models × 5 plans). Improvements
Regressions (minor)
Unchanged
Full assessment: analysis/54_enrich_potential_levers/assessment.md |
Uh oh!
There was an error while loading. Please reload this page.
neoneye added a commit
that referenced
this pull request
Mar 29, 2026
B1: The enrich step previously aborted the entire plan on any batch failure. Now on failure it splits the batch in half and retries each sub-batch. If a single-lever batch still fails, it logs and skips that lever rather than discarding all successfully enriched levers. This should recover gpt-oss-20b plans that fail on large batches hitting the output token limit. B4: runner.py now reports the actual batches_succeeded count from EnrichPotentialLevers instead of hardcoding 1. D5: Added two new known problems to OPTIMIZE_INSTRUCTIONS: - Consequence echoing without elaboration (llama3.1 post-PR #451) - UUID cross-reference format inconsistency Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
4 tasks
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 freeto 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
lever_id,name, andoptionsto the LLM, but omittedconsequencesandreview— the two fields that document the lever's effects and primary trade-off.description,synergy_text, andconflict_text.Identified by
analysis/53_enrich_potential_leverssynthesis as the #1 ranked improvement direction (B3 + I4).Test plan
enrich_potential_leversexperiment with this PR across all models🤖 Generated with Claude Code