Available Categories
The workload categories available for evaluation and routing.
Workload categories are the contract between evaluation and routing. A category tells Meridias which evidence to use and what operational constraints matter for a request.
Why categories matter
Provider performance is not uniform across task types. Categories stop teams from applying a single global ranking to workloads with very different quality and latency requirements.
Category definition
Each category should have a clear task description, evaluation dataset, scoring model, and runtime expectations. Ambiguous categories make benchmark outputs harder to trust.
Operational ownership
Categories should be owned by the teams responsible for their prompts, schemas, or downstream customer experience. Ownership helps keep evaluation data and routing policy aligned.
Evolving coverage
As new product workflows appear, categories should be added deliberately rather than overloaded onto existing ones. This protects the meaning of historical benchmark comparisons.
Next step
Continue to Workload Segments for finer-grained operational grouping.