Utility¶
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.
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¶
- 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) — more general patterns this builds on
-
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 (1) — more specific cases that build on this
-
Compensation principle Domain-specific is a kind of Utility
The proposed strict upward parent is
prime:utility.
Hierarchy path (1) — routes to 1 parentless root
- Utility → Evaluation → Comparison → Self Checking