Request / Order Clarification Prompt¶
Clarification prompt — instantiates Speech-Act Clarification
Asks, at the moment of ambiguity, whether a statement is a request, a recommendation, an assignment, or a command — so a listener knows whether compliance is optional or required before acting on it.
A Request / Order Clarification Prompt is the lightweight, in-the-moment move of taking a statement whose directive force is unclear and forcing that force to be named out loud: is this a command, an assignment, a request, or just a recommendation? Its distinguishing move among its siblings is that it works live and pre-consequence, on the directive family alone — it resolves the one question a listener needs before acting, optional or required?, and it names why the wording was ambiguous in the first place. It does not record the answer, pin an owner, or check whether the speaker was entitled to give an order; it simply converts a softened, ambiguous instruction into a labeled one before anyone acts on the wrong reading.
Example¶
A tech lead drops a line in the team's Slack channel during code review: "we should really add tests around the payment-retry path before this ships." Two engineers read it opposite ways. One treats it as a strong suggestion to schedule for next sprint; the other reads it as a hard blocker on the current pull request. The wording — the hedging "should really" — carries no reliable signal about which. Under a Request / Order Clarification Prompt, the team's norm is to reply with the classifying question rather than guess: "Is that a blocker on this PR (order), work you want assigned to someone (assignment), or a nice-to-have for later (recommendation)?" The lead answers: "Blocker — and assign it to whoever picks the PR up." The directive force is now explicit, the ambiguity created by the polite hedge is dissolved, and the PR does not merge on a misread. The prompt produced a label, nothing more — but the label was the whole point.
How it works¶
The distinctive step is presenting the actual utterance alongside a small closed menu drawn from the directive family — command/order, assignment, request, recommendation, informational — and asking the speaker (or the group, with the speaker confirming) to place the statement on it. Because the menu is closed and short, the answer is fast and unambiguous. The prompt also surfaces the mismatch source: it names why the force was masked — usually a politeness strategy that softened a command into a musing, or a power gradient that made a junior unable to tell a suggestion from an instruction. It is speaker-facing and resolves force at the moment of speaking; it deliberately stops there, producing a shared label rather than a durable record.
Tuning parameters¶
- Menu granularity — a coarse optional/mandatory split, or the full command / assignment / request / recommendation ladder. Finer menus disambiguate more precisely but slow the exchange and can feel bureaucratic in casual talk.
- Who names it — the speaker self-labels, or the listener proposes a reading and the speaker confirms. Self-labeling is cleaner; listener-proposes is safer across a steep power gradient, where a junior needs permission to ask.
- Trigger threshold — prompt on every instruction, or only on consequential ones. Prompting everything makes conversation stilted; prompting nothing lets the costly mishears through.
- Face preservation — how bluntly the label is forced versus how much tact is kept. The wording can stay polite, but the performed force must come out clear; over-softening reintroduces exactly the ambiguity the prompt exists to remove.
When it helps, and when it misleads¶
Its strength is that it kills polite ambiguity cheaply, at the one moment it is still free to fix — especially across power gradients, where indirectness is strongest and juniors carry the cost of guessing wrong. It turns "maybe we should" into a known optional-or-required before anyone commits effort or lets a hazard through.
Its failure modes follow from how light it is. Over-prompting chills ordinary talk into a stilted label-everything ritual, so it must be reserved for statements that actually carry consequences. It can also be run in reverse and weaponized: a speaker who labels every instruction a mere "recommendation" keeps plausible deniability while still expecting compliance, so the label dodges accountability rather than clarifying it. And it resolves force, not validity — a statement can be cleanly labeled an order while the speaker had no standing to command at all.[n1] The discipline that keeps it honest is to reserve it for consequential statements, to pair the resulting label with who is accountable, and to treat a "recommendation" that carries compliance pressure as the mismatch it is.
How it implements the components¶
Request / Order Clarification Prompt fills the classification-and-diagnosis front of the archetype's machinery — the part that resolves what act before anything is relied on:
utterance— it starts from the exact statement whose force is disputed, not a paraphrase, because the hedge in the literal wording is what created the ambiguity.speech_act_type— its core output: a label placing the utterance in the directive family (command, assignment, request, recommendation), which fixes whether compliance is required or optional.speech_act_mismatch_source— it names why the force was unclear — a politeness softening, a power gradient — so the same masking can be anticipated next time.
It does not record the resulting decision, owner, or deadline (consequence_record, audience_or_counterparty) — that is Meeting Action-Item Capture; and it does not check whether the speaker had the standing to issue an order (authority_or_standing) — that is Authority Matrix. It labels the act; other mechanisms record it and validate it.
Related¶
- Instantiates: Speech-Act Clarification — the prompt resolves the directive force of an utterance at the moment of ambiguity, before a misread hardens.
- Sibling mechanisms: Meeting Action-Item Capture · Authority Matrix · Formal Declaration Record · Apology / Repair Protocol · Commitment Register · Consent Confirmation Form · Contract Speech-Act Clause · Readback Confirmation
Editorial Notes¶
Form Classification¶
Form family: Interface, Display & Cue
Rationale: Request / Order Clarification Prompt operates as a user-facing prompt, display, template, or perceptual cue that shapes attention and action at the point of use because it asks, at the moment of ambiguity, whether a statement is a request, a recommendation, an assignment, or a command — so a listener knows whether compliance is optional or required before acting on it.
Independent corroboration: The frozen evidence defines Request / Order Clarification Prompt as 'Asks, at the moment of ambiguity, whether a statement is a request, a recommendation, an assignment, or a command — so a listener knows whether compliance is optional or required before acting on it', so its operative form is Interface, Display & Cue.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Linguistics & Semiotics
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Distinguishing requests, recommendations, assignments, and commands is rooted in pragmatics and speech-act analysis.
Related originating lineages:
- Organizational & Management Science — Authority and delegation practice materially shapes consequences of the classification at work.
- Philosophy — Philosophy of language supplied illocutionary-force and obligation distinctions.
Review resolution: Both blind reviewers agree that linguistics_semiotics is the primary historical origin. Explicit reconciliation of alternate origin disagreement, domain reach disagreement adopts reviewer_a's evidence: Distinguishing requests, recommendations, assignments, and commands is rooted in pragmatics and speech-act analysis. The selected record uses alternates=organizational_management, philosophy, origin_mode=cross_disciplinary_synthesis, and domain_reach=universal; the other review proposed alternates=communication_media_studies, organizational_management, origin_mode=cross_disciplinary_synthesis, and domain_reach=multi_domain. The selected combination better preserves the mechanism-specific formative lineages and calibrated scope; broader present-day use is not treated as proof of additional historical origin.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Politeness theory (Brown & Levinson) explains why directive force gets masked: to protect a hearer's "face," speakers soften commands into indirect, hedged forms — "you might want to…," "we should probably…" — trading clarity of force for social smoothness. The same indirectness that preserves harmony is exactly what makes an order indistinguishable from a suggestion, which is why the prompt has to make the performed force explicit without stripping the tact from the wording. ↩