Utility

Version

v3 · 2026-09-28 · History

Prime #

1558

Domain group

Social Sciences

Origin domain

Economics & Finance

Core Idea

Utility is a substrate-independent evaluation that maps possible outcomes to an ordered value representation preserving the chooser’s relevant preference comparisons under declared conditions. The abstraction is not exhausted by its familiar source-domain notation. Its autonomous core is preference-preserving value representation, distinct from usefulness in ordinary speech, realized welfare, monetary price or probability.

The operative mechanism is this: Outcomes are compared, preference evidence or normative commitments constrain an ordering and a numerical or ordinal representation assigns values so larger values track more-preferred or more-valued states. The mechanism separates identity from observation. A case does not qualify merely because an observer can describe it using the word utility; the constitutive relation must be present in the carrier.

How would you explain it like I'm…

Points for What You Like

If you like ice cream more than carrots, and carrots more than broccoli, you could give them points: ice cream 3, carrots 2, broccoli 1. Bigger points mean you like it more. The points just keep your order of likes — they're not how useful something is or how much it costs.

Ranking What You Prefer

Utility is a way of giving numbers (or ranks) to choices so that the ones someone prefers get bigger numbers. If you'd rather have a bike than a scooter, the bike gets a higher utility for you. It isn't the same as how useful something is, how much it costs, or how happy it will actually make you later. It's just a way to write down someone's preferences so you can reason about choices. And it's about one particular chooser — your numbers and your friend's numbers can't simply be compared.

Preference-Preserving Values

Utility is a way of representing preferences with values, so that more-preferred outcomes get higher values than less-preferred ones. It belongs to a specific evaluator and a specific set of possible outcomes. In the simplest version, only the order matters: 10 versus 5 just means 'preferred,' not 'twice as good.' Saying something stronger — like how much more one thing is preferred, how to handle risky choices, or comparing one person's utility to another's — requires extra assumptions. Utility isn't the same as everyday usefulness, actual well-being, money price, or probability. Economists use it to model choices: people are treated as picking the option with the highest utility.

 

Utility is an evaluation that maps possible outcomes to an ordered value representation preserving a chooser's relevant preference comparisons under declared conditions. Its mechanism: outcomes are compared; preference evidence or normative commitments constrain an ordering; and a numerical or ordinal representation assigns values so that larger values track more-preferred or more-valued states. A declared evaluator, outcome domain, and preference ordering determine utility only up to order-preserving transformation (ordinal utility). Stronger claims each require additional axioms: cardinal scale and expected-utility representation over lotteries (e.g., von Neumann–Morgenstern axioms), and interpersonal comparison, which is not implied by individual orderings at all. Utility is thus a preference-preserving representation — distinct from ordinary usefulness, from realized welfare or happiness, from monetary price, and from probability. Treating utility numbers as measured satisfaction, or adding them across people without justification, are characteristic misuses.

Broad Use

consumer choice. The carrier is bundles of goods. The identity test is that represent an individual preference ordering. This is a literal instantiation rather than decorative analogy because the carrier, observable organization, conserved relation, variation class, and failure test retain the same roles. The domain accent is ordinal scale may suffice. A responsible analysis states scale, observation window, representation and noise model before claiming the structure, then distinguishes the structure itself from the process used to discover, stabilize or exploit it. Removing the constitutive relation must make the classification fail; otherwise the label is only topical resemblance. Evidence can be mathematical, experimental, computational or documentary, but it must attach to the same role graph and expose uncertainty and counterexamples.

Clarity

A clear Utility claim can be rewritten as a testable sentence: on carrier C at scale S, relation R holds within tolerance T, remains under transformations V, and fails for counterexample K. This grammar exposes missing components and prevents a noun from standing in for an argument.

Manages Complexity

Utility manages complexity by replacing an unstructured inventory with a small set of relations that survive relevant variation. Compression becomes legitimate when the retained relation supports reconstruction, comparison or reliable discrimination and the discarded details are declared incidental for the task.

The abstraction also supports chunking. Once an organized unit is established, reasoning can treat it as one object while retaining an audit trail to its elements.

Abstract Reasoning

1. Type the carrier and explain why its elements are individuated at the selected scale.
2. Separate the target structure from the notation, image, model or story used to display it.
3. State the constitutive relation as an equation, rule, repeatability condition or traceable interpretive criterion.
4. List transformations expected to preserve identity and justify why they are incidental.
5. Choose at least one positive diagnostic and one collapse test.

Knowledge Transfer

Transfer begins from the role graph, not the name. Preserve carrier, relation, invariant, admissible variation, diagnostic and collapse test; then substitute domain occupants. A successful mapping explains how the target case would be recognized and how it would fail.

The most common transfer error is feature substitution. One field may represent the structure visually, another algebraically and another behaviorally. The visible features are not the invariant. Transfer must identify the relation those features evidence and state the target domain's measurement or proof obligations.

Relationships to Other Abstractions

Current abstraction Utility Prime

Parents (1) — outgoing typed relations

• Utility is a kind of Evaluation Prime

  The accepted reference-grade review places Utility under Evaluation because the child instantiates or depends on the parent's broader structure while retaining its own constitutive identity.

Children (3) — abstractions linked here by typed relations

• Compensation principle Domain-specific is a kind of Utility

  It remains its own entry because its identity is fixed by the original and alternative social states, affected persons, valuation and price basis, gains and losses, hypothetical transfer, Kaldor Hicks or related test, feasibility versus actual payment, distributional assumptions and reversal or inconsistency checks.

• Time-Utility Function Domain-specific presupposes Utility

  Time-Utility Function presupposes Utility: the parent's defining role is necessary to the child's frozen mechanism or criterion.

• Welfare Cost of Business Cycles Domain-specific presupposes Utility

  Welfare Cost of Business Cycles presupposes Utility: the parent's defining role is necessary to the child's frozen mechanism or criterion.

Hierarchy path (1) — routes to 1 parentless root

• Utility → is a kind of Evaluation → presupposes Comparison