Repository navigation
Use Gemma 4 31B for child simulation - #38
Merged
Merged
Conversation
Clemalfroy
changed the title
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
1 participant
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.
New runs using the bundled profile use
google/gemma-4-31b-itfor first child messages, simulation and continuation. Settings: the existing 4,000-token default ceiling, with first-message generation retaining its explicit 300-token cap, no explicit temperature or reasoning options, Vercel Gateway with no upstream provider pin. Prompts and judges are unchanged.The configuration fingerprint changes; DeepSeek registry entries and historical artifacts remain available. Existing corpora keep their stored
firstUserMessagevalues. This PR does not regenerate corpora or add a regeneration script. Empty, filtered and truncated Gemma responses fail rather than becoming child dialogue.Validation:
yarn tsbuildpassed.yarn prettypassed.google/gemma-4-31b-it. This was an integration smoke check, not a repeat of the research battery.yarn lintpassed with one existing unused-variable warning.Reference: https://github.com/korabench/research/tree/main/refusal_battery
Companion infra PR https://github.com/korabench/infra/pull/204 adds the production driver, queue and new-run default while preserving historical DeepSeek profiles. Neither PR deploys production.