feat: research director — periodic strategic redirection (opt-in)#26
Merged
Conversation
A meta-agent that periodically reads the population and writes ONE strategic directive into the steering channel for the next interval, to break the local plateaus the population-level loop gets stuck in (e.g. autocorrelation ~C 1.52 across every roster/prompt/config we tried — a strategy bottleneck, not a knob). Design (grounded in how Karpathy's autoresearch actually works: a single agent in a keep/discard loop, quality from a good skill + a structured memory log, not multi-turn deliberation): - kaievolve/research_director.py — ResearchDirector: gathers the experiment log (best, trajectory, top programs + their HMRD notes), sees its own last directive and whether best improved (keep vs pivot), makes ONE LLM call, writes research_directive.md, and keeps memory in research_log.md. Fully fail-safe. - skills/research-director/SKILL.md — the director's instructions, including the full KaiEvolve mechanism + how steering propagates its directive to agents. - Wired into the controller on its OWN cadence (research_director_interval, decoupled from migration so it fires often enough to matter); the directive is folded into the existing steering channel that already reaches every agent. - Gated by prompt.research_director_enabled (default off). Tests in test_research_director.py (5). Full suite green (347). Single-call per fire to start (faithful to autoresearch's per-decision simplicity); multi-turn / web-search / per-island targeting are follow-ups.
This was referenced Jun 8, 2026
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.
An optional meta-agent that periodically reads the evolving population and writes one strategic directive into the steering channel for the next interval — aimed at breaking the local plateaus the population loop gets stuck in (autocorrelation parked at ~C 1.52 across every roster/prompt/config; that's a strategy bottleneck, not a tunable knob).
Design
Grounded in how the autoresearch loop it's modeled on actually works — a single agent in a keep/discard loop whose quality comes from a good instruction skill + a structured memory log, not multi-turn deliberation:
kaievolve/research_director.py—ResearchDirector: gathers the experiment log (current best, trajectory, top programs + the HMRD notes their authors left), sees its own previous directive and whether best-so-far improved (keep vs pivot), makes one LLM call, writesresearch_directive.md, and keeps memory across fires inresearch_log.md. Fully fail-safe — any error is swallowed so it can never break the evolution loop.skills/research-director/SKILL.md— the director's instructions, including the full KaiEvolve mechanism (island MAP-Elites, LLM-mutated programs, frozen evaluator) and how its directive reaches the agents (folded into the steering brief that rides atop every generation prompt).research_director_interval, decoupled from migration so it gets enough shots), and the directive is folded into the existing steering channel in_create_database_snapshot, so it reuses plumbing that already reaches every worker.prompt.research_director_enabled(default off) +research_director_interval.Verification
test_research_director.py(5): directive written + rendered into the steering block, skill+task+experiment-log present in the prompt, keep/pivot state advances across fires, and the fail-safe (a throwing DB yieldsNone, not a crash).Single call per fire to start (faithful to the source's per-decision simplicity); multi-turn / web-search grounding / per-island targeting are natural follow-ups if the A/B shows uplift.
🤖 Generated with Claude Code