Description
For nonnegative integer matchingObjects return exists=(count>0), unique=(count===1), and failedUniqueness=(count!==1).
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.
For nonnegative integer matchingObjects return exists=(count>0), unique=(count===1), and failedUniqueness=(count!==1).
When to use this tool
Use Definite Description Uniqueness Count 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 matchingObjects. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read exists, unique, failedUniqueness. Inspect exists, unique, failedUniqueness before interpreting the associated values.
For nonnegative integer matchingObjects return exists=(count>0), unique=(count===1), and failedUniqueness=(count!==1).1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| matchingObjects | Matching Objects | Required. Safe integer; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| exists | Exists | Required. Boolean. |
| unique | Unique | Required. Boolean. |
| failedUniqueness | Failed Uniqueness | Required. Boolean. |
{
"input": {
"matchingObjects": 1
},
"output": {
"exists": true,
"unique": true,
"failedUniqueness": false
}
}Limitations and assumptions
- Zero matches fails uniqueness as well as existence. The count is supplied; objects, predicates, and philosophical interpretation of definite descriptions are not evaluated.
- 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
- Argument Conclusion Reference Count
Count exact supplied conclusion references without deciding logical entailment.
- Formula Free Variable Count
Count explicitly annotated variable occurrences; binding scope is supplied rather than parsed.