Pragmatic Force Walkthrough¶

Interpretive walkthrough — instantiates Context-Bounded Meaning Recovery

Recovers what an utterance is doing — asserting, ordering, promising, warning, joking — by walking its literal content through the situation and conventions that fix its force.

The Pragmatic Force Walkthrough reads for what a message does, not just what it says. Its distinctive concern is illocutionary force — whether a given string is functioning as an assertion, an order, a promise, a warning, a joke, or a threat — which the literal words underdetermine and which only the situation and the operative conventions fix. It walks a specific utterance step by step through its context (who is speaking to whom, when, where, with what shared knowledge and deixis) and the pragmatic conventions in force (genre, register, politeness codes, and what is implied by saying this rather than the expected thing), to recover the act being performed. Where other mechanisms ask what the substrate means, this one asks what it is doing to its audience — and, crucially, it preserves the cases where the force is deliberately left plural.

Example¶

A moderation queue surfaces a post: "Nice shop. Be a shame if something happened to it." Read literally it pairs a compliment with a vague possibility — harmless. The walkthrough recovers its force instead. Context anchors: the author is replying to a small business that just refused them a refund; the platform is a public review page; the two have a prior thread. Conventions in play: the sentence is a recognizable extortion trope whose genre convention converts a "shame if…" construction into a conditional threat — the politeness surface is exactly the tell. Walking content through that context and those conventions, the force resolves as a veiled threat, not a compliment — an illocutionary act the literal parse never contained.^[1]

The walkthrough also records the residual ambiguity honestly: the same words, from a regular with a joking history and no dispute, could be banter. So the preserved note reads "threatening force is context-dependent; absent the refund dispute this reading weakens" — which is what lets a reviewer apply the right standard rather than a keyword rule.

How it works¶

Fix the deictic context. Resolve who, to whom, when, where, and against what shared knowledge — the indexical anchors a literal reading floats free of.
Load the conventions. Name the genre, register, and pragmatic rules in force, including what saying this implies by departing from what was expected (implicature).
Walk content → act. Step the utterance through context and convention to name the act it performs — assert, direct, commit, express, declare, or their indirect and non-literal cousins.
Preserve plural force. Where the act is genuinely indeterminate or strategically deniable, record the ambiguity and its context-dependence rather than forcing a single label.

Tuning parameters¶

Context radius — how much surrounding situation to admit (this message vs. the whole thread and relationship history). Wider radius recovers force more reliably but risks importing assumptions the utterance doesn't warrant.
Convention specificity — how local the operative code is (broad speech-act types vs. a niche community's in-jokes). More specificity catches insider force but travels badly to outsiders.
Literal ↔ intended balance — how far to privilege sentence meaning over speaker meaning. Leaning literal under-reads sarcasm and threats; leaning intended over-reads and imputes acts never performed.
Ambiguity tolerance — whether to force a single force-label or preserve a deliberate plurality. Forcing resolution aids action; preserving it protects against over-charging strategic deniability.
Uptake weighting — how much the audience's actual reception counts toward the force. Heavy weighting grounds the reading in effect; too heavy lets the most sensitive reader define the act.

When it helps, and when it misleads¶

Its strength is recovering meaning that lives entirely in use — the threat dressed as a compliment, the order phrased as a question, the promise smuggled into small talk — that any content-only reading misses by construction. It is the mechanism that stops a literal filter from clearing a veiled threat and stops a nervous one from convicting a joke, by making the situational and conventional grounds of the force explicit and inspectable.

Its failure modes come from the same power. Force is context-hungry, so the walkthrough can over-read — manufacturing an illocutionary act from an innocent string by importing a hostile frame — or under-read by missing a convention the interpreter doesn't share. Reading force also shades toward reading intent, which the substrate rarely settles; treating a recovered force as proven intent is the classic overreach, and it is why the honest output is the act performed-in-context, not a mind-read. The discipline that guards against this is to bind every force claim to a named context anchor or convention, to keep the literal reading visible beside the pragmatic one, and to preserve — not resolve — the plural cases where deniability is real.

How it implements the components¶

The Pragmatic Force Walkthrough realizes the meaning-in-use side of the archetype — turning situation and convention into an act:

context_anchor_set — resolves the speaker, audience, moment, and shared knowledge (the deixis) that a literal reading leaves unfixed.
constraint_and_convention_map — brings the genre, register, politeness, and implicature conventions to bear that convert content into an act.
ambiguity_preservation_note — records strategically or genuinely plural force instead of collapsing it to one label.

It does not trace claims to textual marks (evidence_mark_trace — the Evidence-to-Claim Matrix), choose the interpretive framework (framework_selection_rule — the Framework Selection Memo), or test whether the audience actually took the force as read (validation_or_uptake_check — the Stakeholder Meaning Check). It consumes a reconstructed context and reads the act performed within it.

Instantiates: Context-Bounded Meaning Recovery — the walkthrough recovers illocutionary force, the "what is it doing" layer of a reading.
Consumes: Context Reconstruction Worksheet supplies the situational record whose anchors it activates.
Sibling mechanisms: Context Reconstruction Worksheet · Ambiguity Register · Interpretation Brief · Framework Selection Memo · Evidence-to-Claim Matrix · Close Reading Table · Alternative Readings Review · Glossary or Code Key · Stakeholder Meaning Check · Precedent Comparison Table · Translation Backcheck · Hermeneutic Loop Log · Interpretation Red Team

Notes¶

Recovered force is the act performed in context, not proof of the speaker's private intent — "this functions as a threat here" is a warranted reading; "the author intended to threaten" is a further, weaker claim the substrate usually cannot settle. Keeping force and intent distinct is what stops the walkthrough from becoming a mind-reading exercise.

References¶

[1] Illocutionary force (J. L. Austin, How to Do Things with Words; developed by John Searle) is the act a speaker performs in saying something — ordering, promising, warning — as distinct from the sentence's literal content (locution) and its effect on the hearer (perlocution). Recovering force is precisely reading the illocution the words alone underdetermine. ↩