Iterative baking builds on single-prompt and multi-target baking. Complete those first.
Why Iterative Baking?
Use iterative baking to:- Refine behavior: Modify behavior issues or improve specific responses
- Add capabilities: Layer new skills onto existing knowledge
- Specialize further: Make an expert model even more expert
- A/B test variations: Create model versions to compare
How It Works
- Standard Baking
- Sequential Baking
Train once from a pretrained model to create your first baked model.Qwen/Qwen3-32B → Bake Yoda personality → Yoda v1Single bake pass from pretrained base.
Example: Refining Yoda
Scenario
Your Yoda model (v1) works well but needs improvement:- Sometimes too verbose (want more cryptic responses)
- Missing some Force-specific wisdom
- Could be calmer in certain situations
Complete Iterative Workflow
1
Identify Your Base Model
Use your previously baked model as the starting point:
Use a model from a previous bake in the repo
2
Create Refinement Prompts
Define prompts that address specific improvements:
3
Generate Targeted Training Data
Create training examples that target your improvements:
4
Bake More Prompts
Bake additional prompts into your baked model:
Iterative Baking Strategies
- Incremental Refinement
- A/B Testing
- Domain Expansion
- Error Correction
Make improvements over multiple iterations.V1 → Prompt to be calmer → V2 → Add mysticism prompt → V3 → Reduce verbosity → V4
Each iteration adds one specific improvement.
Each iteration adds one specific improvement.
Key Differences vs. Initial Baking
| Aspect | Parallel Baking | Sequential Baking |
|---|---|---|
| Base model | Pretrained (e.g., Qwen) | Your baked model |
| Training data | Comprehensive coverage | Focused on improvements |
| Goal | Establish behavior/knowledge | Improve behavior/add more knowledge |
Multi-Target Sequential Baking
Refine a model by adding multiple refinement targets:Best Practices
Keep Version History
Keep Version History
Note which version you are baking on top of if testing multiple strategies.
Test Between Iterations
Test Between Iterations
Validate what works and what doesn’t with V1 before creating V2. Ensure you’re refining a solid base.
Small Changes
Small Changes
Make incremental improvements. It’s easier to debug and there’s less risk of breaking existing behavior.
When to Sequentially Bake
Don’t use sequential baking if:- ❌ Your base model has major flaws - start fresh instead
- ❌ You want completely different behavior - bake from pretrained model
- ❌ You’re testing a new prompt - start with new base for clean comparison
- ✅ Base model is good but needs polish
- ✅ Adding complementary skills to existing behavior
- ✅ Fixing specific edge cases