Part 7 of 12 · 1 min read
Using the patterns
- Spend extra compute where it is checkable: tests, schema validation, deterministic checks. Use a vote only for tasks with a single short answer and diverse errors.
- Vary what you sample: different temperatures, prompts or models increase diversity; identical samples add nothing.
- Cap N from measured returns, and compute cost per percentage point gained.
- Order work by value per cost when both can be measured; keep a deadline or dependency rule for ties and for tasks that unblock others.
- Record outcomes per strategy (prompt version, tool, agent) so that selection can learn; keep a small share of runs for exploration so that changes are noticed.
- Treat tree search and plan search as the same idea with structure: expand several candidate next steps, score them, and keep the best few (beam), spending calls only on promising branches (general knowledge; not tested here).