Pith. sign in

REVIEW 3 major objections 4 minor 2 references

Quantifiers metamorphoses. Generalizations, variations, algorithmic semantics

T0 review · 3 major / 4 minor · reviewed 2026-08-14 · deepseek-v4-flash

Pith's one-line read The paper recasts ∀ and ∃ as property-checking operators over functions, so every quantifier term becomes a lambda-defined anonymous function.

desk verdict A clear but thin working note on quantifiers in YAFOLL: the parameterized ∀/∃ and lambda syntax are elementary, and the unformalized enumeration assumption undercuts the claim that # causes no algorithmic problems. read the letter →

arxiv 1908.11342 v1 pith:ZAKAY4AG submitted 2019-08-24 cs.LO

classification cs.LO MSC 03B1003B7068Q55
keywords quantifierquantityalgorithmicsemanticsforallexistslambdacalculusfinitestructuresYAFOLL
verification ladder T0 review T1 audit T2 compute T3 formal

The pith

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The reading

This paper argues that quantifiers are understood as operators over functions rather than as primitive variable binders. In this reading, $\forall(v)x{:}s\,f(x)$ checks whether $f$ is constant on sort $s$ with value $v$, and $\exists(v)x{:}s\,f(x)$ checks whether $v$ appears among the values of $f$. A quantified term can be written as an anonymous function definition in the $\lambda$-calculus style, so the quantifier variable becomes a formal parameter. The paper extends the same operator view to a counting quantifier $\#$ and a sum quantifier $\Sigma$, and supplies enumeration-based algorithmic semantics for $\forall$ and $\exists$ on finite sorts. If correct, this gives YAFOLL a uniform, syntactically complete way to define quantifier meaning that can be turned almost directly into program instructions.

What carries the argument

The central mechanism is the parameterized quantifier form $Q(v)x{:}s\,t$, together with the well-formedness constraint that the sort of $v$ matches the sort of the value of $t$. Rewriting the term $t$ as a $\lambda$ abstraction turns the bound variable into a formal parameter, so the quantifier no longer binds a variable but applies to a function and tests a property: constancy for $\forall$, presence in the image for $\exists$, cardinality for $\#$, summation for $\Sigma$. The algorithmic semantics is the accompanying 'iterate over the finite sort' procedure: it returns `_False` for $\forall$ and $\exists$ when the sort is empty, and otherwise scans the enumerated elements, which makes the account executable.

What would settle it

Give the processor an empty sort $s$ and any value $v$: the paper's algorithms prescribe `_False` for both $\forall(v)x{:}s\,f(x)$ and $\exists(v)x{:}s\,f(x)$. If an implementation returns `_True` for the universal case on the grounds of vacuous truth, the semantics depends on an unstated non-vacuity convention, and the claimed constancy/image reading would need revision.

Watch

Extended reading notes

Core claim

The central claim is that the universal and existential quantifiers, generalized with a parameter, are exactly the tests of two properties of a function. For $f:s\to s_1$ and $v\in s_1$, $\forall(v)x{:}s\,f(x)$ is true exactly when $f$ is defined and equal to $v$ on every element of $s$, and $\exists(v)x{:}s\,f(x)$ is true exactly when some element of $s$ maps to $v$. The paper then identifies the quantified term with an anonymous function $x\mapsto t$, treating any external parameters as free variables of that function, and makes the quantifier an operator applied to the function. On finite structures, the truth values are computed by enumerating $s$; the paper writes explicit algorithms for both quantifiers and notes that they are easily converted into programming-language instructions. It also introduces $\#$, which returns the number of elements of a sort satisfying a predicate, and $\Sigma$, which returns the sum of a numeric function over a finite sort.

Load-bearing premise

The algorithmic semantics assume every sort is finite and comes with an enumeration mechanism that actually reaches every element and terminates; without that, the $\forall$ and $\exists$ procedures never finish or have no defined behavior.

Editorial extensions

If this is right

  • Every quantifier expression in YAFOLL can be rewritten without quantifier variables, because the quantified term becomes an anonymous function whose formal parameter replaces the variable.
  • The same syntax handles ordinary predicates as a special case: $\forall x{:}s\,p(x)$ is $\forall(\_True)x{:}s\,p(x)$, and similarly for $\exists$.
  • The counting quantifier $\#$ makes definitions such as 'loop' and 'binary edge' in graph theory direct equations about cardinalities, so quantitative requirements can be stated inside a formal theory.
  • The enumeration algorithms for $\forall$ and $\exists$ on finite sorts are simple enough to be compiled into a programming language, giving executable semantics for quantifier-heavy queries.

Reading between the lines

Editorial extensions of the paper, not claims the author makes directly.

  • This operator view suggests a family of threshold quantifiers ('at least $n$', 'at most $n$', 'exactly $n$') built on $\#$, which would make cardinality constraints first-class in the language without leaving finite-model semantics.
  • The same lambda-abstraction move could be applied to quantifiers over several variables, treating a binary predicate $R(x,y)$ as a curried function and letting a quantifier test properties of its image; the paper does not spell this out.
  • If a sort is infinite but effectively enumerable, the $\forall$ and $\exists$ algorithms become nonterminating processes; a natural extension would introduce explicit partiality or convergence conventions, which the paper does not address.
Share X Bluesky LinkedIn Reddit HN

Signed reviews

No signed human review yet.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, and a circularity audit.

Referee Report

3 major / 4 minor

Summary. The paper proposes a reformulation of the quantifiers of the many-sorted language YAFOLL: the quantifier expression Q(v)x:s t is read as an operator acting on the function x↦t, where ∀ checks whether the function is constant at value v and ∃ checks whether v belongs to the image of the function. The paper then observes that the body t can be viewed as a lambda abstraction, so that quantifier variables become formal parameters and a quantifier becomes an operator over a function definition. It introduces a counting quantifier #x:s p(x) and a sum quantifier Σx:s f(x), and gives informal algorithmic semantics for ∀ and ∃ based on iterating over the elements of a finite sort. The conclusion argues that the counting quantifier is a useful practical addition for work with finite models.

Significance. The central observation that ∀ and ∃ can be reformulated as operators testing two elementary properties of a function is correct and clearly presented, and the lambda-calculus reading of the quantifier body is a useful way to explain why quantifier variables can be eliminated in favor of formal parameters. The paper also gives concrete examples (loop, binary edge) and explicitly handles partial functions in the ∀ and ∃ algorithms, which is a thoughtful touch. However, the paper's headline claim that the counting quantifier # 'does not cause logical and algorithmic problems on finite structures' is not supported by any algorithmic semantics or proof, and the algorithmic semantics that are given rely on an unformalized enumeration mechanism. The significance is therefore moderate: the conceptual reframing is elegant, but the paper does not deliver the technical development of the counting and summation quantifiers that the abstract promises.

major comments (3)
  1. [∀∃. Algorithmic semantics] The algorithms for ∀ and ∃ iterate over all elements of the sort s, but the paper only says that enumeration 'does not cause any logical difficulties if we are given an enumeration mechanism.' It never defines what an enumeration mechanism is, nor proves that every finite sort of YAFOLL admits one. If a sort is presented by a comprehension term (for example, the set of elements satisfying a predicate p), enumerating it requires deciding p, and if p itself contains quantifiers including # or Σ, the enumeration can become circular or undecidable. Because the paper later states that the algorithmic semantics is 'easily programmed' and that # causes no algorithmic problems, this missing formalization is load-bearing for the paper's central algorithmic claim.
  2. [# - quantity quantifier] The abstract claims that # 'does not cause logical and algorithmic problems on finite structures,' yet the paper gives no algorithmic semantics for #. The only algorithmic-semantics section is devoted to ∀ and ∃; for #, the paper merely states that it 'returns the number of elements of sort s satisfy the predicate p,' with no counting algorithm, no treatment of partial predicates, and no argument that the count is always computable on the finite sorts of YAFOLL. This is an unsupported assertion rather than a demonstrated result, and it should either be proven or substantially qualified.
  3. [Σ - sum quantifier] The behavior of Σ is underspecified for partial functions and for empty sorts. The paper says that if s is empty or the function f is empty, 'Yp will display a No value message,' but it does not define what it means for f to be empty, nor does it specify what happens when f is undefined on a proper subset of s. In contrast, the ∀ and ∃ algorithms explicitly say what to do when f has no value on a given element, so the analogous case for Σ is missing and the semantics is incomplete.
minor comments (4)
  1. [Designations and values in YAFOLL] The paper relies on the YAFOLL language but does not summarize its syntax and semantics, so the definitions of terms, sorts, and functions are not self-contained for readers unfamiliar with the author's prior work.
  2. [Church quantifier - λ] The paper calls λ a 'Church quantifier' and says its meaning is 'Let's define!', which conflicts with the standard use of λ-abstraction already appearing later in the same section as λx:s.t; this overloading is likely to confuse readers.
  3. [# - quantity quantifier] The claim that in many formal theories # is 'only syntactic sugar' is made without a sketch of an elimination procedure or a reference, leaving the reader without a way to evaluate the assertion.
  4. [∀∃. Algorithmic semantics] The informal parenthetical remarks such as 'This is algorithmic semantics:-)' and 'new absolutely understandable subcommand...:-)' are out of place in a formal journal paper and should be removed or rephrased.

Circularity Check

0 steps flagged · score 0.0 of 10

No circularity: the quantifier semantics are stipulated definitions, not derived from their own conclusions.

full rationale

The paper's central move is definitional, not derivational. It stipulates that ∀(v)x:s f(x) means f is constant on s with value v, and ∃(v)x:s f(x) means v is in the image of f; the lambda-calculus section then rewrites the quantified term as a function definition and the quantifier as an operator on that function. These are explicit semantic conventions with a well-formedness constraint (the sort of v and the sort of t must coincide), not predictions fitted to or deduced from the target claims. The only self-citation, to the author's YAFOLL [1], fixes the host language and notation and is not load-bearing: the quantifier generalization, the # counting operator, and the algorithmic semantics are presented as new stipulations for that language rather than as consequences imported from [1]. No uniqueness theorem, ansatz, fitted parameter, or empirically calibrated quantity is invoked. The enumeration-mechanism assumption in the algorithmic-semantics section is a genuine unformalized precondition—the paper says 'if we are given an enumeration mechanism'—but this is an implementation/completeness caveat, not circularity, because the algorithms do not presuppose the truth of the quantifier claims they define. Thus no load-bearing step reduces to its own input by construction.

Assumptions & free parameters 0 free parameters · 5 assumptions · 2 invented entities

The paper introduces no fitted parameters. Its central proposal rests on domain assumptions about finite enumeration and the YAFOLL type system, plus standard lambda calculus. The two invented entities are syntactic constructs tied to the language and do not have independent falsifiable handles.

assumptions (5)
  • domain assumption Finite sorts can be effectively enumerated.
    Stated in the algorithmic semantics section: enumeration of elements of a finite sort does not cause logical difficulties if given an enumeration mechanism. This underpins the termination of the algorithms for ∀ and ∃.
  • domain assumption Quantifiers return a truth value (TV).
    Given in section '∀∃ with parameter': 'The sort of value of the quantifier itself is TV.'
  • standard math A term in a quantifier can be viewed as defining a function of the bound variable, possibly with external parameters.
    In section 'Function with external parameters. Transition to terms', the paper uses the standard lambda-abstraction property that any term in a variable defines a function.
  • ad hoc to paper The well-formedness constraint requires the parameter v and the term t to have the same sort.
    Introduced in 'Function with external parameters': 'There is also WFC (well-formedness constraint): the sort of v and the sort of value of t must be the same.' This type rule is specific to the proposed notation.
  • domain assumption Natural numbers are a subsort of rational numbers in YAFOLL.
    In section '# - quantity quantifier': 'In YAFOLL, natural numbers are considered part of the rational sort Number.'
invented entities (2)
  • Parameterized quantifier notation Q(v)x:s t
    purpose: Generalizes ∀ and ∃ so they check whether a function is constant with value v or contains v in its image.
    This syntactic construct is introduced in the paper as a generalization. No external falsifiable consequences are provided; it is a notation within YAFOLL.
  • Quantity quantifier #
    purpose: Counts the number of elements of a finite sort satisfying a predicate; used in definitions and queries.
    The paper introduces # as a new quantifier. While counting is a standard operation, the particular construct is a language addition with no independent empirical evidence.

how reviews work

0 comments
Cite this review

Pith. "Pith review of Quantifiers metamorphoses. Generalizations, variations, algorithmic semantics." pith.science (2026). https://pith.science/paper/ZAKAY4AG

@misc{pith2026190811342,
  author       = {Pith},
  title        = {Pith review of: Quantifiers metamorphoses. Generalizations, variations, algorithmic semantics},
  year         = {2026},
  howpublished = {\url{https://pith.science/paper/ZAKAY4AG}},
  note         = {Machine review of arXiv:1908.11342}
}
read the original abstract

This article contains ideas and their elaboration for quantifiers, which appeared after checking in practice the experimental language of the formal knowledge representation YAFOLL [1]: - looking at for_all and exists quantifiers as operators clarifying two trivial properties of a function: the constancy of result value and presence of a value in the result; -It turned out that the quantifier term can be written in the lambda calculus technique, i.e. as definition; -quantifier of quantity # is introduced into the language, as needed in practice and does not cause logical and algorithmic problems on finite structures; - the quantifier of the sum is mentioned because it is a quantifier of the language; -algorithmic semantics is written for for_all and exists quantifiers as an introduction to the topic.

Discussion (0). Continue with ORCID to comment.

Reference graph

Works this paper leans on

2 extracted references · 2 canonical work pages

  1. [1]

    [1] A. Shkotin. Finite Systems Handling Language (YAFOLL message 1), December 2015, Studia Humana 4(4). DOI: 10.1515/sh-2015-0021 https://www.researchgate.net/publication/307841408_Finite_Systems_Handling_Language_Y AFOLL_message_1 [2] OWL 2 Web Ontology

  2. [2]

    ​ https://www.w3.org/TR/owl-primer/

    Language, Primer (Second Edition), W3C Recommendation 11 December 2012. ​ https://www.w3.org/TR/owl-primer/

Pith tools

Reviewed August 14, 2026 · model on record in the stance chip above.