Implicative Verbs ([Nad23b]) #
Causal-prerequisite semantics for implicative verbs. Implicatives (manage, fail, dare, bother, jaksaa, hesitate, ...) all share a prerequisite-account schema (Proposal 32):
- (32i) Presuppose: ∃ prerequisite A(x) causally necessary for P(x)
- (32ii) Assert: x did A
- (32iii) Presuppose (two-way only): A(x) causally sufficient for P(x)
Lexical variation #
The chief dimension of variation is the type of prerequisite:
- dare/uskaltaa → courage
- bother/viitsiä → engagement/effort
- malttaa → patience
- hennoa → hard-heartedness
- jaksaa → strength
- manage/onnistua → underspecified
V2 substrate #
Polymorphic V2 forms over SEM V α. The legacy ImplicativeScenario
struct + manageSem/failSem over CausalDynamics,
PrerequisiteAccount, ConcreteExample (swim/manage), the
ComplementEntailing.CausalFrame abstraction (with abilityFrame/
viewpoint-aspect bridges), and Implicative.toSemantics over scenarios
were deleted in Phase D-H. The polymorphic V2 versions
(manageSem, failSem, necessityPresup, Implicative.toSemantics
dispatch) are promoted to canonical here.
Lexically-specified prerequisite types for implicative verbs.
Specific verbs (dare, bother) name their prerequisites; bleached verbs (manage, onnistua) leave the prerequisite underspecified.
- courage : Prerequisite
- engagement : Prerequisite
- patience : Prerequisite
- hardHeartedness : Prerequisite
- strength : Prerequisite
- fitness : Prerequisite
- time : Prerequisite
- shamelessness : Prerequisite
- unspecified : Prerequisite
Instances For
Equations
- Causation.Implicative.instDecidableEqPrerequisite x✝ y✝ = if h : x✝.ctorIdx = y✝.ctorIdx then isTrue ⋯ else isFalse ⋯
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
Is the prerequisite lexically specific or underspecified?
Equations
- Causation.Implicative.Prerequisite.unspecified.isSpecific = false
- x✝.isSpecific = true
Instances For
V2 manage-sem ([Nad23b] Definition 10a with the
Definition 10 preamble, over the strict T_D development):
prerequisite-as-xP is causally sufficient for complement-as-xC —
the background entails neither fact, and augmenting it with the
prerequisite causally entails the complement. Polymorphic over value
types.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
- Causation.Implicative.instDecidableManageSem M background prerequisite xP complement xC = Classical.dec (Causation.Implicative.manageSem M background prerequisite xP complement xC)
V2 fail-sem: prerequisite-as-xP is NOT causally sufficient for
complement-as-xC.
TODO: this is denial of the sufficiency presupposition, which is what
the Dreyfus infelicity judgments test, but it is NOT Proposal 32's
semantics for negative implicative assertions (assert ¬A(x) with
both presuppositions intact); the Features.Implicative.toSemantics
.negative dispatch below inherits the same caveat.
Equations
- Causation.Implicative.failSem M background prerequisite xP complement xC = ¬Causation.Implicative.manageSem M background prerequisite xP complement xC
Instances For
V2 necessity presupposition: prerequisite-as-xP is causally
necessary (Nadathur 2023 Def 10b) for complement-as-xC.
Equations
- Causation.Implicative.necessityPresup M background prerequisite xP complement xC = M.causallyNecessary background prerequisite xP complement xC
Instances For
[Nad23b] (pp. 316–317) takes Facts A–C as the class-level data any account of implicatives must derive. On the prerequisite account they fall out of the presupposition + assertion split of Proposal 32, for an arbitrary deterministic SEM:
- Fact B, positive half (
complement_of_positive_assertion): asserting the prerequisite realizes the complement — the sufficiency presupposition's entailment clause. - Fact B, negative half (
no_complement_of_negative_assertion): given the necessity presupposition, the negative assertion leaves no consistent completion realizing the complement. - Fact C (
complement_iff_prerequisite): in a felicitous two-way context the prerequisite is sufficient and necessary — a consistent completion realizes the complement exactly when it realizes the prerequisite.
Fact A (the existence of a potential obstacle, blocking the entailment
from complement to implicative claim) is carried by the presuppositional
preamble itself (SEM.causallyNecessary.precondition).
Fact B, positive half: a positive two-way implicative claim entails its complement — the background updated with the asserted prerequisite causally entails the complement.
Fact B, negative half: given the necessity presupposition, a
negative implicative claim (asserting the prerequisite took a value
other than xP) leaves no consistent completion realizing the
complement: by no-alternative, every consistent path to the
complement runs through the prerequisite value the assertion denies.
Fact C: in a felicitous two-way context (both presuppositions in
force), a consistent completion of the background realizes the
complement exactly when it realizes the prerequisite. The forward
direction is no-alternative; the converse composes the sufficiency
clause with causallyEntails_mono (determinations cannot be undone).
The two-way entailment profile — [Kar71]'s defining criterion for the manage class — follows from the prerequisite account: in a context satisfying both presuppositions, the positive assertion entails the complement (Fact B, positive) and any negative assertion precludes it in every consistent completion (Fact B, negative). This is the derivation [Nad23b] advertises for Facts A–C at the class level.
Directionality of complement entailment ([Nad23b]).
- oneWay: complement entailment under only one matrix polarity.
- twoWay: complement entailment under both polarities.
- oneWay : Directionality
- twoWay : Directionality
Instances For
Equations
- Causation.Implicative.instDecidableEqDirectionality x✝ y✝ = if h : x✝.ctorIdx = y✝.ctorIdx then isTrue ⋯ else isFalse ⋯
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
The full lexical signature of an implicative verb ([Nad23b]).
- polarity : Features.Implicative
Positive (manage, force) or negative (fail, prevent) polarity
- directionality : Directionality
One-way (ability) or two-way (manage) entailment
- aspectGoverned : Bool
Does aspect govern the actuality inference?
- prerequisite : Option Prerequisite
Lexically-specified prerequisite type (if any)
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
- Causation.Implicative.ImplicativeClass.ability = { polarity := Features.Implicative.positive, directionality := Causation.Implicative.Directionality.oneWay, aspectGoverned := true }
Instances For
Equations
- Causation.Implicative.ImplicativeClass.enough = { polarity := Features.Implicative.positive, directionality := Causation.Implicative.Directionality.oneWay, aspectGoverned := true }
Instances For
Equations
- Causation.Implicative.ImplicativeClass.too = { polarity := Features.Implicative.negative, directionality := Causation.Implicative.Directionality.oneWay, aspectGoverned := true }
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
Lives here rather than in Features/Causation.lean because the
dispatch needs Causation.SEM + the Implicative.manageSem/failSem
machinery defined above; Features/Causation.lean is kept import-free.
Standard mathlib pattern: methods on a type may live in a sibling
file via namespace TypeName block when import weight matters.
V2 dispatch: map an Implicative polarity to its V2 polymorphic
semantic function.