Description
Compare primary values first, then secondary only on exact primary equality.
An explicit priority model makes a chosen ordering or tradeoff visible. Lexicographic comparison, tolerance-based ties and weighted benefit-minus-harm are different procedures; computing them does not establish their moral justification.
Compare primary values first, then secondary only on exact primary equality.
When to use this tool
Use Utility Lexicographic Priority One Pair when you need a transparent comparison under a supplied priority or valuation rule.
How to use the tool and how it works
- Enter firstPrimary, secondPrimary, firstSecondary, secondSecondary. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read order, primaryDecides. Inspect primaryDecides before interpreting the associated values.
Compare primary values first, then secondary only on exact primary equality. Return -1, 0 or +1 and whether primary decided.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| firstPrimary | First Primary | Required. Finite number. |
| secondPrimary | Second Primary | Required. Finite number. |
| firstSecondary | First Secondary | Required. Finite number. |
| secondSecondary | Second Secondary | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| order | Order | Required. Safe integer. |
| primaryDecides | Primary Decides | Required. Boolean. |
{
"input": {
"firstPrimary": 2,
"secondPrimary": 1,
"firstSecondary": 0,
"secondSecondary": 100
},
"output": {
"order": 1,
"primaryDecides": true
}
} Limitations and assumptions
- Larger values rank higher under the supplied lexicographic policy. This is a comparison procedure, not a determination of morally correct priorities or interpersonal utility comparability.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Examine the reasons for the priorities and the people affected, including omitted duties and uncertainties. Use the appropriate deliberative or professional process rather than treating a numerical ranking as a complete ethical judgment.
References
Similar or alternative tools
- Competing Duty Priority Tie Label
Label tie within absolute tolerance, otherwise prefer the larger supplied priority.
- Need Weighted Allocation One Share Tool
Calculate need weighted allocation one share from explicit caller-supplied inputs.