Composite scoring
Composite scoring is TypeSafe’s name for: several atomic Scores (or mixed primitives), then a formula you own.
Example from the primitives page: ticket priority from (1) bug severity, (2) customer frustration, (3) how much the report gives an engineer to work with. Normalize, weight, combine in Python. When the blend disagrees with the on-call team, change weights and replay — do not hope a monolithic “rate this ticket 1–10” prompt rebalances.
Why not one Score?
A single rubric that secretly mixes three dimensions produces low confidence and arguments about what a “3” meant. Atomic levels stay inspectable. You can log each dimension.
Keep arithmetic out of the model
Do not ask Jev to multiply weights. jev-1.13 is not a calculator. Sum in code. Do not interpret a fractional Score as a dollar amount or a count.
See the official composite scoring page for their worked request.
Sources
Public TypeSafe or adjacent documentation only. No private claims.