Description
Compare caller-supplied priorities under an explicit equality convention.
A logical calculation operates on a stated representation: truth values, token lists, counts, or an explicitly supplied relation. Checking one assignment, pair, trace, or witness is different from proving a formula or validating an entire argument. Empty domains, duplicate tokens, and scope conventions can change the result.
Compare caller-supplied priorities under an explicit equality convention.
When to use this tool
Use Deontic Exception Priority Gap when you need this exact local truth, count, token, relation, or witness check within a larger logic workflow.
How to use the tool and how it works
- Enter rulePriority, exceptionPriority, exceptionApplies, equalityToException. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read priorityGap, exceptionWins. Inspect exceptionWins before interpreting the associated values.
Return priorityGap=exceptionPriority-rulePriority. Set exceptionWins only when exceptionApplies and its priority is higher, or priorities tie with equalityToException=true.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| rulePriority | Rule Priority | Required. Finite number. |
| exceptionPriority | Exception Priority | Required. Finite number. |
| exceptionApplies | Exception Applies | Required. Boolean. |
| equalityToException | Equality To Exception | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| priorityGap | Priority Gap | Required. Finite number. |
| exceptionWins | Exception Wins | Required. Boolean. |
{
"input": {
"rulePriority": 2,
"exceptionPriority": 3,
"exceptionApplies": true,
"equalityToException": false
},
"output": {
"priorityGap": 1,
"exceptionWins": true
}
}Limitations and assumptions
- The priority ordering and tie policy are supplied. This compares one rule and one exception without resolving a complete norm system or determining legal applicability.
- 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. Signed zero is exported as zero.
Alternative or Complementary methods
Use a parser, scope-aware representation, model checker, or proof procedure when the supplied token or witness representation is insufficient. A local passing check should not be promoted to global validity.
References
Similar or alternative tools
- Deontic Permission Prohibition Duality Tag
Use weak permission P(a) = not O(not a), with prohibition defined as O(not a).
- Alpha Equivalence Bound Variable Pair
Compare flat single-binder token bodies, rejecting potential free-variable capture; nested binders are outside this model.