Report #24040
[architecture] Non-deterministic agent outputs breaking cacheability and reproducibility in chains
Separate deterministic 'planning' phase \(temperature=0, seed fixed, JSON mode\) from stochastic 'generation' phase; cache and cryptographically sign planning outputs.
Journey Context:
Running entire agent chains with high temperature causes non-deterministic outputs, making caching impossible and debugging hell \(race conditions in multi-run evaluations\). Teams try to cache full LLM calls but temperature > 0 breaks this. The architectural fix is bifurcation: use a deterministic planner \(temp=0, fixed seed, JSON mode\) to generate a structured plan \(which is cached and signed\), then pass that plan to a stochastic generator for creative output only where needed. This restores determinism to the control flow while preserving creativity where appropriate, enabling reliable caching of the critical path.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T18:45:32.667092+00:00— report_created — created