Skip to content

Main content

Quantified Statement Empty Domain Policy Tool

Classical finite quantification with an explicit empty-domain admission flag.

Loading tool…

Description

Classical finite quantification with an explicit empty-domain admission flag.

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.

Classical finite quantification with an explicit empty-domain admission flag.

When to use this tool

Use Quantified Statement Empty Domain Policy 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

  1. Enter predicateValues, quantifier, allowEmpty. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read value, empty. Inspect value, empty before interpreting the associated values.

Accept quantifier all or some and require a nonempty predicateValues list unless allowEmpty. Return every value for all, some value for some, and empty on an empty list.1

Input fieldMeaning and unitsAccepted input
predicateValuesPredicate ValuesRequired. Array of boolean; maximum items 256.
quantifierQuantifierRequired. Text; one of "all", "some"; maximum UTF-16 length 8192.
allowEmptyAllow EmptyRequired. Boolean.
Output fieldInterpretationReturned shape
valueValueRequired. Boolean.
emptyEmptyRequired. Boolean.
json
{
  "input": {
    "predicateValues": [],
    "quantifier": "all",
    "allowEmpty": true
  },
  "output": {
    "value": true,
    "empty": true
  }
}

Limitations and assumptions

  • When empty input is allowed, all is true and some false. The chosen empty-domain policy is explicit and no domain or predicate evaluation is performed.
  • 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.

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

  1. Calculation and input contract: philosophy/quantified-statement-empty-domain-policy — tool.io

Similar or alternative tools