Quantified Claim Template¶
Documentation template — instantiates Claim Quantifier Scope Calibration
A fill-in-the-blanks record that captures a claim's quantifier, domain, predicate, and counting basis in one auditable form.
Before a quantified claim can be reviewed for force, searched for counterexamples, or pinned to a threshold, it has to be written down in parts. Quantified Claim Template is that first artifact: a structured form with a slot for the quantifier, the domain it ranges over, the predicate being asserted, and the counting or measure basis — the raw QDPM record every other mechanism in this archetype consumes. Its defining move is that it is deliberately neutral: it does not judge whether the claim is too strong, whether the domain is apt, or whether the evidence suffices. It only ensures the claim is decomposed into its load-bearing fields so those judgments have something explicit to bite on. A claim that resists being filled into the template — where nobody can say what the domain is — has failed the cheapest possible test, and that failure is itself the finding.
Example¶
A product analyst drafts a line for a quarterly decision memo: "Most churned users never onboarded." Persuasive, and completely unaudited. Dropped into the template, it separates into fields. Quantifier: "most" (a majority token, flagged for later threshold work). Domain: which users — everyone who ever signed up, or accounts that churned in Q3? Fixed to accounts that cancelled in Q3. Predicate: "never onboarded," which must itself be defined — never completed the setup wizard. Measure basis: churned users counted as distinct cancelled accounts, onboarding measured by the wizard-completion event. Filling the form surfaces immediately that "never onboarded" was doing undefined work and that "most" had no denominator yet. The template does not resolve those — it hands the "most" to the most-threshold statement and the wobbly predicate to a predicate check — but it has turned a slogan into a claim with named, inspectable parts. The memo now carries the record, not just the sentence.
How it works¶
- Slot the quantifier. Record the claim's quantifier token verbatim (all, most, some, none, exactly N), including the pragmatically implied one when the grammar omits it.
- Name the domain. Write the population the quantifier ranges over as an explicit set, converting an assumed "users" into a defined membership.
- State the predicate. Capture the property being asserted of domain members, flagging any term that is itself undefined.
- Fix the basis. Note how membership and the predicate are measured or counted, so downstream mechanisms inherit a consistent unit.
Tuning parameters¶
- Field completeness — whether every slot is mandatory or some may be left "unspecified — needs work." Mandatory slots force rigor but stall on genuinely open questions; optional slots keep the form moving but let gaps hide.
- Granularity — one template per atomic claim versus one covering a compound sentence. Splitting compound claims prevents a single record from smuggling two quantifiers, at the cost of more forms.
- Verbatim vs. normalized — whether the quantifier is recorded as spoken or mapped to a canonical token set. Normalization aids downstream tooling but can erase a nuance ("virtually all" flattened to "most").
- Handoff routing — how aggressively filled fields are dispatched to the specialist mechanisms (threshold, witness, exhaustion) that act on them.
When it helps, and when it misleads¶
Its strength is that it is the cheap, upstream discipline that makes everything downstream possible: a claim decomposed into quantifier, domain, predicate, and basis can be audited; a claim left as prose cannot. It plays for quantifiers the role the Toulmin model[n1] plays for arguments generally — forcing the hidden parts into named slots.
Its failure mode is the false comfort of a filled form: completing every slot proves the claim is well-formed, not well-supported or true. A tidy template can hold a precisely specified falsehood, and the neatness invites readers to skip the harder mechanisms that test force, coverage, and evidence. The classic misuse is treating documentation as validation — citing "it's in the template" as if structure were substantiation. The guarding discipline is to route every filled template onward: the form is the entry point to the archetype's checks, never a substitute for them.
How it implements the components¶
quantifier_token_record— it records the claim's quantifier token, the anchor field the whole form is built around.domain_of_quantification— it captures the population the quantifier ranges over as an explicit set.predicate_under_quantification— it states the property asserted of domain members.measure_or_count_basis— it notes the unit by which membership and predicate are measured.
It deliberately stops at recording: it does not test the support_burden_rule, apply a counterevidence_consequence_rule, or set a threshold_statement — those are the jobs of the claim strength ladder review, universal counterexample test, and most-threshold statement that consume this record.
Related¶
- Instantiates: Claim Quantifier Scope Calibration — supplies the base claim record the whole appraisal is built on.
- Sibling mechanisms: Most-Threshold Statement · Claim Strength Ladder Review · Nested Quantifier Parse · Exact-N Count Audit
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Quantified Claim Template operates by externalizes a claim's quantifier, domain, predicate, and counting basis in a persistent fill-in template. That concrete deployed or enacted form is Representation, Specification & Plan under the frozen taxonomy.
Nearest alternative: Interface, Display & Cue — Although Interface, Display & Cue can support this mechanism, the frozen evidence makes its operative form the act that externalizes a claim's quantifier, domain, predicate, and counting basis in a persistent fill-in template; the alternative is therefore secondary rather than defining.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Philosophy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Explicitly recording quantifier, domain, predicate, and counting basis descends from formal logic and philosophy of language.
Related originating lineages:
- Linguistics & Semiotics — Natural-language quantification and scope analysis shaped detection of ambiguous claims.
- Mathematics — Formal logic and set-theoretic domains supplied exact quantified notation.
- Statistics & Experimental Design — Counting bases and population definitions supplied the empirical operationalization.
Review resolution: Both blind reviewers agree on philosophy as the primary origin. Explicit reconciliation resolves reported_ambiguity, alternate_origin_disagreement. The merged alternate lineages retain only domains the reviewers identified as materially formative; domain_reach=universal records later applicability separately from origin breadth.
Attribution caveat: The fill-in template is an encyclopedia operationalization of logical claim structure. The fill-in template is an encyclopedia synthesis of logical and measurement disciplines.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
This template is the archetype's entry point: nearly every sibling mechanism consumes its output rather than re-parsing the raw sentence. Keeping it strictly a recording artifact — no judgment baked in — is what lets the specialist mechanisms disagree with each other about force, coverage, and evidence while sharing one agreed decomposition of what the claim actually says.
[n1] The Toulmin model of argument decomposes a claim into named parts — grounds, warrant, backing, qualifier, rebuttal — so each can be examined separately. The template does the same service specifically for the quantifier structure of a claim. ↩