Shipping gradual prompt rollout
How we built percentage-based traffic splitting for prompt revisions, and the design decisions that were harder than expected.
Sofia Lindqvist ·
Engineering notes, evaluation techniques and product updates from the team building Cloudmind.
How we built percentage-based traffic splitting for prompt revisions, and the design decisions that were harder than expected.
Sofia Lindqvist ·
Three changes, none of them a model swap, and what each one was worth.
Dana Whitfield ·
Why keeping prompts in a doc, or in your repo, both break at the same point.
Marcus Osei ·
A practical method for going from zero to a 50-example golden dataset that actually catches regressions, using traces you already have.
Priya Nandakumar ·
Twelve graders, and why the boring ones catch the most.
Priya Raman ·
Time to first token is the number your users experience. Most dashboards show the wrong one.
Dana Whitfield ·
LLM judges are useful and widely misused. Here is how to measure whether yours is good enough to gate a deploy on.
Marcus Hale ·
What to record, what to collapse, and what to leave out entirely.
Marcus Osei ·
Most teams that want to fine-tune have a prompt problem or a retrieval problem.
Priya Raman ·
A walkthrough of how a silent retry loop tripled one team's token bill, and how nested tracing made it obvious in ten minutes.
Sofia Lindqvist ·
The retrieval was fine in testing because you wrote the test questions.
Dana Whitfield ·
From a user complaint to the exact model call, with nothing skipped.
Marcus Osei ·
The case for moving prompts out of source control and into a versioned registry, and the objections that are actually right.
Marcus Hale ·
Schema enforcement moves the failure rather than removing it.
Priya Raman ·
How to roll out a model change to 5% of traffic and actually learn something.
Dana Whitfield ·
Retrieval quality, not generation quality, is where most RAG systems fail. Here is how to measure the two separately.
Priya Nandakumar ·
The eval set you need is already in your traces.
Marcus Osei ·
What to change in the interface when the model is confidently wrong.
Priya Raman ·
Traditional APM assumes failures are loud. LLM failures are quiet, well-formed and return 200 OK. That difference breaks most of the tooling.
Marcus Hale ·
Announcing our Series A, led by Ridgeline Ventures, and what we are building next.
Cloudmind Team ·