KCAE.USE:4.3 - Turn anticipated use into a workload

Sample real requests and failures when available. Include known-name lookup, uncertain vocabulary, cross-document synthesis, historical use, no useful advice and source changes. Record approximate corpus size and growth, request rate, update rate, language/format distribution, acceptable latency, required source return and recipient preparation. Distinguish observations from forecasts. If no log exists, construct explicit scenarios and treat the workload as a design assumption to revisit after use.

Select a finite horizon and identify who bears each cost. Build and extraction costs occur before requests; maintenance follows changes; discovery and reading occur per question; interpretation and action burden fall on the recipient. Retention and notification add separate costs. Shared work is counted once, while costs displaced to a colleague remain costs. KCAE.EVAL supplies the comparison method; the workload supplies its population and use conditions.