Skip to content

Update OPTIMIZE_INSTRUCTIONS with lessons from analyses 69-78 - #485

Merged
neoneye merged 1 commit into
mainfrom
fix/identify-update-optimize-instructions
Apr 1, 2026
Merged

Update OPTIMIZE_INSTRUCTIONS with lessons from analyses 69-78#485
neoneye merged 1 commit into
mainfrom
fix/identify-update-optimize-instructions

Conversation

@neoneye

Copy link
Copy Markdown
Member

Summary

Documentation-only change to OPTIMIZE_INSTRUCTIONS in identify_potential_levers.py. No prompt or behavioral changes. Captures lessons from 10 self_improve iterations (analyses 69-78):

No experiment needed — OPTIMIZE_INSTRUCTIONS is developer documentation only, not injected into runtime prompts.

🤖 Generated with Claude Code

Document proven failure modes and fixes from 10 self_improve iterations:
- Field-description template lock: expanded with evidence from PR #484
(the fix) and PR #479 (replacement phrase also locks). Strip to
content-type + word count, let examples teach.
- Negative prohibitions activate banned patterns: confirmed across
PRs #458, #460, #475. Use positive framing instead.
- Consequence parroting in later calls: llama3.1 copies consequences
into review_lever. Anti-parrot needed in subsequent-call prompt.
- Field descriptions vs system prompt consistency: haiku follows
system prompt, text-completion models follow field descriptions.
- Stripping field descriptions too far: weak models need "one sentence"
and section pointer as structural anchors.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@neoneye
neoneye merged commit 046acf1 into mainApr 1, 2026
3 checks passed
@neoneye
neoneye deleted the fix/identify-update-optimize-instructions branch April 1, 2026 23:06
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@neoneye