Batch a regulatory briefing into one call

01 · Role in the system

What Jev does here

Jev answers eight Noul, two Choice, and three Score questions against the same 53,777-character document. The cookbook repeats both batching strategies five times and compares each answer's tracked probability or normalized score. Local code pins and fetches the article, caches calls, calculates variance, tokens, cost, and elapsed time, and renders the comparison.

02 · Control boundary

Where Jev sits

A document-dominated workload batches independent typed judgments so shared state is sent once; code measures and compares the two call strategies.

Code owns the loop, permissions, thresholds, validation, and side effects. Jev owns only the bounded judgments described above.

03 · Known limits

What this evidence does not prove

• The cost advantage is largest because the long shared document dominates each request; workloads with little shared state will differ.
• The reported speed ratio sums sequential single-call latencies, and concurrent requests would reduce that latency gap without reducing repeated input tokens.

04 · Attribution

Public sources

This is an Official record: the example was published by TypeSafe itself.

• TypeSafe ↗Official · cookbook · public · checked 2026-09-18