Skip to content
echogeco
The tech a PM needs · Evals

How stale is too stale

Turn an eval's decay with index age into wrong drafts and dollars, and pick the refresh interval where staleness and re-indexing cost least together.

estimatehardExercise · 3 min · 35 of 59
On this page

RAG against fine-tune chose retrieval for a help centre that changes every week and left the index interval open. The eval can measure what a day of staleness costs, and the interval follows from that number.

The situation

One tenant: 1,200 agents, 48,000 drafts a day. Its help centre has 3,000 articles, about 2.4 million words, and about 70 articles change a week, edited throughout the working week rather than in one batch. The retrieval index is rebuilt every Sunday night by re-embedding the whole help centre. Assume 1.3 tokens a word and $0.10 per million embedding tokens. The eval team re-ran the 200-case time-sensitive slice, tickets whose answer is a price, a date or a policy line, against copies of the index 0, 1, 3 and 7 days old: 95%, 93%, 89% and 81%. Those tickets are 10% of the tenant's traffic, and every stale answer is a factual error; the launch gate blocks above 0.5% factual errors. Agents catch three in four wrong drafts at 20 seconds each; the fourth is sent and comes back as a 20-minute escalation. Assume $30 an hour loaded.

The question

Pick the refresh interval for this tenant's index, showing for each candidate what staleness costs a month and what refreshing costs.

A strong answer · Rubric · Where answers go wrong

Write your answer first, then open