Speech Act Clarification¶
Essence¶
Speech-Act Clarification is the intervention pattern for moments when words do more than describe. A statement can create an obligation, refuse a request, authorize a release, assign work, provide consent, issue an apology, close a decision, waive a right, or change an institutional state. The core question is not only “what did the words mean?” but “what did the words do?”
This archetype makes the action force of an utterance explicit. It asks what act was performed, who had standing to perform it, who needed to recognize it, what consequence follows, and how to repair the situation if those elements do not align.
Compression statement¶
When language creates obligations, permissions, requests, commitments, approvals, refusals, apologies, declarations, or status changes, clarify the performed act, standing, uptake, consequences, and repair path so participants do not coordinate around different interpretations of the same words.
Canonical formula: utterance + act_type + standing + uptake + consequence_record + repair_path -> reliable language-as-action
When to Use This Archetype¶
Use this archetype when a communicative expression has consequences. The expression may be spoken language, written policy, a signature, a click, a workflow approval, a meeting statement, a public declaration, or a ceremonial phrase. It applies when people could plausibly disagree about whether the expression was a suggestion, order, promise, refusal, consent, waiver, approval, decision, apology, or formal declaration.
It is especially useful where ambiguity creates accountability gaps: meetings where “we should” becomes an unclear assignment, contracts where notice or acceptance depends on the right language, consent processes where “yes” must be scoped and voluntary, or customer-support interactions where sympathy is confused with a refund promise.
Structural Problem¶
The structural problem is a mismatch between sentence content and performed action. Participants hear the same utterance but attach different consequences to it. One person hears “I’ll look into it” as a firm commitment; another hears it as tentative intent. One team hears “approved” as authorization to proceed; another sees it as an informal opinion. One party treats silence as consent while another treats it as non-response.
This mismatch happens because communication carries several layers at once. Words have literal content, social relationship meaning, institutional standing, and action force. When the action layer remains implicit, the utterance becomes a weak substitute for a decision record, consent process, commitment register, or authority check.
Intervention Logic¶
The intervention begins by capturing the actual utterance or expression. Then it names the plausible act types the expression could perform. Once the options are visible, the drafter, facilitator, designer, or decision owner states the intended performed action. Next, the intervention checks whether the speaker or system had standing to perform that act and whether the relevant audience recognized it. Finally, it records the consequence and defines a repair path if interpretation diverged.
The pattern works by separating five questions that are often collapsed: What was said? What act was performed? Who had authority to perform it? Who had to recognize it? What consequence now follows?
Key Components¶
Speech-Act Clarification makes the action force of an utterance explicit, so participants do not coordinate around different interpretations of the same words. The pattern grounds analysis in the Utterance itself — the exact sentence, signature, click, approval comment, or recorded declaration whose force matters — preventing drift into speculation about what someone probably intended. The Speech Act Type classifies what action the utterance performed: request, order, promise, consent, refusal, apology, approval, warning, declaration, notice, waiver, or decision. The Intended Performed Action states in operational language what the speaker meant to accomplish, replacing vague claims about helpfulness with concrete claims about commitments made or work assigned. Authority or Standing then asks whether the speaker, role, system, or process actually had the recognized capacity to perform that act, because the right words spoken from the wrong position do not bind.
The remaining components close the loop between speaker and consequence. The Audience or Counterparty names who must receive, understand, accept, or act on the speech act, since a request needs a recipient and consent needs a party who recognizes the scope. Uptake Confirmation verifies that the relevant audience actually recognized which act occurred and what follows — distinguishing assumed hearing from confirmed understanding through readback, acknowledgment, or countersignature when stakes warrant. The Consequence Record captures what the utterance changed in the world: an obligation, permission, refusal, deadline, status change, or revocation window. When interpretations diverge, the Speech-Act Mismatch Source diagnoses why — indirect wording, unclear authority, power differences, missing records, ambiguous rituals, or politeness strategies — and the Repair Action corrects the failed act by restating, retracting, voiding, downgrading, or recording a corrected decision before unreliable acts harden into disputes.
| Component | Description |
|---|---|
| Utterance ↗ | The utterance is the exact expression whose force matters: a sentence, signature, click, approval comment, meeting phrase, public statement, or recorded declaration. Starting from the actual expression prevents the analysis from drifting into speculation about what someone “probably intended.” |
| Speech Act Type ↗ | The speech act type classifies the action performed by the utterance. Common types include request, order, promise, consent, refusal, apology, approval, warning, declaration, notice, waiver, and decision. This is the central component because different act types create different expectations and obligations. |
| Intended Performed Action ↗ | The intended performed action states what the speaker, writer, signer, or system meant to accomplish by issuing the utterance. It should be operational rather than psychological. “They wanted to be helpful” is less useful than “they promised to refund the fee” or “they assigned ownership of the task.” |
| Authority or Standing ↗ | Authority or standing asks whether the person, role, office, system, or process can validly perform the act. A person can say “approved,” but the utterance may not authorize action if that person lacks approval authority. A declaration may be ceremonial, advisory, or binding depending on recognized standing. |
| Audience or Counterparty ↗ | The audience or counterparty is the person or group that must receive, understand, accept, or act on the speech act. A request needs a recipient. Consent needs a party who recognizes the scope. A notice may require delivery to a specified counterparty. A declaration may require public or procedural uptake. |
| Uptake Confirmation ↗ | Uptake confirmation verifies that the relevant audience recognized which act occurred and what follows. It is the difference between assuming that people heard a statement and confirming that they understood it as a decision, assignment, refusal, consent, or commitment. |
| Consequence Record ↗ | The consequence record captures what the utterance changed. It may record an obligation, permission, refusal, approval, deadline, owner, status change, apology condition, or revocation window. A good record says not only what was said but what action was performed by saying it. |
| Speech-Act Mismatch Source ↗ | The mismatch source diagnoses why interpretations diverged. Common sources include indirect wording, unclear authority, power differences, missing records, ambiguous rituals, role confusion, politeness strategies, or conflicting institutional norms. |
| Repair Action ↗ | The repair action corrects a failed or disputed speech act. Repair can mean restating the act, confirming uptake, retracting a claim, voiding an invalid approval, downgrading an order to a request, recording a corrected decision, or reopening consent. |
Common Mechanisms¶
| Mechanism | Description |
|---|---|
| Commitment Register ↗ | A commitment register implements the archetype by recording who committed to what, under what scope, and by when. It is not the archetype itself; it is a mechanism for cases where the speech act creates an obligation that must survive beyond the conversation. |
| Meeting Action-Item Capture ↗ | Meeting action-item capture turns ambiguous meeting language into explicit decisions, owners, and deadlines. It implements Speech-Act Clarification when it distinguishes an idea from a decision and a casual offer from an accepted assignment. |
| Consent Confirmation Form ↗ | A consent confirmation form implements the archetype for consent acts. It only works if it checks the validity conditions of the act: standing, information, voluntariness, scope, and uptake. The form alone is not enough. |
| Formal Declaration Record ↗ | A formal declaration record implements the archetype when a recognized utterance changes status: closing a vote, appointing a role, authorizing a transition, accepting a resignation, or declaring a process complete. |
| Request / Order Clarification Prompt ↗ | This mechanism asks participants to name whether a statement is a request, recommendation, assignment, or command. It is useful when power differences or polite wording obscure whether compliance is optional. |
| Readback Confirmation ↗ | Readback confirmation asks the recipient to restate the performed act and expected response. It is common in safety, operations, medicine, incident response, and high-stakes coordination because it catches false uptake immediately. |
| Apology / Repair Protocol ↗ | An apology or repair protocol helps distinguish sympathy, acknowledgment, responsibility-taking, restitution, commitment to change, and closure. It implements the archetype by clarifying what the apology is meant to do, not by providing polite words alone. |
| Contract Speech-Act Clause ↗ | A contract clause can specify what counts as notice, acceptance, waiver, approval, termination, representation, warranty, or binding commitment. It implements the archetype in legal language by tying words to recognized consequences. |
| Authority Matrix ↗ | An authority matrix maps who may approve, decide, bind, consent, publish, or declare on behalf of a group. It supports the authority_or_standing component so that action-force clarification does not accidentally validate unauthorized speech. |
Parameter / Tuning Dimensions¶
The first tuning dimension is act explicitness. Low-stakes settings may need a simple clarification such as “Is that a decision or a suggestion?” High-stakes settings may need formal act labels, records, signatures, and review.
The second dimension is authority formality. A small team can rely on informal standing for many acts, while legal, medical, financial, safety, and governance settings often need explicit authority checks.
The third dimension is uptake strength. Passive receipt may be enough for ordinary information, but consequential acts may require readback, countersignature, acknowledgment, or recorded acceptance.
The fourth dimension is consequence visibility. Some consequences can remain local to a conversation. Others need durable records because other parties, auditors, systems, or future decision-makers will rely on them.
The fifth dimension is repair window. Some acts need immediate correction only; others need a defined revocation, appeal, reconsideration, or correction period.
The sixth dimension is directness versus face preservation. The wording can be tactful, but the performed act still needs to be clear. A softened order, refusal, or criticism should not become ambiguous merely to preserve harmony.
Invariants to Preserve¶
The most important invariant is shared action force. The same utterance should not silently count as different acts for different participants in the same consequential setting.
A second invariant is valid standing. Authority-sensitive acts should not be treated as binding unless the speaker, role, process, or system has recognized standing.
A third invariant is recoverable consequence. Affected parties should be able to tell whether they are obligated, permitted, refused, released, assigned, warned, approved, or merely informed.
A fourth invariant is repairability. If wording, standing, uptake, or records are defective, the system should have a way to correct the act before reliance grows.
Target Outcomes¶
The target outcome is fewer disputes about what happened by means of language. Teams should know whether a decision was made. Parties should know whether consent, notice, acceptance, waiver, or refusal occurred. Organizations should know who made a binding commitment and who had authority to make it.
A second outcome is clearer accountability. Once the performed act and consequence are explicit, people can follow through, contest validity, repair misunderstanding, or hold the right party responsible.
A third outcome is better procedural integrity. Speech acts that affect rights, duties, roles, resources, or status become checkable rather than hidden inside conversational phrasing.
Tradeoffs¶
The main tradeoff is explicitness versus fluidity. If every utterance is labeled and recorded, communication becomes stiff. If consequential utterances are never labeled, obligations and decisions become unreliable.
Another tradeoff is record strength versus trust. Records support accountability, but over-recording can signal suspicion or chill exploratory discussion. The solution is to scale the mechanism to the consequence.
A third tradeoff is authority checking versus local autonomy. Standing checks prevent invalid acts, but too many checks can disempower people who need to act. Good use of this archetype distinguishes high-stakes binding acts from ordinary coordination.
A fourth tradeoff is repairability versus finality. A correction window protects against misunderstanding, but unlimited correction undermines reliance on decisions, commitments, or consent.
Failure Modes¶
A common failure mode is content-only interpretation. People analyze what the sentence literally said but never clarify whether it performed a decision, promise, order, or consent.
A second failure mode is invalid authority. A person says the right words but lacks standing to approve, bind, declare, or consent. The mitigation is an explicit authority check.
A third failure mode is false uptake. A speaker assumes the act was recognized because the recipient heard the words. The mitigation is confirmation, readback, acknowledgment, or countersignature when stakes warrant.
A fourth failure mode is polite ambiguity. Indirect wording may preserve face but obscure whether something is optional, expected, or required. The mitigation is to keep tactful language while naming the action force.
A fifth failure mode is mechanism substitution. A form, script, clause, or template is treated as proof that a valid act occurred. The mitigation is to check act type, standing, scope, uptake, and consequence rather than relying on the artifact alone.
Neighbor Distinctions¶
Speech-Act Clarification is distinct from Sign–Meaning Alignment. Sign–Meaning Alignment asks whether a sign evokes the intended concept. Speech-Act Clarification asks whether an utterance performed a specific action.
It is distinct from Polysemy Disambiguation. Polysemy Disambiguation clarifies which sense of a term is active. Speech-Act Clarification clarifies whether the language was a promise, order, refusal, approval, consent, or declaration.
It is distinct from Semantic Drift Monitoring. Semantic Drift Monitoring tracks meaning change over time. Speech-Act Clarification resolves present action force and validity.
It is related to Context Anchor Design because speaker, time, role, and situation can determine the force of an utterance. But context anchoring resolves references; speech-act clarification resolves actions and consequences.
It is related to decision-rights and consent governance, but narrower. Decision-rights work allocates who may decide. Consent governance manages the broader conditions for valid consent. Speech-Act Clarification focuses on the utterance or expression that purports to perform the act.
Variants and Near Names¶
Important variants include commitment-act clarification, request/order distinction, consent uptake confirmation, declarative status-change clarification, and apology/repair act clarification. Each variant preserves the same structure: utterance, act type, standing, uptake, consequence, and repair.
Near names include Language-as-Action Clarification, Performative Utterance Clarification, Action Force Clarification, Commitment Language Clarification, and Declaration Clarification. These names should be retained for search and aliasing, but they should not create duplicate archetypes.
Performative Boundary Setting remains a merge-review candidate. It may deserve separate treatment later if formal declarations that create or close social states prove to have distinct components and failure modes. For now, it is captured as a declaration/status-change variant under this archetype.
Cross-Domain Examples¶
In a project meeting, a facilitator can ask whether “let’s do this” is a decision, recommendation, or proposed next step. The clarification prevents one person from leaving with an assignment while another leaves with an idea.
In contract drafting, a clause can state exactly what language or notice performs acceptance, waiver, approval, or termination. The point is not ornate legal wording; it is explicit linkage between utterance and consequence.
In healthcare, a patient’s “yes” must be clarified as consent to a specific procedure under specific information and scope conditions. Mere agreement that the doctor explained something is not the same as consent to proceed.
In customer support, “sorry about that” may perform sympathy, but “we will refund the fee” performs a commitment. Distinguishing the two prevents false promises and inadequate repair.
In interface design, a button can perform an act: submitting, deleting, authorizing, accepting terms, or purchasing. Speech-Act Clarification pushes the design to show what action the click performs before the user is bound by it.
Non-Examples¶
A confusing icon is not Speech-Act Clarification unless the icon or click performs a consequential act. Otherwise it belongs under Sign–Meaning Alignment or sign-type design.
A word with multiple meanings is not automatically Speech-Act Clarification. If the problem is choosing which sense of “model,” “client,” or “active” applies, use Polysemy Disambiguation.
A historical change in the meaning of a term is not this archetype. Use Semantic Drift Monitoring.
A desire to make language more polite is not enough. Politeness matters here only when it changes or obscures whether the utterance is a request, order, refusal, apology, commitment, or other act.