The ASSERT Operator and Speech Act Phrase #
@cite{hacquard-2006}
Formalizes the Speech Act Phrase (SAP) from @cite{hacquard-2006}. Every matrix clause is headed by a SAP that introduces a speech event e* with propositional CONTENT. The type of speech act determines the content:
- Declarative: CON(e*) = speaker's beliefs → epistemic R
- Imperative: CON(e*) = addressee's to-do list → deontic R
- Interrogative: CON(e*) = question content
Architectural Significance #
EventBinder.speechAct.hasContent = true is currently stipulated in
EventRelativity §8. This file DERIVES that fact: ASSERT introduces
a speech event, and all speech events carry propositional content
(that is what makes them speech acts). Content licensing then follows:
the speech event is contentful → epistemic R can project from it.
Connection to EventRelativity #
The speech event's content IS the conversational background that a
modal bound to e* accesses. In the AnchoringFn framework:
anchor f e* = CON(e*)
Different speech act types give different CON(e*), hence different modal flavors — without lexical ambiguity in the modal.
The type of speech act heading the Speech Act Phrase.
@cite{hacquard-2006}: "The content of the speech event is different depending on the type of speech act."
Now unified with IllocutionaryMood from Core.Discourse. The five
constructors — declarative, interrogative, imperative, promissive,
exclamative — classify the pragmatic act performed.
Instances For
All speech acts are contentful events. This is definitional: a speech act IS the performance of propositional content.
This derives EventBinder.speechAct.hasContent = true: the speech
event introduced by SAP always carries content, hence it can always
project epistemic R (content licensing, EventRelativity §8).
Equations
Instances For
The primary modal flavor licensed by each speech act type.
- Declarative → epistemic: the content is the speaker's beliefs, so R accesses what the speaker considers possible.
- Imperative → deontic: the content is the addressee's obligations, so R accesses what is permitted/required.
- Promissive → deontic: the content is the speaker's commitments, paralleling imperative.
Equations
- Semantics.Modality.Assert.primaryFlavor Core.Discourse.IllocutionaryMood.declarative = Core.Modality.ModalFlavor.epistemic
- Semantics.Modality.Assert.primaryFlavor Core.Discourse.IllocutionaryMood.imperative = Core.Modality.ModalFlavor.deontic
- Semantics.Modality.Assert.primaryFlavor Core.Discourse.IllocutionaryMood.promissive = Core.Modality.ModalFlavor.deontic
- Semantics.Modality.Assert.primaryFlavor Core.Discourse.IllocutionaryMood.interrogative = Core.Modality.ModalFlavor.epistemic
- Semantics.Modality.Assert.primaryFlavor Core.Discourse.IllocutionaryMood.exclamative = Core.Modality.ModalFlavor.epistemic
Instances For
A speech act event e* with its content CON(e*).
This is what the Speech Act Phrase introduces at the top of every
matrix clause. The content field is the conversational background
that modals in the clause can bind to (@cite{hacquard-2006}, (219)–(222)).
- actType : SpeechActType
The type of speech act
CON(e*): the propositional content of the speech event. Maps each world to the set of propositions encoding the content.
Instances For
ASSERT: introduce a declarative speech event.
(222) SPEECH ACT_DECLARATIVE(e*):
The content encodes the speaker's beliefs — worlds compatible with
what the speaker takes to be true.
Equations
- Semantics.Modality.Assert.ASSERT beliefs = { actType := Core.Discourse.IllocutionaryMood.declarative, content := beliefs }
Instances For
DIRECT: introduce an imperative speech event.
The content encodes the addressee's to-do list — worlds compatible with the addressee fulfilling their obligations.
Equations
- Semantics.Modality.Assert.DIRECT obligations = { actType := Core.Discourse.IllocutionaryMood.imperative, content := obligations }
Instances For
A speech act event's content IS a conversational background.
SpeechActEvent.content : W → List (BProp W) has the same type as
a Kratzer ConvBackground and as anchor f e from EventRelativity §10.
The speech event's content is the background that modals in its scope
access when they bind to e*.
Equations
- sa.toBackground = sa.content
Instances For
Lift a speech act event into an anchoring function.
Given a speech act event sa, we construct an AnchoringFn where:
- The speech event (
.inl) maps to sa's content - Any described event (
.inr ev) maps to the described event's own background.
This models the clause structure: the speech event anchoring is provided by ASSERT at the top; the described event anchoring comes from the verb's event structure lower in the clause.
Equations
- Semantics.Modality.Assert.speechActAnchoring sa describedBg (Sum.inl PUnit.unit) x✝ = sa.content x✝
- Semantics.Modality.Assert.speechActAnchoring sa describedBg (Sum.inr ev) x✝ = describedBg ev x✝
Instances For
The speech event slot of speechActAnchoring reduces to the
speech act's content.
The described event slot passes through to the verb's background.
EventRelativity §8 stipulates EventBinder.speechAct.hasContent = true.
With the SAP formalization, this becomes derivable:
- Every matrix clause has a SAP.
- SAP introduces a speech event e*.
- e* carries CON(e*) (the speech act's propositional content).
- Therefore e* is contentful.
- Therefore epistemic R can project from e* (content licensing).
The bridge theorems below make this derivation explicit.
All speech act types are contentful — by definition, performing a speech act involves producing propositional content.
ASSERT produces a contentful event.
DIRECT produces a contentful event.
Speech act contentfulness agrees with EventBinder.speechAct.hasContent.
This is the key bridge: the stipulated fact in EventRelativity §8
(EventBinder.speechAct.hasContent = true) is justified by the SAP
analysis — ASSERT always introduces a contentful event.
Declarative speech acts license epistemic modals.
Imperative speech acts license deontic modals.
Different speech act types yield different primary flavors for the same modal. This derives the "must" ambiguity:
- "John must be home" (declarative) → epistemic necessity (CON(e*) = speaker's beliefs → must = "given my evidence")
- "Go home!" (imperative) → deontic necessity (CON(e*) = to-do list → must = "you are required to")
Same modal, different speech acts, different readings. No lexical ambiguity needed.
Two contexts for "You can leave":
Declarative (informing): "Based on what I know, it's possible you'll leave." ASSERT introduces e* with content = speaker's evidence. The modal accesses epistemic R. Staying is also possible.
Imperative (permitting): "You have permission to leave." DIRECT introduces e* with content = addressee's permissions. The modal accesses deontic R. Staying is NOT permitted.
The difference: same modal "can" (◇), but different speech events yield different accessible worlds.
Equations
- Semantics.Modality.Assert.instBEqLeaveWorld.beq x✝ y✝ = (x✝.ctorIdx == y✝.ctorIdx)
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
Declarative context: speaker's evidence is compatible with both outcomes (speaker doesn't know whether the addressee will leave).
Equations
Instances For
Imperative context: permission to leave — only leave-world is compatible with the addressee's permissions.
Equations
- One or more equations did not get rendered due to their size.
Instances For
The two speech acts have different types.
Under the declarative, both leaving and staying are possible (speaker is uncertain).
Under the imperative, leaving is permitted but staying is NOT.
The core contrast: same modal (◇), same proposition (stay), same evaluation world — but different speech acts yield different truth values. The speech act type, mediated through CON(e*), determines the modal domain.
The speech event projects to an individual-time pair via
EventProjection (EventRelativity §11):
| Speech act | holder(e*) | τ(e*) |
|---|---|---|
| Declarative | speaker | speech time |
| Imperative | addressee | speech time |
The holder determines WHOSE propositional attitudes are relevant:
- Declarative: speaker's beliefs (epistemic = "what I know")
- Imperative: addressee's obligations (deontic = "what you must do")
Both share the same time (speech time = now), but the different holders yield different content types.
Speaker and addressee for the projection example.
- speaker : Interlocutor
- addressee : Interlocutor
Instances For
Equations
- Semantics.Modality.Assert.instBEqInterlocutor.beq x✝ y✝ = (x✝.ctorIdx == y✝.ctorIdx)
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
- Semantics.Modality.Assert.instBEqSpeechTime.beq x✝ y✝ = (x✝.ctorIdx == y✝.ctorIdx)
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
The event projection for speech act events.
Declarative: holder = speaker (it's the speaker's beliefs). Imperative: holder = addressee (it's the addressee's obligations).
NB: .interrogative =>.speaker because the holder is who PERFORMS the
speech act (always the speaker in Hacquard's framework). This is distinct
from the SEAT OF KNOWLEDGE, which is the hearer for
interrogatives — that notion captures who has epistemic authority over
the content, not who initiates the speech event. The bridge between these
is in SpeechActs.lean: seat_of_knowledge_agrees_with_epistemic_authority.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Declarative projects to (speaker, now).
Imperative projects to (addressee, now).
Different speech act types project to different holders. The holder determines whose attitudes provide the modal content: speaker's beliefs (epistemic) vs addressee's obligations (deontic).